bea.com | products | dev2dev | support | askBEA

Download Docs | Site Map | Glossary
Search

Administration Console Online Help

Servers

A server is an instance of WebLogic Server. A server is part of an inter-related set of WebLogic Server resources managed as a unit called a domain. A domain includes one or more WebLogic Servers, and may include WebLogic Server clusters. More than one server may reside on a single machine.

A server can be either a managed server or an Administration Server. A WebLogic Server running the Administration Service is called an Administration Server and hosts the Administration Console. In a domain with multiple WebLogic Servers, only one server is the Administration Server; the other servers are called Managed Servers. Each WebLogic Managed Server obtains its configuration at startup from the Administration Server.

For each server, you can configure a variety of attributes that define the functionality of the server in a WebLogic domain. These attributes are configured using the Servers node of the Administration Console.

Server names must be unique within a domain. For example, if you create a server instance named ManagedServer1 in a domain named DomainA, you cannot create another server instance named ManagedServer1 in DomainA.

Server Management Tasks

Adding a Server to the Domain

A WebLogic Server instance must be installed before you can add a server to your domain.

1. Select the Servers node in the left panel.

2. Click configure a new server.

3. Enter the name of the server in the name field.

   Server names must be unique within a domain. For example, if you create a server instance named ManagedServer1 in a domain named DomainA, you cannot create another server instance named ManagedServer1 in DomainA.

4. Select a machine name from the drop-down list labelled Machine. If your domain only uses a single machine, leave this field set to (none).

5. Enter the listen port number of this server in the Listen Port field.

6. Fill in the remaining fields on the General Tab

7. Click Create. The new server appears under the Servers node in the left pane. You may now configure other attributes for this server.

Cloning a Server

Cloning a server creates a new server instance with the same attributes as the original. server.

1. Click the Servers node in the left pane. The Servers table displays in the right pane showing all the servers defined in the domain.

2. Click the Clone icon in the row of the server you want to clone. A dialog displays in the right pane showing the tabs associated with cloning a new server.

3. Enter values in the Name, Machine, and Listen Port, Administration Port, and List attribute fields.

4. Click the Clone button in the lower right corner to create a server instance with the name you specified in the Name field. The new instance is added under the Servers node in the left pane.

5. Click the additional tabs and change the attribute fields or accept the default values as assigned.

6. Click Apply to save any changes you made.

Deleting a Server

1. Click the Servers node in the left pane. The Servers table displays in the right pane showing all the servers defined in the domain.

2. Click the Delete icon in the row of the server you want to delete. A dialog displays in the right pane asking you to confirm your deletion request.

3. Click Yes to delete the server. The server icon under the Servers node is deleted.

Starting a Server

If you have configured a Node Manager on the host machine of a Managed Server, you can do the following to start a Managed Server from the Administration Console:

1. Expand the Servers node in the left pane. A list of servers appears under the Servers node.

2. Select a specific server in the left pane.

3. Select the Control tab.

4. Select Start this server. Then click Yes to confirm and start the server, or No to cancel the action.

Note: This command overrides the Startup Mode setting on the Server—> Configuration—>General tab.

Starting a Server in the STANDBY State

If you have configured a Node Manager on the host machine of a Managed Server, and if you have set up an Administration Port for the server, you can start a server and place it in STANDBY from the Administration Console:

1. Expand the Servers node in the left pane. A list of servers appears under the Servers node.

2. Select a specific server in the left pane.

3. Select the Control tab.

4. Select Start this server in Standby mode. Then, click Yes to confirm and start the server in Standby mode, or No to cancel the action.

Note: This command overrides the Startup Mode setting on the Server—> Configuration—>General tab.

For information about Administration Ports, refer to "Administration Port and Administration Channel."

Resuming a Server

1. Expand the Servers node in the left pane. A list of servers appears under the Servers node.

2. Select a specific server in the left pane.

3. Select the Control tab.

4. Select Resume this server. Then, click Yes to confirm and resume the server, or No to cancel the action.

