bea.com | products | dev2dev | support | askBEA

Download Docs | Site Map | Glossary
Search

Administration Console Online Help

Domain

A domain is an inter-related set of WebLogic Server resources that are managed as a unit. A domain includes one or more WebLogic Servers, and may include one or more WebLogic Server clusters.

A domain is a self-contained administrative unit. If an application is deployed in a domain, components of that application cannot be deployed on servers that are not a part of that domain. When a cluster is configured in a domain, all of its servers must be a part of that domain as well.

For each domain, you can configure a subset of Weblogic Server resources that apply to all servers and clusters that reside in the domain. These attributes are configured in the Domain node of the Administration Console.

Tasks

Enabling the Domain-Wide Administration Port

WebLogic Server 7.0 provides the option to enable an SSL administration port for use with all servers in the domain. The administration port is optional, but it provides two capabilities:

- It enables you to start a server in STANDBY state.

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

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 servers in the domain, including the Administration Server, enable or disable the administration port at the same time.

- After enabling the administration port, you must establish an SSL connection to the Administration Server in order to start any managed server in the domain. This applies whether you start managed servers manually, at the command line, or using Node Manager.

- After enabling the administration port, all Administration Console traffic must connect via the administration port.

To enable the administration port for your domain:

1. First ensure that all servers in the domain are properly configured to use SSL. See Configuring the SSL Protocol (Version 7.0) for more information.

2. Select the name of the active domain in the left pane to display the domain's configuration attributes.

3. Click the Configuration tab in the right pane.

4. Click the General tab in the right pane.

5. Select the Enable Domain Wide Administration Port (Please Configure SSL) attribute to enable the SSL administration port for this domain.

6. Enter the default SSL port number that all servers in the domain use as the administration port. (You can override an individual server's administration port selection using the server's Configuration->SSL Ports tab.)

7. Click Apply to apply your changes.

8. To start Managed Servers after enabling the administration port, you must establish an SSL connection to the domain's Administration Server. You can do this by specifying the following option at the command line when started the Managed Server:

   >     -Dweblogic.management.server=https://host:admin_port

   In this argument, host refers to the address of the Administration Server and admin_port is the administration port that the Administration Server uses. Note that you must specify the http s:// prefix, rather than http://.

Creating a New Domain

Note: WebLogic Server 7.0 provides a new Configuration Wizard to help you create a new domain with an administration server, managed servers, and optionally, a cluster. The Configuration Wizard also automatically generates start scripts for the server(s) you choose to add to the new domain. See Creating New Domains Using the Configuration Wizard for more information.
The following steps describe how to use the Administration Console to generate a basic config.xml file for a new domain. You can use this functionality to set up the new domain name, JTA, SNMP, Logging, and Application settings. However, you cannot add new servers or generate start scripts using this functionality.

To generate a basic config.xml file for a new domain using the Administration Console:

1. Right-click the instance node that represents the active domain (for example, myDomain) in the left pane. This opens a pop-up menu.

2. Select Create or edit other Domains from the pop-up menu. The current domain configurations display in the right pane.

3. Select Configure a new Domain...

4. Fill in the new domain attribute fields as follows:

   - Name: Enter a name for the new domain.

   - Location: Enter the path to hold the new domain's config.xml configuration file. If you specify a directory that does not exist, the Administration Console automatically creates the directory.

5. Click Create to create a new domain.

6. Use the Configuration, Security, and Notes tabs to configure attributes for the new domain, clicking Apply to apply your changes. The Administration Console records your changes in the new domain's config.xml configuration file.

7. After you have finished configuring the new domain, click the Home icon at the top of the page to return to the active domain.

Starting and Shutting Down Domains

To start or shut down all of the Managed Servers in the active domain, do the following:

1. Right click on the name of the active domain in the left panel.

2. Select Kill this domain... or Start this domain...

If you start the entire domain from the Administration Console, the results displayed in the right pane will consist of a series of links to the results for each Managed Server that was configured for that domain.

Viewing the Domain Log

1. Right-click the instance node that represents your Domain (for example, "examples") in the left pane. This opens a pop-up menu.

2. Click View Domain Log. The log displays in the right pane.

Specifying the Name and Location of the Domain Log File

1. Click the instance node that represents your Domain (for example, "examples") in the left pane.

2. Select the Configuration tab in the right pane, then select the Logging tab.

3. In the File Name box, enter a path and filename for the domain log.

   For information about including a time and date stamp in the name of rotated log files, refer to the next section, Specifying Criteria for Rotating Domain Log Files.

4. Click Apply to apply your changes.

5. Restart the Administration Server. The Administration Server writes all subsequent domain messages to the new file.

Specifying Criteria for Rotating Domain Log Files

