How to Register and Configure an SAP J2EE Engine Resource

1. Become superuser on one of the nodes in the cluster that is to host the SAP J2EE engine.

2. Register SUNW.gds, the resource type for the SAP J2EE engine.

   # scrgadm -a -t SUNW.gds

   -a

   Specifies that a new resource type is to be added.

   -t SUNW.gds

   Specifies the name of the resource type to be added. This name is predefined for the SAP J2EE engine.

3. Create an HAStoragePlus resource for the SAP J2EE engine disk storage.

   # scrgadm -a -j hsp-j2ee-rs -g j2ee-rg -t SUNW.HAStoragePlus \ -x filesystemmountpoints="mountpoint-list"

   -a

   Specifies that a new configuration is to be added.

   -j hsp-j2ee-rs

   Specifies the name of the resource that you are creating.

   -g j2ee-rg

   Specifies that the resource is to be added to the SAP J2EE engine resource group.

   -t SUNW.HAStoragePlus

   Specifies that the resource is an instance of the SUNW.HAStoragePlus resource type.

   -x filesystemmountpoints="mountpoint-list"

   Specifies a list of valid mount points for the file system. For more information, see the SUNW.HAStoragePlus(5) man page.

4. Configure the Sun Cluster SAP J2EE engine resource.

   Edit the ha_sap_j2ee_config file and follow the comments with that file, as in the following example.

   # cd /opt/SUNWscswa/util # # more ha_sap_j2ee_config # # Copyright 2003 Sun Microsystems, Inc. All rights reserved. # Use is subject to license terms. # # This file will be sourced in by ha_sap_j2ee_register and the parameters # listed below will be used. # # These parameters can be customized in (key=value) form # # RS - name of the resource for the application # RG - name of the resource group containing RS # JAVA_HOME - name of the Java home directory # SAPID - The SAP System Name # J2EE_INSTANCE - name of the SAP J2EE Engine instance # LH - name of the LogicalHostname SC resource # HAS_RS - name of the SAP J2EE HAStoragePlus SC resource # # Optional parameters # # SAP_START - Optional, name of a startsap script within # <SAPID>adm home directory that will be used # instead of the default startsap. # # SAP_STOP - Optional, name of a stopsap script within # <SAPID>adm home directory that will be used # instead of the default stopsap. # # SAP_LOGDIR - Optional, where to put the logfiles from # startsap and stopsap. Default is the <SAPID>adm home # directory # # RESOURCE_PROJECT_NAME - Optional, name of a SRM project. # # The following examples illustrate sample parameters # for SAP J2EE Engine Instance # # RS=RES-SAP-J2EE # RG=RG-SAP-J2EE # JAVA_HOME=/usr/java # SAPID=TST # J2EE_INSTANCIES=JC00 # LH=j2eelh # HAS_RS=RES-SAP-J2EE-HAS # # SAP_START= # SAP_STOP= # SAP_LOGDIR= # RESOURCE_PROJECT_NAME= # # RS= RG= JAVA_HOME=/usr/java SAPID= J2EE_INSTANCE= LH= HAS_RS= SAP_START= SAP_STOP= SAP_LOGDIR= RESOURCE_PROJECT_NAME=

5. Register the Sun Cluster SAP J2EE engine resource.

   # cd /opt/SUNWscswa/util # ./ha_sap_j2ee_register

6. Set the resource dependencies.

   The SAP J2EE engine resource depends on the database resource, the SAP enqueue server, and the SAP message server resource.

   # scrgadm -c -j j2ee-rs -y Resource_Dependencies=db-rs,enq-rs,msg-rs

   -c

   Specifies that an existing configuration is to be changed.

   -j j2ee-rs

   Specifies the name of the resource to be changed. This resource name must be the same resource name that you specified in the configuration file in Step 4.

   -y Resource_Dependencies=db-rs,enq-rs,msg-rs

   Specifies that the following resources must be online before the SAP J2EE engine resource for the can be online:

   • Database resource. The database resource is created by the relevant data service.

   • SAP enqueue server resource.

   • SAP message server resource.

7. Enable the Sun Cluster SAP J2EE engine resource.

   # scswitch -ej j2ee-rs

   -ej

   Specifies that the specified resource is to be enabled.

   j2ee-rs

   Specifies the name of the resource to be enabled.