Shutting Down a Server

The following steps initiate a graceful shutdown.

1. Expand the Servers node in the left pane. A list of servers appears under the Servers node.

2. Select a specific server in the left pane.

3. Select the Control tab.

4. Select Shutdown this server. Then click Yes to confirm and shut down the server, or No to cancel the action.

Forcing Shutdown of a Server

This forces subsystems to terminate in-work requests immediately and the server to stop. If a Managed Server does not respond to this request, and if you have configured a Node Manager on the server's host machine, then the Node Manager kills the server.

1. Expand the Servers node in the left pane. A list of servers appears under the Servers node.

2. Select a specific server in the left pane.

3. Select the Control tab.

4. Select Force shutdown this server. Then click Yes to confirm and force shutdown of the server, or No to cancel the action.

Setting the Timeout Period for LifeCycle Operations

1. Expand the Servers node in the left pane. A list of servers appears under the Servers node.

2. Select a specific server in the left pane.

3. Select the Configuration—>Tuning tab.

4. In the Timeout for Server Lifecycle Operations box, enter the number of seconds a lifecycle operation waits before timing out.

5. Click Apply to save your changes.

For more information about the timeout period for LifeCycle operations, refer to Timeout Period for LifeCycle Operations in the WebLogic Administration Guide.

Specifying a Startup or Shutdown Class for a Server

1. Click the Server node in the left pane and select a specific server in the left pane.

2. Select the Deployments tab.

3. Select the Startup/Shutdown tab. This tab lists all of the configurations of startup or shutdown classes that have been created in this domain.

4. To assign a class to this server, move it from the Available column to the Chosen column.

5. To unassign a class, move it from the Chosen column to the Available column.

6. Click Apply to save your changes.

Specifying Cluster Settings for a Server

1. Click the Server node in the left pane and select a specific server in the left pane.

2. Select the Cluster tab.

3. Enter the name of a list of clustered instances for storing session state replicas in the Replication Group field.

4. Enter the name of a secondary list of clustered instances for storing session state replicas in the Preferred Secondary Group field.

5. Enter a value in the range 1-100, to determine what proportion of the load a server will bear relative to other servers in a cluster, in the Cluster Weight field.

6. Enter the interface address to handle multicast traffic in the Interface Address field.

7. Click Apply to save your changes.

JDBC Tasks

Monitoring All Active JDBC Connection Pools

1. In the left pane, click the Servers node to expand it, then select a server. A dialog displays in the right pane showing tabs with attributes for the server.

2. Select the Services tab and then select the JDBC tab.

3. Click the Monitor all Active Pools text link. A table displays with information about all active JDBC connection pools assigned to the server.

Assigning JDBC Connection Pools to a Server

1. Click the Server node in the left pane.

2. Select the server to which you want to assign a connection pool in the left pane.

3. Select the Services tab.

4. Select the JDBC tab.

5. To assign a connection pool to the selected server, select a connection pool in the list of Available connection pools and click the right arrow to move the connection pool to the Chosen list. You can select multiple connection pools by Shift-clicking or Ctrl-clicking connection pools in the list.

6. To remove a connection pool from the selected server, select a connection pool in the list of Chosen connection pools and click the left arrow to move the connection pool to the Available list. You can select multiple connection pools by Shift-clicking or Ctrl-clicking connection pools in the list.

7. Click Apply to save your changes.

Connectivity Tasks

Assigning WLEC Connection Pools to a Server

1. Click the Server node in the left pane.

2. Select the server to which you want to assign a connection pool in the left pane.

3. Select the Services tab.

4. Click the WLEC Tab.

5. To assign a connection pool to the selected server, select a connection pool in the list of Available connection pools and click the right arrow to move the connection pool to the Chosen list. You can select multiple connection pools by Shift-clicking or Ctrl-clicking connection pools in the list.

6. To remove a connection pool from the selected server, select a connection pool in the list of Chosen connection pools and click the left arrow to move the connection pool to the Available list. You can select multiple connection pools by Shift-clicking or Ctrl-clicking connection pools in the list.

