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

Configuring high availability for
Administration Server
The Administration Server is a single WebLogic Server instance responsible for the
configuration and management of the WebLogic domain. By default, the Administration
Server runs on the machine that the domain was created.
Unlike WebLogic clustering, WebLogic Server does not provide out of the box high availability
options for the Administration Server, if this machine fails.
Thanks to the Managed Servers Independence Mode (MSI) Managed
Servers will keep running even if the Administration Server is down.
Managed Servers can also be started by using only Node Manager
and WLST or by using the start-up shell scripts without the need of the
Administration Server.
This recipe will provide the steps to prepare the environment in case the machine that hosts
the Administration Server fails.
Getting ready
By default, the Administration Server binds to all IP addresses of the machine, but sets the
prod01 machine as its default hostname.
The first step is to set the Listen Address field to a unique hostname or alias decoupled
from the original hostname of the machine. This recipe will use a new hostname adminhost.
domain.local , which will initially point to the IP Address of prod01 machine or to a VIP to
prod01 that can be migrated later.
Also a copy of the Administration Server directory must be provisioned on all machines in the
domain so the Administration Server can be started on one of them when needed.
How to do it...
Change the Administration Server Listen Address value:
1. Access the Administration Console with your web browser at http://prod01.
domain.local:7001/console .
2. Click on the Lock & Edit button to start a new edit session.
3. Expand the Environment tree on the left and click on Servers.