Technical data

Starting the WebLogic Administration Server
Administration Guide 2-3
Failover Considerations for the Administration Server
Because the Administration Server contains the configuration repository
(
config.xml), security files, and application files for your domain, you should keep
an archived copy of these files in case a failure of the Administration Server causes
them to become unavailable. Common methods of archiving include periodic
back-ups, fault tolerant disks, and manually copying files whenever they are changed.
Remember that any configuration changes you make to Weblogic Server, either by
using the Administration Console, the
weblogic.admin command, or the JMX API
are persisted in the
config.xml file.
To provide for quick failover in case of an Administration Server crash or other failure,
you may wish to create another instance of the Administration Server on a different
machine that will be ready to use if it the original Administartion Server fails.
As long as you have back ups of your configuration, security, and application files, you
can safely restart the Administration Server on another machine without interrupting
the functioning of the Managed Servers. For instructions, see “Restarting the
Administration Server when Managed Servers are Running” on page 2-13.
Starting the WebLogic Administration
Server
There are several ways in which the WebLogic Administration Server can be started:
n From the command line
The command to start the WebLogic Server can be either typed in a command
shell manually or it can be placed in a script to avoid retyping the command
each time the server is started. For information on the sample scripts provided
see Starting the WebLogic Managed Servers Using Scripts.
n From the Start Menu (Windows only)
n A WebLogic Server installed as a Windows service will start automatically when
the computer is rebooted.