High Availability with WebLogic Clusters - Oracle WebLogic Server 12c Advanced Administration - page 70

4. Click on the PROD_AdminServer (admin) link to navigate to
General | Configuration of the Administration Server.
5. Type adminhost in the Listen Address field.
6. Click on the Save button and then on the Activate Changes button.
7. Shutdown all Server instances, including the Administration Server.
8. Start the Administration Server.
9. The Administration Console should now be accessible at http://adminhost.
domain.local:7001/console .
Copy the Administration Server files to all machines:
1. Log in as a wls user to prod01 shell and copy to the Administration Server directory
to prod02 :
[wls@prod01]$ cd $DOMAIN_HOME/servers
[wls@prod01]$ scp -rp PROD_AdminServer wls@prod02:$DOMAIN_HOME/
servers/
The Administration Server directory must always be updated on
all machines. A recent backup can also be restored when needed.
Remember to define a backup routine of your files.
2. Restart all instances and the configuration part is finished.
Starting the Administration Server on the prod02 machine:
1. In a situation where prod01 is unavailable, the adminhost.domain.local
hostname must be changed to point to the IP address of prod02 or the adminhost.
domain.local VIP should move to prod02 .
2. Log in as a wls user to the prod02 shell and start the Administration Server. Make
sure you use a recent copy of the Administration Server directory:
[wls@prod02]$ cd $DOMAIN_HOME/bin
[wls@prod02]$ nohup ./startWebLogic.sh &
3. The Administration Server is now running on prod02 and the Administration
Console is still accessible at the same address http://adminhost.domain.
local:7001/console .