1 WebLogic Server Domains

An Oracle WebLogic Server administration domain is a logically related group of Oracle WebLogic Server resources.

Domains include a special Oracle WebLogic Server instance called the Administration Server, which is the central point from which you configure and manage all resources in the domain. Usually, you configure a domain to include additional Oracle WebLogic Server instances called Managed Servers. You deploy Web applications, EJBs, Web services, and other resources onto the Managed Servers and use the Administration Server for configuration and management purposes only.

1.1 Configure domains

This section describes how to configure your domain. This section includes the following tasks:

1.1.1 Configure general settings

To configure general settings for a domain:

  1. From the Welcome Page, select Targets, then select Middleware.

  2. In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.

  3. From the WebLogic Domain dropdown menu, select Administration, then select General Settings.

    From the General Settings page you can configure administrative options that apply to all server instances in the current domain, such as:

    • Enable Administration Port

    • Administration Port

    • Production Mode

    • Enable Exalogic Optimizations

    • Enable Cluster Constraints

    • On-demand Employment of Internal Applications

    • Enable Oracle Guardian Agent

    For more information about these fields, see Configuration Options.

    Optionally, expand Advanced to define advanced settings for this domain.

  4. Click Save.

1.1.1.1 Configure the domain-wide administration port

Before you begin:

The administration port accepts only secure, SSL traffic, and all connections via the port require authentication by a server administrator. Because of these features, enabling the administration port imposes the following restrictions on your domain:

  • The Administration Server and all Managed Servers in your domain must be configured with support for the SSL protocol.

  • All server instances in the domain, including the Administration Server, enable or disable the administration port at the same time.

Note:

The administration port cannot be dynamically enabled on a Managed Server. You must shut down each Managed Server, enable the administration port, then restart.

WebLogic Server provides the option to enable an SSL administration port for use with all server instances in the domain. Using the administration port is strongly recommended. It provides three capabilities:

  • Since communication uses SSL, administration traffic (which includes such things as administrator passwords) is more secure.

  • It enables you to start a server instance in the STANDBY state.

  • It enables you to separate administration traffic from application traffic in your domain.

To enable the administration port for a domain:

  1. From the Welcome Page, select Targets, then select Middleware.

  2. In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.

  3. From the WebLogic Domain dropdown menu, select Administration, then select General Settings.

  4. Select the Enable Administration Port check box to enable the SSL administration for this domain.

  5. In the Administration Port field, enter the SSL port number that server instances in the domain use as the administration port. You can override an individual server instance's administration port assignment on the Advanced options portion of the General Settings page.

  6. Click Save.

After you finish:

Start all Managed Server instances in the domain. You do not need to restart the Administration Server.

1.1.1.2 Archive domain configuration files

To configure how many archive files are retained:

  1. From the Welcome Page, select Targets, then select Middleware.

  2. In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.

  3. From the WebLogic Domain dropdown menu, select Administration, then select General Settings.

  4. Expand Advanced, then select the Configuration Archive Enabled check box.

  5. In the Archive Configuration Count field, enter the number of archive files to retain.

  6. Click Save.

1.1.1.3 Change to production mode

All server instances in a domain run either in development mode or production mode. In general, production mode requires you to configure additional security features.

To configure all server instances in a domain to run in production mode:

  1. From the Welcome Page, select Targets, then select Middleware.

  2. In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.

  3. From the WebLogic Domain dropdown menu, select Administration, then select General Settings.

  4. Select the Production Mode check box.

  5. Click Save.

  6. Shut down any server instances that are currently running.

  7. Invoke the domain's startWebLogic script. The Administration Server starts in the new mode.

  8. If the domain contains Managed Servers, start the Managed Servers.

1.1.2 Configure domain JTA settings

To configure the Java Transaction API (JTA) of a domain:

  1. From the Welcome Page, select Targets, then select Middleware.

  2. In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.

  3. From the WebLogic Domain dropdown menu, select Administration, then select Java Transaction API (JTA).

    From the JTA page you can define the JTA configuration settings for your domain, such as:

    • Timeout Seconds

    • Abandon Timeout Seconds

    • Before Completion Iteration Limit

    • Max Transactions

    • Max Unique Name Statistics

    • Checkpoint Interval Seconds

    • Forget Heuristics

    • Unregister Resource Grace Period

    • Execute XA Calls in Parallel

    • Enable Two Phase Commit

    • Enable Tightly Coupled Transactions

    • Enable Cluster-Wide Recovery

    For more information about these fields, see Configuration Options.

    Optionally, expand Advanced to define advanced settings for this domain.

  4. Click Save.

1.1.3 Configure the default JPA persistence provider

You can specify which Java Persistence API (JPA) persistence provider to use for each persistence entity in the persistence.xml file. However, if no persistence provider is specified, the domain-wide default provider is used.

Changing the default provider does not affect applications that are already deployed. The setting takes effect when the server instance is restarted or the application is manually redeployed.

To specify the default JPA provider in a domain:

  1. From the Welcome Page, select Targets, then select Middleware.

  2. In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.

  3. From the WebLogic Domain dropdown menu, select Administration, then select Java Persistence API (JPA).

    From the JPA page you can define the JPA configuration for your domain by selecting a JPA provider from the Default JPA Provider menu.

    For more information, see Configuration Options.

  4. Click Save.

1.1.4 Configure domain EJBs

To configure the EJBs in a domain:

  1. From the Welcome Page, select Targets, then select Middleware.

  2. In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.

  3. From the WebLogic Domain dropdown menu, select Administration, then select EJBs.

    From the EJB page you can define domain-wide EJB configuration settings, such as:

    • Java Compiler

    • Prepend Java Compiler Options

    • Append Java Compiler Options

    • Extra RMIC Options

    • Keep Generated EJBC Source Files

    • Force Generation

    • Temporary Directory

    • Extra EJBC Options

    For more information about these fields, see Configuration Options.

  4. Click Save.

1.1.5 Configure domain Web applications

To configure Web applications in a domain:

  1. From the Welcome Page, select Targets, then select Middleware.

  2. In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.

  3. From the WebLogic Domain dropdown menu, select Administration, then select Web Applications.

    From the Web Applications page you can define the domain-wide Web application configuration settings, such as:

    • Relogin Enabled

    • Allow All Roles

    • Filter Dispatched Requests

    • Overload Protection Enabled

    • X-Powered-By Header

    • Mime Mapping File

    • Optimistic Serialization

    • Error on Name Request Time Value

    • Client Cert Proxy Enabled

    • HTTP Trace Support Enabled

    • WebLogic Plug-in Enabled

    • Auth Cookie Enabled

    • Change Session ID on Authentication

    • WAP Enabled

    • Post Timeout

    • Maximum Post Timeout

    • Maximum Post Size

    • Work Context Propagation Enabled

    • P3P Header Value

    • JSP Compiler Backwards Compatible

    • Archived Real Path Enabled

    For more information about these fields, see Configuration Options.

  4. Click Save.

1.1.6 Create domain notes

To create notes for domain configuration:

  1. From the Welcome Page, select Targets, then select Middleware.

  2. In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.

  3. From the WebLogic Domain menu, select Administration, then select Notes.

  4. On the Notes page, enter your notes.

  5. Click Save.

For more information, see Configuration Options.