7. Click Apply to save your changes.

Assigning Jolt Connection Pools to a Server

1. Click the Server node in the left pane.

2. Select the server to which you want to assign a connection pool in the left pane.

3. Select the Services tab.

4. Click the Jolt Tab.

5. To assign a connection pool to the selected server, select a connection pool in the list of Available connection pools and click the right arrow to move the connection pool to the Chosen list. You can select multiple connection pools by Shift-clicking or Ctrl-clicking connection pools in the list.

6. To remove a connection pool from the selected server, select a connection pool in the list of Chosen connection pools and click the left arrow to move the connection pool to the Available list. You can select multiple connection pools by Shift-clicking or Ctrl-clicking connection pools in the list.

7. Click Apply to save your changes.

Assigning a WTCServer to a Server

1. Click the Server node in the left pane.

2. Select the server to which you want to assign a WTCServer in the left pane.

3. Select the Services tab.

4. Click the WTC Tab.

5. To assign a WTCServer to the selected server, select a WTCServer in the list of Available WTCServers and click the right arrow to move the WTCServer to the Chosen list. You can not assign more than one WTCServer to a WebLogic Server.

6. To remove a WTCServer from the selected server, select the WTCServer in the list of Chosen WTCServers and click the left arrow to move the WTCServer to the Available list.

7. Click Apply to save your changes.

Server Configuration Tasks

Setting the Listen Port

1. Expand the Servers node in the left pane. A list of Servers appears under the Servers node.

2. Select the Server for which you want to set the listen port.

3. Select the Configuration tab in the right pane.

4. Select the General tab under the Configuration Tab.

5. Enter the port number that this server is listening on in the Listen Port field. (This port number is initially configured when you install an instance of WebLogic Server.)

6. Click Apply

7. Re-start the server whose listen port you just set.

Specifying the Default Protocol

1. Click the server node in the left pane.

2. Select a specific server in the left pane.

3. Select the Connections tab.

4. Select the Protocols tab.

5. Select a protocol from the Default Protocol list.

6. Select a secure protocol from the Default Secure Protocol list.

7. Click Apply

Configuring the T3 Protocol

1. Click the server node in the left pane.

2. Select a specific server in the left pane.

3. Select the Connections tab.

4. Select the Protocols tab.

5. Enter the maximum T3 message size, in bytes, in the T3 Max Message Size field

6. Enter the a value, in seconds, in the T3 Message Timeout field.

7. Click Apply.

Configuring the HTTP Protocol

1. Click the server node in the left pane.

2. Select a specific server in the left pane.

3. Select the Connections tab.

4. Select the Protocols tab.

5. Enter the maximum HTTP message size, in bytes, in the HTTP Max Message Size field

6. Enter the a value, in seconds, in the HTTP Message Timeout field.

7. Click Apply.

Configuring the IIOP Protocol

1. Click the server node in the left pane.

2. Select a specific server in the left pane.

3. Select the Connections tab.

4. Select the Protocols tab.

5. Enable the IIOP protocol by checking the Enable IIOP check box.

6. Enter the default IIOP user name in the Default IIOP User field.

7. Enter the default IIOP password in the Default IIOP Password field.

8. Enter the maximum IIOP message size, in bytes, in the IIOP Max Message Size field

9. Enter the a value, in seconds, in the IIOP Message Timeout field.

10. Click Apply.

Creating an Execute Queue

1. Click the Server node in the left pane.

2. Select a specific server in the left pane.

3. Select the Monitoring tab.

4. Select the General tab.

5. Select the Monitor all Active Queues... link.

6. Select Configure Execute Queue...

7. Select Configure a new Execute Queue...

8. Fill in the fields for the new execute queue as appropriate.

9. Click Create to create the new execute queue.

Assigning FileT3 (Deprecated) Files to a Server

For information on how to create a file system, see Create a File System.

1. Click the Server node in the left pane.

