Restarting an Administration Server on the Same Machine

8-8 Oracle WebLogic Communications Server Administration Guide Make sure that the startup command or startup script does not include -Dweblogic.management.discover=false, which disables an Administration Server from discovering its running Managed Servers. When the Administration Server starts, it communicates with the Managed Servers and informs them that the Administration Server is now running on a different IP address.

8.1.4 Restarting Failed Managed Servers

If the machine on which the failed Managed Server runs can contact the Administration Server for the domain, simply restart the Managed Server manually or automatically using Node Manager. Note that you must configure Node Manager and the Managed Server to support automated restarts. If the Managed Server cannot connect to the Administration Server during startup, it can retrieve its configuration by reading locally-cached configuration data. A Managed Server that starts in this way is running in Managed Server Independence MSI mode. To start up a Managed Server in MSI mode: 1. Ensure that the following files are available in the Managed Servers root directory: – msi-config.xml – SerializedSystemIni.dat – boot.properties If these files are not in the Managed Servers root directory: a. Copy the config.xml and SerializedSystemIni.dat file from the Administration Servers root directory or from a backup to the Managed Servers root directory. b. Rename the configuration file to msi-config.xml. When you start the server, it will use the copied configuration files.

2. Start the Managed Server at the command line or using a script.

The Managed Server will run in MSI mode until it is contacted by its Administration Server. For information about restarting the Administration Server in this scenario, see Section 8.1.3, Restarting a Failed Administration Server .

8.2 Overview of Failover Detection

In a production system, engine tier servers continually access SIP data tier replicas in order to retrieve and write call state data. The Oracle WebLogic Communication Services architecture depends on engine tier nodes to detect when a SIP data tier server has failed or become disconnected. When an engine cannot access or write call state data because a replica is unavailable, the engine connects to another replica in the same partition and reports the offline server. The replica updates the current view of Note: Alternatively, use the -Dweblogic.RootDirectory=path startup option to specify a root directory that already contains these files.