Configuring service groups for SAP WebAS
Prev Configuring the service groups for SAP WebAS using the CLI Next

Configuring service groups for SAP WebAS

While setting up a cluster, you must always ensure that the cluster has some spare capacity to handle the SAP WebAS failover scenarios. For example, in case of a backend database failure, the cluster must be able to run another database instance in conjunction with other running applications.

See Veritas Cluster Server Installation and Configuration Guide.

The cluster should be able to provide application failover by encapsulating the resources required for an application into a service group. A service group is a virtualized application that can switch between the cluster nodes. It contains a set of dependent resources, such as disk groups, disk volumes, file systems, IP addresses, NIC cards, and dependent application processes. It also includes logic about the dependencies between the application components.

These service groups should thus be configured such that the cluster can start, stop, monitor, and switch the service groups between the nodes, depending upon the server faults or resource faults. An administrator should also be proactively able to move a service group between cluster nodes to perform preventative maintenance or apply patches.

Perform the following steps to add a service group for SAP WebAS

  1. Create a service group for SAP WebAS.

    For example,

    # hagrp -add SAP71-PI1SCS

    For more details on creating a service group refer to,Veritas Cluster Server User's Guide

  2. Modify SystemList attribute for the group, to add systems.

    For example,

    # hagrp -modify SAP71-PI1SCS SystemList vcssx074 0 vcssx075 1

  3. Create resources for NIC, IP, DiskGroup, Volume and Mount in the service group.

    For example,

    # hares -add SAP71-PI1SCS_nic NIC SAP71-PI1SCS

    # hares -add SAP71-PI1SCS_ip IP SAP71-PI1SCS

    For more details on creating and modifying resource attributes for NIC, IP, DiskGroup, Volume and Mount refer to, Bundled Agents Reference Guide.

  4. Create links between the resources. For example,

    # hares -link SAP71-PI1SCS_ip SAP71-PI1SCS_nic

  5. Create SAPWebAS71 resource for SAP. For example,

    # hares -add SAP71-PI1SCS_scs SAPWebAS71 SAP71-PI1SCS

    Based on the SAP instance you are clustering, modify the resource attributes. For more information on agent attributes,

    See SAP WebAS agent attributes.

  6. Create resource dependencies for SAP WebAS resource.

    The SAPWebAS71 resource depends on IP and Mount resources.

    For example,

    # hares -link SAP71-PI1SCS_scs SAP71-PI1SCS_ip

  7. Verify the final resource dependencies for SAP WebAS server group.

    # hares -dep

    For example,

    			Group      		 	Parent      		     Child
	SAP71-PI1SCS 				SAP71-PI1SCS_ip  		SAP71-PI1SCS_nic
	SAP71-PI1SCS 				SAP71-PI1SCS_mnt 		SAP71-PI1SCS_vol
	SAP71-PI1SCS 				SAP71-PI1SCS_scs 		SAP71-PI1SCS_mnt
	SAP71-PI1SCS 				SAP71-PI1SCS_scs 		SAP71-PI1SCS_ip
	SAP71-PI1SCS 				SAP71-PI1SCS_vol 		SAP71-PI1SCS_dg

Prev Up Next
Creating service groups for Enqueue and Enqueue Replication Server under Solaris non-global zones Home Generating environments file for SAP