2. Select the server to which you want to assign a file system in the left pane.

3. Select the Services tab.

4. Click the FileT3 Tab.

5. To assign a file system to the selected server, select a file system in the list of Available file systems and click the right arrow to move the file system to the Chosen list. You can select multiple file systems by Shift-clicking or Ctrl-clicking file systems in the list.

6. To remove a file system from the selected server, select a file system in the list of Chosen file systems and click the left arrow to move the file system to the Available list. You can select multiple file systems by Shift-clicking or Ctrl-clicking file systems in the list.

7. Click Apply to save your changes.

Configuring Low Memory Detection

1. Click the server node in the left pane.

2. Select a specific server in the left pane.

3. Select the Configuration tab.

4. Select the Memory tab.

5. Enter a percentage value in the Low Memory GCThreshold attribute field to specify the threshold after which WebLogic Server performs automatic garbage collection. A value of 5 means that the server forces garbage collection after the average free memory reaches 5% of the initial free memory measured at the server's boot time.

6. Enter a percentage value in the Low Memory Granularity Level attribute field to specify the size of memory drop required before WebLogic Server logs a low memory warning message. A value of 5 means that if the average free memory drops by 5% or more over two measured intervals, the server logs a low memory warning in the log file and changes the server health state to "warning."

7. Enter a value in the Low Memory Sample Size to specify the number of times the server samples free memory during a fixed time period. Using a higher sample size can increase the accuracy of the reading.

8. Enter a value in the Low Memory Time Interval to define the interval (in seconds) over which the server determines average free memory values.

9. Click Apply to apply your changes.

10. Reboot the server to use the new low memory detection attributes.

Tuning an Execute Queue for Overflow Conditions

1. Click the server node in the left pane.

2. Select a specific server in the left pane.

3. Select the Monitoring tab.

4. Select the General tab.

5. Click the Monitor All Active Queues... text link to display the execute queues this server uses.

6. Click the Configure Execute Queue... text link to display the execute queues that you can modify.

7. Click the name of the default execute queue or the user-defined execute queue that you want to configure.

8. To specify how this server detects an overflow condition in the selected queue, edit the attributes:

   - Queue Length: Enter a value to indicate the maximum possible length that the execute queue can reach. This value should be higher than the normal operating length of the queue.

   - Queue Length Threshold Percent: Enter the percentage (from 1 to 99) of the Queue Length size that can be reached before the server indicates an overflow condition for the queue. Queue lengths below the threshold percentage are considered normal; sizes above the threshold percentage indicate an overflow

9. To specify how this server should address an overflow condition for the selected queue, edit the attribute:

   - Threads Increase: Enter the number of threads WebLogic Server should add to this execute queue when it detects an overflow condition. If you specify zero threads (the default), the server changes its health state in response to an overflow condition in the thread, but it does not allocate additional threads to reduce the workload.

10. To fine-tune the variable thread count of this execute queue, edit the attributes:

    - Threads Minimum: Enter the minimum number of threads that WebLogic Server should maintain in this execute queue to prevent unnecessary overflow conditions.

    - Threads Maximum: Enter the maximum number of threads that this execute queue can have; this value prevents WebLogic Server from creating an overly high thread count in the queue in response to continual overflow conditions.

11. Click Apply to apply your changes.

12. Reboot the selected server to enable the new execute queue settings.

Setting the Maximum Number of Open Sockets

1. Click the server node in the left pane.

2. Select a specific server in the left pane.

3. Select the Configuration tab.

4. Select the Socket tab.

5. Enter the maximum number of sockets you want to be open in the Max Open Sock Count field

6. Click Apply.

Server Logging Tasks

Viewing Server Logs

1. Right-click the instance node in the left pane under Servers for the server whose log you want to view. This opens a pop-up menu.

2. Click View Server Log.

Specifying the Transaction Log File Location (Prefix)

1. Click the Server node in the left pane.

2. Select a specific server in the left pane.

3. Select the Logging tab.

4. Select the JTA tab.

