This section contains the information you need to plan your Sun Cluster HA for BEA WebLogic Server installation and configuration.
Your data service configuration might not be supported if you do not observe these restrictions.
This section provides a list of software and hardware configuration restrictions that apply to Sun Cluster HA for BEA WebLogic Server. Use the restrictions in this section to plan the installation and configuration of Sun Cluster HA for BEA WebLogic Server.
For restrictions that apply to all data services, see the Sun Cluster Release Notes for Solaris OS.
Sun Cluster HA for BEA WebLogic Server provides high availability to stand alone BEA WebLogic Server instances (instances not using BEA WebLogic Server clustering).
For a Failover Filesystem, all BEA WebLogic Server instances using that filesystem must be configured in a single resource group.
If the user wants to configure different instances in different resource groups, the BEA WebLogic Server installation must be on a Global File System.
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 configuration 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
http://e–docs.bea.com/wls/docs70/admin_domain/failures.html#1104833 |
You can configure separate scripts to start the BEA WebLogic 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 BEA 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 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 user name and password. You can configure a file boot.properties to store the user name and password which are 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 perform a smooth shutdown of the BEA WebLogic Server because the user name 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. To ensure a smooth shutdown (by using Java weblogic.Admin), you must configure the user name and password by 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 user name and password accordingly. Otherwise, the associated server will not start under Sun Cluster. This information applies only to BEA WebLogic Server 7.x or earlier versions.
In BEA WebLogic Server 8.1 or later versions, you can perform a smooth shutdown without adding the user name and password to the START script. For BEA WebLogic Server 8.1 or later versions, the boot.properties file must be present in the $DOMAIN_DIR directory for smooth shutdown. The user name and password do not need to be configured by adding the BEA WebLogic Server variables WLS_USER and WLS_PW to the START script. If the extension property smooth_shutdown is set to TRUE, the boot.properties file must be present in the $DOMAIN_DIR directory.
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
http://e-docs.bea.com/wls/docs70/adminguide/startstop.html#1086359 |
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
http://e-docs.bea.com/wls/docs70/admin_domain/failures.html#1104811 |
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.
Use the standard configurations in this section to plan the installation and configuration of Sun Cluster HA for BEA WebLogic Server. Sun Cluster HA for BEA WebLogic Server supports the standard configurations in this section.
In addition to the standard configurations provided in this section, the following BEA WebLogic Server configurations are possible.
Separate START script for each BEA WebLogic Server (Administration and Managed)
Single START script for all Managed Servers which takes the Managed Server name as the input
Setting the user name and password in the boot.properties file
This configuration enables a smooth shutdown by Sun Cluster HA for BEA WebLogic Server 8.1 or later versions.
Setting the user name and password in the START script
This configuration enables a smooth shutdown by Sun Cluster HA for BEA WebLogic Server 7.x or earlier versions.
The BEA WebLogic Server is currently supported as a failover data service.
Sun Cluster HA for BEA WebLogic Server might support additional configurations. However, you must contact your Sun service provider for information about additional configurations.
This simple configuration for Sun Cluster HA for BEA WebLogic Server uses two resource groups configured as follows.
RG1 containing logical-host-1 and WLS-Admin-Server-resource
RG2 containing logical-host-2 and WLS-Managed-Server-resource
RG1 and RG2 are failover resource groups.
This configuration is possible only if the BEA WebLogic Server is installed on a global file system. See Figure 1 for an illustration of this configuration.
In this configuration, RG1, RG2, RG3, and RG4 are failover resource groups configured as follows.
RG1 containing logical-host-1 and WLS-Admin-resource
RG2 containing logical-host-2 and WLS-Managed-Server-resource2
RG3 containing logical-host-3 and WLS-Managed-Server-resource3
RG4 containing logical-host-4 and WLS-Managed-Server-resource4
This configuration is possible only if the BEA WebLogic Server is installed on a global file system.
In this configuration, RG1, RG2, and RG3 are failover resource groups configured as follows.
RG1 containing logical-host-1, WLS-Admin-resource, and WLS-Managed-Server-resource1
RG2 containing logical-host-2, WLS-Managed-Server-resource2, WLS-Managed-Server-resource3, and WLS-Managed-Server-resource4
RG3 containing logical-host-3, WLS-Managed-Server-resource5, WLS-Managed-Server-resource6, WLS-Managed-Server-resource7
This configuration is possible only if the BEA WebLogic Server is installed on a global file system.
If the BEA WebLogic Server is installed on a failover file system by using HAStoragePlus, all the BEA WebLogic Server instances must be configured in the same failover resource group that has a dependency on the failover file system.
RG1 contains logical-host-resource resources and all Administration and Managed-Server resources.
For information about how to register a resource with dependency on an HAStoragePlus resource, see Enabling Highly Available Local File Systems in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.
See Figure 2 for an illustration of this configuration.