| Skip Navigation Links | |
| Exit Print View | |
|
Oracle Solaris Cluster Data Services Reference Manual |
scalable_asm_instance_proxy(5)
SUNW.scalable_asm_instance_proxy(5)
- resource type implementation for failover and multiple masters Sun Java System Application Server (s1as)
The SUNW.s1as resource type represents the Sun Java System Application Server application in an Oracle Solaris Cluster configuration.
You must set the following properties on an SUNW.s1as resource by using scrgadm(1M).
See r_properties(5) for a complete description of the following resource properties.
A list of logical-hostname or shared-address network resources upon which this resource has a dependency. This list contains all network-address resources that appear in the properties Resource_dependencies, Resource_dependencies_weak, Resource_dependencies_restart, or Resource_dependencies_offline_restart.
This property is updated automatically by the RGM, based on the setting of the resource-dependencies properties. You do not set this property directly. Instead, use the Resource_dependencies property.
Conditional/Optional
The empty list
Any time
Specifies a list of resources upon which a resource depends. This list includes any logical-hostname or shared-address network resources that are used by a resource. The default value for this property is null.
You can specify one or more resource names. Each network resource can contain one or more logical host names. See the clreslogicalhostname(1CL) and clressharedaddress(1CL) man pages for more information.
You can specify an alternate kind of dependency by using the Resource_dependencies_weak, Resource_dependencies_restart, or Resource_dependencies_offline_restart property instead of the Resource_dependencies property. For more information, see the r_properties(5) man page.
Optional
The empty list
Any time
Default: No default
Tunable: Any time
Default: 2
Tunable: Any time
Default: 480
Tunable: Any time
Default: 120
Tunable: Any time
Type string array. This property is a path name set to install-dir/domains/domain/server which is the path name of an s1as instance directory. You must specify this property at resource creation time.
Type string array; defaults to "". This property allows you to ensure that application components are responding by querying the configured URIs. The Monitor_Uri_List property is used for detailed fault monitoring of Sun Java System Application Server. The fault monitor periodically performs HTTP GET command for the URIs. The monitor takes action if the HTTP request returns with response code 500 "Internal Server Error" or if the application server does not respond. An example URI setting is http://logical-hostname/App/tester. If the configured URIs are implemented by using a Servlet in the application server, detailed monitoring of the application server JVM (Java Virtual Machine) is possible. Either the Monitor_Uri_List or the Network_Resources_Used and the Port_List properties must be set. If Network_Resources_Used, Port_List, and Monitor_Uri_List are all set, the fault monitor will probe the ports and the URIs provided. Setting Port_List to include the IIOP listeners helps to ensure that the application server is listening and responding to IIOP requests.
Type string; defaults to 120 seconds. This property is tunable anytime and sets the timeout value for the probe.
Example 1 Creating a Failover s1as Resource in an Existing Group
For this example to work, you must first install the SUNWscs1as data service package. This example creates a failover s1as resource named appsrv-rs in an existing resource group named appsrv-rg. The appsrv-rg resource group contains a LogicalHostname resource, which identifies the logical hostname associated with the resource group.
(Register the SUNW.s1as resource type.) # scrgadm -a -t SUNW.s1as (Create a Sun Java System Application Server resource and add it to the resource group.) # scrgadm -a -j appsrv-rs -g appsrv-rg \\ -t SUNW.s1as \\ -x Confdir_list=/global/appsrv/domains/scdomain/server1 \\ -y Network_resources_used=schost-1 \\ -y Port_list=80/tcp,3700/tcp \\ -x Monitor_Uri_list=http://schost-1:80/servlet/monitor
In the preceding example, the s1as resource created is named appserver-rs, with a corresponding s1as instance in the directory /global/appsrv/domains/scdomain/server1.
Example 2 Creating a Failover s1as Resource Listening on a Specified Port
For this example to work, you must first install the SUNWscs1as data service package. This example creates a failover s1as resource named appserver-secure, which listens on port 443 in an existing resource group named app-rg.
example# scrgadm -a -t SUNW.s1as example# scrgadm -a -j appserver-secure -t SUNW.s1as -g app-rg -x Confdir_list=/global/s1as/domains/domain1/server2 -y Network_resources_used=schost-1 -x Monitor_Uri_list=http://schost-1:80/servlet/monitor -y Port_list=443/tcp
Example 3 Configuring s1as in a Scalable Resource Group
In this example a scalable resource group, s1as-rg, is created with Maximum_primaries and Desired_primaries equal to three. A Sun Java System Application Server resource named scalable-app-server1 is then created in this resource group with a configuration directory of /global/s1as/domains/domain1/server1 . The URI http://localhost:8000/servlets/testservlet is specified to the extension property Monitor_uri_list.
example# scrgadm -a -g s1as-rg -y Maximum_primaries=3 -y Desired_primaries=3 example# scrgadm -a -g s1as-rg -j scalable-app-server1 -t SUNW.s1as -x Confdir_list=/global/s1as/domains/domain1/server1 -x Monitor_uri_list=http://localhost:8000/servlets/testservlet
See attributes(5) for descriptions of the following attributes:
|
scrgadm(1M), scswitch(1M), scha_resource_get(3HA), pmfadm(1M), attributes(5), r_properties(5), scalable_service(5)
Oracle Solaris Cluster Data Service for Sun Java System Application Server Guide, and Oracle Solaris Cluster Data Services Planning and Administration Guide
|