Skip Navigation Links | |
Exit Print View | |
![]() |
Oracle Solaris Cluster Data Service for Oracle WebLogic Server Guide Oracle Solaris Cluster 4.0 |
1. Installing and Configuring Oracle Solaris Cluster HA for WebLogic Server
Oracle Solaris Cluster HA for WebLogic Server Overview
Planning the Oracle Solaris Cluster HA for WebLogic Server Installation and Configuration
Standard Data Service Configurations
WebLogic Server Configured as a Failover Resource
WebLogic Server Configured as a Multi-Master Resource
How to Prepare the Nodes for a Failover Configuration
How to Prepare the Nodes for a Multi-Master Configuration
Installing and Configuring the WebLogic Server Application
How to Install WebLogic Server
Verifying the WebLogic Server Installation and Configuration
How to Verify the WebLogic Server Installation and Configuration for Failover Services
How to Verify the WebLogic Server Installation and Configuration for Multi-Master Services
Installing the HA for WebLogic Server Package
How to Install the HA for WebLogic Server Package
Registering and Configuring the Oracle Solaris Cluster HA for WebLogic Server
Setting Oracle Solaris Cluster HA for WebLogic Server Extension Properties
Setting Up the WebLogic Server for HAStoragePlus Configuration
How to Set Up the WebLogic Server on Zone Clusters for HAStoragePlus Configuration
Verifying the Oracle Solaris Cluster HA for WebLogic Server Installation and Configuration
Alternate Oracle Solaris Cluster HA for WebLogic Server Configurations
Creating a Simple WebLogic Server Resource
Creating a Resource With a Server Name Argument
Creating a Resource That Shuts Down Smoothly
Creating a Resource That Probes the Database
Creating a Resource That Monitors URIs
Using a Non-Clustered Managed Server Instance as a Proxy Server
Operation of the Oracle Solaris Cluster HA for WebLogic Server Fault Monitor
Probing Algorithm and Functionality
This section contains the procedures that you need to configure Oracle Solaris Cluster HA for WebLogic Server.
The sections that follow contain instructions for registering and configuring Oracle Solaris Cluster HA for WebLogic Server resources. For information about the extension properties, see Appendix A, HA for WebLogic Server Extension Properties. The Tunable entry indicates when you can update a property.
For details about all the Oracle Solaris Cluster properties, see the following man pages: cluster(1CL), rt_properties(5), r_properties(5), and rg_properties(5).
To set an extension property of a resource, include the following option in the clresource(1CL) command that creates or modifies the resource:
-p property=value
Identifies the extension property that you are setting.
Specifies the value to which you are setting the extension property.
You can also use the procedures in Chapter 2, Administering Data Service Resources, in Oracle Solaris Cluster Data Services Planning and Administration Guide to configure resources after the resources are created.
You can configure your WebLogic Server running as a web proxy server in a failover configuration. The procedure below assumes that you have completed the following steps:
You are using one of the configurations described in Standard Data Service Configurations.
You have configured the WebLogic Servers as described in Installing and Configuring the WebLogic Server Application
You have created a resource group for running WebLogic Server as a web proxy server.
You have started an administration server and a managed server either inside or outside the agent's control.
This configuration does not enable a smooth shutdown. The Oracle Solaris Cluster HA for WebLogic Server stop method forces the shutdown of the WebLogic Server, and kills the process. See Creating a Resource That Shuts Down Smoothly for instructions on enabling a smooth shut down. For more information, see STOP Method.
Follow the instructions on the Oracle download site.
# clresourcetype register SUNW.wls
# clresource create -g wls-proxy-rg -t SUNW.wls -p Confdir_list=/global/bea/beahome/weblogic103 -p Server_url=http://logical-host-2:portnumber -p Start_script=/global/bea/beahome/user_projects/petstore/startManagedWebLogic.sh -p resource_dependencies=wls-mgd1-rs,wls-mgd2-rs.... wls-proxy-rs
Note - If you are running managed server instances outside agent control, ensure that the managed server instances are running. If you are running the managed server instances under the agent control, add the managed server resources that are configured in the web proxy server configuration under the resource_dependencies property. This ensures that the managed server resources are online before bringing the proxy server resource online.
Use this procedure to configure Oracle Solaris Cluster HA for WebLogic Server as a failover data service. The following steps assume that you are using the failover configuration that is described in Standard Data Service Configurations and have configured the WebLogic Servers as mentioned in Installing and Configuring the WebLogic Server Application. These steps assume that you have already created resource groups RG1 and RG2 and have also created logical-host-1 and logical-host-2 resources in these resource groups. Refer to How to Prepare the Nodes for a Failover Configuration for procedures to create logical hostname resources. If you are planning a different configuration, you must configure the WebLogic Server resources accordingly.
Note - Before you start Oracle Solaris Cluster HA for WebLogic Server, if you are using a database, check that your database is accessible.
# clresourcetype register SUNW.wls
# clresource create -g RG1 -t SUNW.wls \ -p Confdir_list=/global/bea/beahome/weblogic700 \ -p Server_url=http://logical-host-1:7001 \ -p Start_script=/global/bea/beahome/user_projects/petstore/startWebLogic.sh admin-rs
The resource is created in the enabled state.
Note - This configuration does not enable smooth shutdown. The Oracle Solaris Cluster HA for WebLogic Server stop method forces the shutdown of the WebLogic Administration Server (kills the process). Refer to Creating a Resource That Shuts Down Smoothly for the configuration to enable smooth shutdown. For more information, see STOP Method.
# clresource create -g RG2 -t SUNW.wls \ -p Confdir_list=/global/bea/beahome/weblogic700 \ -p Server_url=http://logical-host-2:7004 \ -p Start_script=/global/bea/beahome/user_projects/petstore/startManagedWebLogic.sh managed-rs
The resource is created in the enabled state.
Use this procedure to configure Oracle Solaris Cluster HA for WebLogic Server in a multi-master configuration. The following steps assume that you are using the configuration that is described in WebLogic Server Configured as a Multi-Master Resource and have configured the WebLogic Servers as mentioned in Installing and Configuring the WebLogic Server Application. These steps assume that you have already created a resource group and started the administration server either outside or inside the agent control. If you are planning a different configuration, you must configure the WebLogic Server resources accordingly.
Note - This configuration does not enable smooth shutdown. The Oracle Solaris Cluster HA for WebLogic Server stop method forces the shutdown of the WebLogic Server (kills the process). Refer to Creating a Resource That Shuts Down Smoothly for the configuration to enable smooth shutdown in a multi-master configuration. For more information, see STOP Method.
# clresourcetype register SUNW.wls
Note - The Server_url must be set to localhostport-number because the managed server instances are listening on all local addresses.
The following example starts the WebLogic Server managed server instances mgd1 on node1 and mgd2 on node2.
# clresource create -t SUNW.wls -g mdg-rg \ -p Confdir_list=/local/bea/beahome/wlserver_10.3 \ -p Server_url=http://localhost:port-number \ -p Start_script=/local/bea/beahome/user_projects/domains/base_domain_mgd1 \ /bin/startManagedWebLogic.sh \ -p "Server_name{node1}"=mgd1 \ -p "Server_name{node2}"=mgd2 \ -p smooth_shutdown=true managed-rs
Tip - You can create the resource in the global cluster or in a zone cluster. To create a resource in the specific zone cluster from the global cluster, use the -Z option to specify the name of the zone cluster.