1. Click the instance node that represents your Domain (for example, myDomain) in the left pane. The domain dialog displays in the right pane showing the tabs associated with this domain.

2. On the Configuration tab, click the Logging tab.

3. If you want all log messages to accumulate in a single file, in Rotation Type, choose none. You must erase the contents of the file when the size is unwieldy.

4. If you want the Administration Server to move old messages to another file when the current log file reaches a specific size, do the following:

   1. In Rotation Type, choose by Size.

   2. In File Min Size, specify the file size (1 - 65535 kilobytes) that triggers the server to move log messages to a separate file. After the log file reaches the specified minimum size, the next time the server checks the file size, it will rename the current log file and create a new one to store subsequent messages.

   3. If you want to limit the number of log files that the server creates to store old log messages, select Number of Files Limited. Then in File Count, enter the maximum number of files. If the server receives additional domain log messages after reaching the capacity of the last log file, it overwrites the oldest log file.

   4. Click Apply.

5. If you want the Administration Server to create another file at specific time intervals, do the following:

   1. In Rotation Type, choose by Time.

   2. In Rotation Time, enter the start time for a time-based rotation sequence.

      At the time that you specify, the server rotates the current log file. If the time that you specify has already past, then the server starts its file rotation immediately.

      Thereafter, the server rotates the log file at an interval that you specify in File Time Span.

      Use the following format: hh:mm, where hh is the hour in a 24-hour format and mm is the minute.

   3. In File Time Span, enter the interval at which the server saves old messages to another file.

   4. If you want to limit the number of log files that the server creates, select Number of Files Limited. Then in File Count, enter the maximum number of log files. If the server reaches this maximum during the current time-rotation sequence, it overwrites the oldest log file when the next interval expires.

   5. Click Apply.

6. To include a time or date stamp in the file name when the log file is rotated, in the File Name field, add java.text.SimpleDateFormat variables to the file name. Surround each variable with percentage (%) characters.

   For example, if you enter the following value in the File Name field:
   wl-domain_%yyyy%_%MM%_%dd%_%hh%_%mm%.log

   the domain log file will be named:
   wl-domain_yyyy_MM_dd_hh_mm.log

   When the Administration Server rotates the domain log file, the rotated file name contains the date stamp. For example, if domain log file is rotated on 2 April, 2003 at 10:05 AM, the log file that contains the old log messages will be named:
   wl-domain_2003_04_02_10_05.log

   If you do not include a time and date stamp, the rotated log files are numbered in order of creation filename nnnnn, where filename is the name configured for the log file. For example: wl-domain.log00007.

Administering SNMP

For more information on how to configure SNMP, see Configuring SNMP and WebLogic Server.

1. Click the instance node that represents your Domain (for example, myDomain) in the left pane. The domain dialog displays in the right pane showing the tabs associated with this domain.

2. On the Configuration tab, click the SNMP tab.

3. Click the checkbox to enable the SNMP service.

4. In SNMP Port, specify the port on which the agent will listen for SNMP requests.

5. In Mib Data Refresh Interval, specify the interval (seconds) MIB values are cached before being refreshed

6. In Server Status Check Interval Factor, specify a value used to determine the interval to check the server status.

7. In Community Prefix, provide the SNMP Community name.

8. Specify the Debug Level.

9. Select Trap Destinations:

   1. To select a Trap Destination, select a trap destination in the list of Available trap destinations and click the right arrow to move the trap destination to the Chosen list. You can select multiple trap destinations by Shift-clicking or Ctrl-clicking trap destinations in the list.

   2. To remove a trap destination, select a trap destination in the list of Chosen trap destinations and click the left arrow to move the trap destination to the Available list. You can select multiple trap destinations by Shift-clicking or Ctrl-clicking trap destinations in the list.

Enabling Configuration Auditing

Configuration auditing causes the Administration Server to emit log messages when a user changes the configuration or invokes management operations on any resource within a domain. See "Configuration Auditing" in the Administration Guide.

To enable configuration auditing:

1. Click the instance node that represents your Domain (for example, myDomain) in the left pane. The domain dialog displays in the right pane showing the tabs associated with this domain.

2. On the Configuration tab, click the General tab.

3. On the General tab, place a check mark in the Configuration MBean Auditing Feature Enabled check box.

4. Click Apply.

5. Restart the Administration Server.

Administering a Different Domain

1. Right-click the instance node that represents your Domain (for example, myDomain) in the left pane. This opens a pop-up menu.

2. Click Create or edit other Domains. The current domain configurations display in the right pane.

3. Click the name of an inactive domain to administer that domain.

4. After you have finished configuring the inactive domain, click the Home icon at the top of the page to return to the active domain.