Configuration Requirements

Language:

Caution - Your data service configuration might not be supported if you do not adhere to these requirements.

Use the requirements in this section to plan the installation and configuration of HA for WebLogic Server. These requirements apply to HA for WebLogic Server only. You must meet these requirements before you proceed with your HA for WebLogic Server installation and configuration.

For requirements that apply to all data services, see Configuration Guidelines for Oracle Solaris Cluster Data Services in Oracle Solaris Cluster Data Services Planning and Administration Guide .

If the WebLogic Server home directory and other configuration files are installed on a failover file system using HAStoragePlus, then all WebLogic Server resources using that file system should be configured in the same resource group.
If the WebLogic Server depends on any database, such as Oracle or Sybase, the administrator must ensure that the database is highly available before configuring and starting the WebLogic Server under Oracle Solaris Cluster HA for WebLogic Server.
In WebLogic Server, the Managed Servers can be configured to start independently in “Managed Server Independence mode.” For the HA for WebLogic Server, the administrator must configure all Managed Servers to be able to start independently.
To configure the Managed Server in independent mode, see the relevant WebLogic Server documentation for the version you are using. For example, for WebLogic Server 12c, the documentation is located at http://docs.oracle.com/middleware/1212/wls/index.html.
You can configure separate scripts to start the WebLogic Server Managed Servers. If separate scripts are configured, the Administration Server URL and the Managed Server name must be set in the START script. The scripts should be able to start each WebLogic Server instance without arguments.
If you intend to use a single START script to start several Managed Servers, the Administration URL must be specified in the START script and only the Managed Server name should be taken as the argument to the script. For example, if the script used to start the Managed Server is startManagedWeblogic.sh, then the Managed Server petstore_server should be able to start as follows:
```
node1>cd /global/wls/user_projects/petstore
node1>./startManagedWeblogic.sh petstore_server
```
The WebLogic Server START script needs a user name and password. You configure the $DOMAIN_DIR/boot.properties file to store the user name and password which are encrypted after the first startup of the WebLogic Server. The $DOMAIN_DIR/boot.properties file also enables a smooth shutdown when used with a resource for which the extension property smooth_shutdown is set to TRUE.
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 12c, see http://docs.oracle.com/middleware/1212/wls/START/overview.htm#START112.
All required environment variables must be set in the WebLogic Server environment file before you start the server. For details about the WebLogic Server environment file, see the relevant WebLogic Server documentation for the version you are using. For example, for WebLogic Server 12c, the documentation is located at http://docs.oracle.com/middleware/1212/wls/index.html. To set the path to the WebLogic Server environment file, use the Environment_File property described in Appendix A, HA for WebLogic Server Extension Properties.
To enable the discovery of running Managed Servers after a failover and restart of an Administration Server, ensure that the Administration server START script does not include -Dweblogic.management.discover+=false. This setting disables the Administration Server from discovering its running Managed Servers. For details, see the relevant WebLogic Server documentation for the version you are using. For example, for WebLogic Server 12c, the documentation is located at http://docs.oracle.com/middleware/1212/wls/index.html.
Ensure that the host names used in the Server_url and monitor_uri_list are resolvable. If you use Fully Qualified Domain Names (FQDNs), then DNS must be enabled and /etc/nsswitch.conf must have the correct entries to resolve the host names using DNS.
Note - To avoid any failures due to delays in name-service lookup, the host name used in the Server_url property should be added to the /etc/hosts file. Configure name-service mapping in the /etc/nsswitch.conf file on the servers to first check the local files before trying to access other name services.