5. Enter a transaction log file prefix.

6. Click Apply to save the setting.

The TransactionLogFilePrefix attribute should be set so that transaction log files are created on a highly available file system, for example, on a RAID device. To take advantage of the migration feature of the Transaction Recovery Service for servers in a cluster, you must store the transaction log in a location that is available to a server and its backup, preferably on a dual-ported SCSI disk or on a Storage Area Network (SAN).

Setting the Transaction Log File Write Policy

1. Click the server node in the left pane and select a server.

2. In the right pane, select the Logging tab and then the JTA tab.

3. Select a Transaction Log File Write Policy: Cache-Flush (the default) or Direct Write.

4. Click Apply to save the attribute setting. The new transaction log file write policy takes effect after you restart the server.

Warning: On Windows, the Direct-Write transaction log file write policy may leave transaction data in the on-disk cache without immediately writing it to disk. This is not transactionally safe because a power failure can cause loss of on-disk cache data. To prevent cache data loss when using the Direct-Write transaction log file write policy on Windows, disable all write caching for the disk (enabled by default) or use a battery backup for the system.

To disable the on-disk cache for a hard disk on Windows, do the following: Start -> Settings -> Control Panel -> System -> Hardware tab -> click the Device Manager button -> Disk Drives -> double-click the drive name -> Disk Properties tab -> clear the Write Caching Enabled check box. Some file systems, however, do not allow this value to be changed (for example, a RAID system that has a reliable cache).

Specifying the JDBC Log File

1. Click the Server node in the left pane.

2. Select a specific server in the left pane.

3. Select the Logging tab.

4. Select the JDBC tab.

5. Select Enable JDBC Logging.

6. Enter a log file name.

7. Click Apply to save the settings.

Specifying General Log File Settings

1. Click the Server node in the left pane.

2. Select a specific server in the left pane.

3. Select the Logging tab.

4. Select the General tab.

5. Enter a log file name.

   For information about including a time and date stamp in the name of rotated log files, refer to the next section, Specifying Log File Rotation.

6. Choose the severity threshold of the messages you want to view. For information about message severity, refer to Message Severity in the WebLogic Server Administration Guide.

7. Click Apply to save the setting.

Specifying Log File Rotation

1. Click the Server node in the left pane and select a specific server in the left pane.

2. Select the Logging tab. Then select the Rotation tab.

3. On the Rotation tab, 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 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, specifiy 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 deletes the oldest log file and creates a new log file with the latest suffix.

   4. Click Apply.

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

   1. In Rotation Type, choose By Time.

   2. In Rotation Time, enter the start time.

      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 deletes the oldest log file and creates a new log file with the latest suffix 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:
   myserver_%yyyy%_%MM%_%dd%_%hh%_%mm%.log

   the server's log file will be named:
   myserver_yyyy_MM_dd_hh_mm.log

   When the server instance rotates the log file, the rotated file name contains the date stamp. For example, if the server instance rotates its local log file on 2 April, 2003 at 10:05 AM, the log file that contains the old log messages will be named:
   myserver_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: myserver.log00007.

Specifying Domain Logging

1. Click the Server node in the left pane.

2. Select a server in the left pane.

3. Select the Logging tab.

4. Select the Domain tab.

5. To enable this server to send messages to the domain log (in addition to its own log), select the Log to Domain Logfile checkbox.

6. By default, the server sends only the log messages of an ERROR or higher severity to domain log. If you want to send a different set of messages, from the Domain Log Filter list, choose a domain log filter.

   The Domain Log Filter list contains all filters that have been defined for the domain. For information about defining domain log filters, refer to Creating a New Domain Log Filter.

7. Click Apply.

Specifying HTTP Log File Settings for a Server

1. Click the Server node in the left pane. Then select a specific server in the left pane.

2. Select the Logging tab.

3. On the HTTP tab, click Enable Logging to activate or deactivate HTTP logging. (If Enable Logging is checked, the HTTP logging will be activated.)

   HTTP requests are kept in a log file that is separate from the server log file.

