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 Sun Cluster HA for BEA WebLogic Server. These requirements apply to Sun Cluster HA for BEA WebLogic Server only. You must meet these requirements before you proceed with your Sun Cluster HA for BEA WebLogic Server installation and configuration.
For requirements that apply to all data services, see “Configuration Guidelines for Sun Cluster Data Services” in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.
If the BEA WebLogic Server home directory and other config files are installed on a failover filesystem using HAStoragePlus, then all BEA WebLogic Server resources using that filesystem should be configured in the same resource group.
If the BEA WebLogic Server depends on any database such as Oracle or Sybase, the administrator must make sure that the database is highly available before configuring and starting the BEA WebLogic Server under Sun Cluster HA for BEA WebLogic Server.
In BEA WebLogic Server, the Managed Servers can be configured to start independently in “Managed Server Independence mode.” For Sun Cluster HA for BEA WebLogic Server, the administrator must configure all Managed Servers to be able to start independently.
To configure the Managed Server in the independent mode, see the relevant BEA WebLogic Server documentation for the version you are using. For example, for BEA WebLogic Server 7.0, the documentation is located at
You can configure separate scripts to start the BEA WebLogic Managed Servers. If separate scripts are configured, the Admin Server url and the Managed Server name must be set in the START script. The scripts should be able to start each BEA WebLogic Server instance without arguments.
If you intend to use a single START script to start several Managed Servers, the Admin 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 startMangedWeblogic.sh, then the Managed Server petstore_server should be able to start as follows:
node1>cd /global/beahome/weblogic700/domain/petstore node1>./startManagedWeblogic.sh petstore_server
The BEA WebLogic Server START script needs a username and password. You can configure a file boot.properties to store the username and password which is encrypted after the first startup of the BEA WebLogic Server. If the boot.properties file is used, Sun Cluster HA for BEA WebLogic Server will not be able to do a smooth shutdown of the BEA WebLogic Server because the username and password will be unavailable. During the Sun Cluster HA for BEA WebLogic Server shutdown, the STOP method will kill the BEA WebLogic Server process using sigkill. If a smooth shutdown (using java weblogic.Admin) is desired, the username and password must be configured using the BEA WebLogic Server variables WLS_USER and WLS_PW in the START script and the extension property Smooth_shutdown must be set to TRUE when the resource is created.
To enable smooth_shutdown at resource creation or by updating the resource, the BEA WebLogic Server variables WLS_USER and WLS_PW must be configured with the username and password accordingly. Otherwise, the associated server will not start under Sun Cluster.
Because the agent runs the server START script as root, all required environment variables must be set in the START script or set in a separate file and sourced by the START script before starting the server. For details, see the relevant BEA WebLogic Server documentation for the version you are using. For example, for BEA WebLogic Server 7.0, the documentation is located at
To enable the discovery of running Managed Servers after a failover and restart of an Administration Server, make sure 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 BEA WebLogic Server documentation for the version you are using. For example, for BEA WebLogic Server 7.0, the documentation is located at
Make sure that the hostnames 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 hostnames using DNS.