Technical data

Starting the WebLogic Administration Server
Administration Guide 2-13
n Change the value of the variable JAVA_HOME to the location of your JDK.
n UNIX users must change the permissions of the sample UNIX script to make the
file executable. For example:
chmod +x startWebLogic.sh
n If you are going to run a Managed Server in the same domain on another
machine (or on a multi-homed machine with the Administration Server), or want
to be able to start and kill Managed Servers using the Node Manager, you will
need to edit the WebLogic Server startup command by adding the argument to
set the listen address of the Administration Server:
-Dweblogic.ListenAddress=host
where host is the DNS name or IP address of the Administration Server.
Restarting the Administration Server when Managed
Servers are Running
For a typical production system it is recommended that you not deploy applications
containing your critical business logic on the Administration Server. In such a
scenario, the role of the Administration Server is that of configuring and monitoring
the Managed Servers. If the Administration Server should become unavailable in such
a configuration, the applications running on the Managed Servers can continue to
process client requests.
When the Administration Server is started, it makes a copy of the configuration file
that was used to boot the active domain. This is saved in the file
install_dir/config/domain_name/config.xml.booted
where install_dir is the directory where you installed the WebLogic Server
software and
domain_name is the name of the domain. The Administration Server
creates the
config.xml.booted file only after it has successfully completed its
startup sequence and is ready to process requests.
You should make a copy of this file so that you have a working configuration file that
you can revert to if you need to back out of changes made to the active configuration
from the Administration Console.