4. Determine the format of the HTTP log file by selecting Common or Extended from the Format list.

5. To determine the frequency with which the server empties its HTTP-request buffer and writes the data to the HTTP log file, do the following:

   1. In Log Buffer Size, specify the maximum size (in kilobytes) of the HTTP-request buffer.

   2. In the Flush Every parameter, specify the interval (in seconds) at which the server checks the size of the HTTP-request buffer. If the buffer has reached the maximum size, the server writes the data to the HTTP log file.

6. If you want the server to move old HTTP requests to another file when the current HTTP log file reaches a specific size, do the following:

   1. In Rotation Type, choose size.

   2. In Max Log File SizeK Bytes, specifiy 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 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. Click Apply.

7. If you want the server to create another file at specific time intervals, do the following:

   1. In Rotation Type, choose date.

   2. In Rotation Time, enter the start time.

      At the time that you specify, the server rotates the current HTTP 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 Rotation Period.

      Use the following java.text.SimpleDateFormat format to specify a date and time: MM-dd-yyyy-k:mm:ss. For information about this format, refer to the J2EE Javadoc.

   3. In Rotation Period, enter the interval (in minutes) at which the server saves old messages to another file.

   4. Click Apply.

8. 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:
   access_%yyyy%_%MM%_%dd%_%hh%_%mm%.log

   the HTTP log file will be named:
   access_yyyy_MM_dd_hh_mm.log

   When the server instance rotates the HTTP log file, the rotated file name contains the date stamp. For example, if the server instance rotates the HTTP log file on 2 April, 2003 at 10:05 AM, the log file that contains the old log messages will be named:
   access_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: myserver.log00007.

Configuring Debug Information in the Server Log File

1. Click the Server node in the left pane.

2. Select a specific server in the left pane.

3. Select the Logging tab.

4. Select the Debugging tab.

5. Fill in the fields as appropriate.

6. Click Apply to save the setting.

Server Monitoring Tasks

Viewing the Server JNDI Tree

1. Right-click the instance node in the left pane under Servers for the server whose JNDI tree you want to view. This opens a pop-up menu.

2. Click View JNDI Tree. A new browser window is displayed showing the naming context data.

Monitoring Transactions

1. Click the server node in the left pane.

2. Select a specific server in the left pane.

3. Select the Monitoring tab.

4. Select the JTA tab. Totals for transaction statistics are displayed in the JTA dialog.

5. Optionally, click the monitoring text links to monitor transactions by resource or by name, or to monitor all active transactions.

Monitoring "Stuck" Threads

1. Click the server node in the left pane.

2. Select a specific server in the left pane.

3. Select the Configuration tab.

4. Select the Tuning tab.

5. In the Stuck Thread Max Time field, enter the length of time, in seconds, that a thread must be continually working before this server diagnoses the thread as being stuck.

6. In the Stuck Thread Timer Interval field, enter the length of time, in seconds, after which WebLogic Server periodically scans threads to see if they have been continually working for the length of time specified by Stuck Thread Max Time.

7. Click Apply to apply your changes.

8. Reboot the server to use the new settings.

Monitoring Web App Components on a Server

1. Click the instance node in the left pane under Servers to select a server for web-application monitoring. A dialog displays in the right pane showing the tabs associated with this instance.

2. Click the Deployments tab.

3. Click the Web Applications tab.

4. Click the Monitor All Active Web Applications text link. The web applications table displays in the right pane showing all the web applications deployed on this server.

Server/Domain Management Tasks

Replicating a Domain's Configuration Files

A Managed Server can replicate the domain's configuration files. If the Administration Server is unavailable, you can start the Managed Server using the replicated files.

Caution: Do not enable file replication for a server that shares an installation or root directory with another server. Unpredictable errors can occur for both servers.

To replicate a domain's configuration files on a server, do the following:

1. Click the server node in the left pane.

2. Select a specific server in the left pane.

