Restarting an Administration Server on Another Machine

4-6 Managing Server Startup and Shutdown for Oracle WebLogic Server

4.4.1.2 Restarting an Administration Server on Another Machine

If a machine crash prevents you from restarting the Administration Server on the same machine, you can recover management of the running Managed Servers as follows: 1. Install the WebLogic Server software on the new administration machine if this has not already been done. 2. Make your application files available to the new Administration Server by restoring them from backups or by using a shared disk. Your application files should be available in the same relative location on the new file system as on the file system of the original Administration Server. DNS name or IP address of the host 1. If you are starting AS on a different machine with the same IP address: a. Install WebLogic Server. b. Move data. 2. Start the Administration Server. Running MSs will reconnect automatically at the next AdminReconnectIntervalS ecs . 3. To start an MS that was not running when AS failed, no change in command is required. 1. Install WebLogic Server. 2. Move data. 3. Update the config.xml with the IP address of the new host machine. See Section 4.4.1.2, Restarting an Administration Server on Another Machine. 4. Start the Administration Server. MSs that were running when AS went down, will not reconnect because they know only the previous Administration Server URL. See Section 4.4.1.3, Managed Servers and the Re-started Administration Server. Restart MSs supplying the new AS listen address or DNS name on the command line. 5. To start an MS that was not running when AS failed, supply the new AS listen address or DNS name on the command line. DNS name mapped to multiple hosts 1. If you are starting AS on a different machine with the same IP address: a. Install WebLogic Server. b. Move data. 2. Start the Administration Server. Running MSs will reconnect automatically at the next AdminReconnectIntervalS ecs . 3. To start an MS that was not running when AS failed, no change in command is required. 1. Install WebLogic Server. 2. Move data. 3. Update the config.xml with the IP address of the new host machine. See Section 4.4.1.2, Restarting an Administration Server on Another Machine. 4. Start the Administration Server. Running MSs that were started with a DNS name for the Administration Server URL that maps to multiple IPs, will attempt reconnection to AS on all the available URLs. MSs can then locate the AS that has been restarted at any of the URLs. 5. To start an MS that was not running when AS failed, supply the DNS name on the command line. Table 4–2 Cont. Administration Server Restart Scenarios Listen Address Definition Same Machine or Different Machine with Same IP Address Different Machine with Different IP Address Avoiding and Recovering From Server Failure 4-7 3. Make your configuration and security data available to the new administration machine by restoring them from backups or by using a shared disk. For more information, refer to Section 4.2, Directory and File Backups for Failure Recovery . ■ Update the config.xml with the IP address of the new host machine. If the listen address was set to blank, you do not need to change it. For example: server nameAdminServername ... listen-addresslisten-address server ■ You can edit config.xml manually or use WLST offline to update the listen address. 4. Restart the Administration Server on the new machine.

4.4.1.3 Managed Servers and the Re-started Administration Server