Note - For failover services, type the logical host name or its IP address when
configuring the WebLogic Servers.

For multi-master configurations, ensure that each managed server is configured to listen on
each logical hostname or its IP address.

After completing all necessary configuration for the domain, shut down the Administration Server.

Edit the Administration Server START script and the Managed Server START script by
setting the WLS_USER and WLS_PW.

The START scripts should be able to run without any arguments.

Note - To perform a smooth shutdown of the WebLogic Server, the boot.properties file
with a valid user name and password is required. You do not need
to set the WLS_USER and WLS_PW variables for a smooth shutdown if the
boot.properties file is available. This waiver applies only to WebLogic Server 8.1 or
later versions.

Note - Starting with WebLogic Server version 10.3, the boot.properties file must reside in
both the $DOMAIN_DIR and $DOMAIN_DIR/servers/server-name/security directories to bypass the need to prompt for
user credentials when starting and stopping instances of WebLogic Server. If the $DOMAIN_DIR/servers/server-name/security
directory does not exist or does not include a boot.properties file, create the
directory and copy the boot.properties file from the $DOMAIN_DIR. For more information about
the boot.properties file for WebLogic Server version 10.3, see http://download.oracle.com/docs/cd/E12840_01/wls/docs103/server_start/overview.html.

In the Managed Server START script, set the ADMIN_URL and the SERVER_NAME variables.

This script should be able to run without any arguments.

Set the necessary environment variables in the setWLSEnv.sh or the startWLS.sh scripts.

These environment variables include any additional CLASSPATH or LD_LIBRARY_PATH, etc. These scripts contain
all necessary environmental variables such as CLASSPATH and LD_LIBRARY_PATH.

Note - Starting with WebLogic Server version 10.3, the startWLS.sh script has been removed.
Therefore, these environment settings must be made only in the setWLSEnv.sh script.

For versions of WebLogic Server before 10.3, verify that the config.xml file is
in the same directory as the START scripts.

For a multi-master configuration of WebLogic Server installed on a local file
system, replicate the domain and Managed Servers across the cluster.

Use the pack.sh command to create a template of the domain and
Managed Servers that you created.

Copy the template to other Oracle Solaris Cluster nodes.

Use the unpack.sh command to unpack the template to create the domain and
Managed Servers.

Installing a Database

If you are using a database with WebLogic Server, install the database by
using its installation documentation. If the database that you are using has a
highly available agent on Oracle Solaris Cluster, install that version.

Installing a Web Server

If you are using a web server with WebLogic Server, install the
web server by using its installation documentation. If the web server that you are
using has a highly available agent on Oracle Solaris Cluster, install that version.