3. From the Configuration tab, click the Tuning tab.

4. Click the MSI File Replication Enabled check box.

Disabling Managed Server Independence

By default, Managed Server Independence mode is enabled. To disable the mode, do the following:

1. Click the server node in the left pane.

2. Select a specific server in the left pane.

3. From the Configuration tab, click the Tuning tab.

4. Clear the Managed Server Independence Enabled check box.

Server Migration Tasks

Creating a Migratable Target

1. Select the Servers node in the left pane.

2. Select the name of a server that resides in the cluster you want to configure.

3. Select Control->Migration Config. in the right panel (or select Control->JTA Migration Config. to create a migratable target for JTA services). The right panel displays a list of servers that you can select as constrained candidate servers for the migratable target.

4. In the Available column, select all of the servers that can potentially host migratable services in the cluster. Use the arrow button to place these servers in the Chosen column.

5. Click Apply to apply your changes to the new migratable target.

Migrating Services to a New Server

1. Select the Servers node in the left panel.

2. Select the name of a server that resides in the cluster you want to work with.

3. Click the Control->Migrate tab to migrate JMS servers or click Control->JTA Migrate to migrate the JTA transaction recovery service.

4. Use the Destination Server drop-down list to select a server from the migratable target list.

5. Click Migrate... to migrate pinned services running on the Current Server to the Destination Server you selected. If you selected the JTA Migrate tab, note that the cluster migrates only the JTA service to the selected server.

jCom Configuration Tasks

Limiting the Size of a COM Message Packet WebLogic Server Accepts

1. Click the server node in the left pane.

2. Select a specific server in the left pane.

3. Select the Connections tab in the right pane.

4. Select the jCOM tab in the right pane.

5. In the COM Max Message Size field, enter the maximum size, in bytes, of a COM message WebLogic Server accepts.

6. Click Apply.

Limiting the Number of Seconds WLS Waits for a Complete COM Message

1. Click the server node in the left pane.

2. Select a specific server in the left pane.

3. Select the Connections tab in the right pane.

4. Select the jCOM tab in the right pane.

5. In the COM Message Timeout field, enter the time, in seconds, WebLogic Server waits to receive a complete COM message.

6. Click Apply.

Allowing or Disallowing COM Calls on the Server's Listen Port

1. Click the server node in the left pane.

2. Select a specific server in the left pane.

3. Select the Connections tab.

4. Select the jCOM tab.

5. Check the EnableCOM box to allow COM calls and uncheck the EnableCOM box to disallow COM calls.

6. Restart the server to effect this change.

Setting the Primary Domain Controller to be Used for Authentication

1. Click the server node in the left pane.

2. Select a specific server in the left pane.

3. Select the Connections tab.

4. Select the jCOM tab.

5. In the NTAuth Host field, enter the IP address of the primary domain controller to be used for authenticating clients.

6. Restart the server to effect this change.

Allowing or Disallowing Native Mode Communication

1. Click the server node in the left pane.

2. Select a specific server in the left pane.

3. Select the Connections tab.

4. Select the jCOM tab.

5. Check or uncheck the Native Mode Enabled Box.

6. Restart the server to effect this change.

Enabling or Disabling the Logging of Memory Usage

1. Click the server node in the left pane.

2. Select a specific server in the left pane.

3. Select the Connections tab.

4. Select the jCOM tab.

5. Check or uncheck the Memory Logging Enabled box.

6. Restart the server to effect this change.

Allowing Prefetching of Elements

1. Click the server node in the left pane.

2. Select a specific server in the left pane.

3. Select the Connections tab.

4. Select the jCOM tab.

5. Check or uncheck the Prefetch Enums box.

6. Restart the server to effect this change.

Allowing or Disallowing Apartment Threaded COM Initialization in Native Mode

1. Click the server node in the left pane.

2. Select a specific server in the left pane.

3. Select the Connections tab.

4. Select the jCOM tab.

5. Check or uncheck the Apartment Threaded box.

6. Restart the server to effect this change.