Cluster Server 7.3.1 Configuration Guide for SAP Web Application Server - Windows
- Section I. Getting Started
- Introducing the Veritas High Availability Agent for SAP Web Application Server
- About the Veritas High Availability agent for SAP Web Application Server
- How application availability is achieved in a physical environment
- How does the Veritas High Availability solution work
- Agent functions
- Agent attributes for SAP Web Application Server
- Installing the agent for SAP Web Application Server
- Installing and configuring the SAP Web Application Server for high availability
- Monitoring an SAP instance
- About installing SAP Web Application Server for high availability
- About configuring SAP Web Application Server for high availability
- Setting up SAP systems for clustering
- Installing SAP system using Virtual Hostname
- Configuring the agent for message server restart
- Configuring the Enqueue Replication Server
- Clustering an SAP instance
- Configuring the first node in the cluster
- Configuring all other nodes in the cluster
- Creating and adding domain groups and users
- Creating and adding local groups and users
- Creating and adding local groups and users
- Creating sapmnt and saploc share directories
- Configuring the first node in the cluster
- Configuring all other nodes in the cluster
- Creating and adding domain groups and users
- User accounts
- Groups
- Adding new domain groups and users
- Creating SAP system users, sapsidadm and SAPServiceSAPSID
- Adding the sapsidadm user to the SAP_SAPSID_GlobalAdmin Group
- To add the SAPServiceSAPSID user to the SAP_SAPSID_GlobalAdmin Group
- User accounts
- Groups
- Adding new domain groups and users
- Creating SAP system users, sapsidadm and SAPServiceSAPSID
- Adding the sapsidadm user to the SAP_SAPSID_GlobalAdmin Group
- To add the SAPServiceSAPSID user to the SAP_SAPSID_GlobalAdmin Group
- Creating and adding local groups and users
- Creating and adding local groups and users
- Creating sapmnt and saploc share directories
- Configuring the SAP systems on Windows Server 2008/2012
- Introducing the Veritas High Availability Agent for SAP Web Application Server
- Section II. Configuring the application for high availability
- Section III. Troubleshooting the Agent
- Troubleshooting the agent for SAP Web Application Server
- Starting the SAP Web Application Server outside a cluster
- Troubleshooting common problems
- Unable to install the Veritas High Availability agent for SAP Web Application Server
- Unable to see an entry in the SAP MMC for an SAP instance
- The agent for SAP Web Application Server fails to bring online an SAP instance resource through VCS
- SAP instance does not come online, and the startsap.exe command exits with exit code -1
- In case of an Enqueue server failure, the Enqueue server instance fails to take over the lock table from the Enqueue Replication server instance
- The ensmon.exe command returns exit code 4 for a Enqueue server instance
- The return code of the ensmon.exe command is 8 for an Enqueue Replication server instance
- The Enqueue server instance does not fail over to the correct Enqueue Replication server instance
- In case of a resource fault, the Service Group does not fail over
- Unable to see an entry in the SAP MMC for an SAP instance
- The agent for SAP Web Application Server fails to bring online an SAP instance resource through VCS
- SAP instance does not come online, and the startsap.exe command exits with exit code -1
- In case of an Enqueue server failure, the Enqueue server instance fails to take over the lock table from the Enqueue Replication server instance
- The ensmon.exe command returns exit code 4 for a Enqueue server instance
- The return code of the ensmon.exe command is 8 for an Enqueue Replication server instance
- The Enqueue server instance does not fail over to the correct Enqueue Replication server instance
- In case of a resource fault, the Service Group does not fail over
- Reviewing SAP Web Application Server agent log files
- Reviewing error log files
- Checks for an SAP Add-In Usage Types
- Troubleshooting the agent for SAP Web Application Server
- Appendix A. Sample Configurations
- About the sample configuration for the agent for SAP Web Application Server
- Sample agent type definition for SAP WebAS
- Sample SAP resource configuration in a physical environment
- Sample SAP primary application server instance
- Sample SAP additional application server instance
- Sample SAP Central Services instance
- Sample SAP Enqueue Replication server instance
- Sample SAP primary application server instance
- Sample SAP additional application server instance
- Sample SAP Central Services instance
- Sample SAP Enqueue Replication server instance
- Sample service group configurations in a physical environment
- Sample service group configuration for ABAP and Java Usage types
- Sample service group configurations for SAP systems on Windows Server 2008/2012
- Sample configuration for SAP Central Services Instances service group for Add-In installation Usage Type
- Sample resource dependency for SAP Central Services Instances service group for Add-In installation usage type
- Sample configuration for SAP Enqueue Replication Server Instances service group for Add-In installation Usage Type
- Sample resource dependency for SAP Enqueue Replication Server Instances service group for Add-In installation Usage Type
- Sample configuration for SAP Central Services Instances service group for Add-In installation Usage Type
- Sample resource dependency for SAP Central Services Instances service group for Add-In installation usage type
- Sample configuration for SAP Enqueue Replication Server Instances service group for Add-In installation Usage Type
- Sample resource dependency for SAP Enqueue Replication Server Instances service group for Add-In installation Usage Type
- Sample service group dependency for SAP Web Application Server
- Sample configuration in a virtual environment
Configuring service groups with the SAP Web Application Server agent
While setting up a cluster, you must always ensure that the cluster has some spare capacity to handle the SAP NetWeaver failover scenarios. For example, in case of a back-end database failure, the cluster must be able to run another database instance in conjunction with other running applications. Review the information about data protection.
The cluster should thus 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 or resource faults. An administrator should also be pro-actively able to move a service group between cluster nodes to perform preventative maintenance or apply patches.
To configure the service groups
- Change the cluster configuration to read/write mode.
C:\> haconf -makerw
- Create a service group for SAP NetWeaver
C:\> hagrp -add SAP710-PI1SCS
- Modify the SystemList attribute for the group, to add systems.
C:\> hagrp -modify SAP710-PI1SCS SystemList vcswin74 0 vcswin75 1
- Create resources for NIC, IP, Lanman,VMDg, and MountV in the service group.
C:\> hares -add SAP710-PI1SCS_nic NIC SAP710-PI1SCS
C:\> hares -add SAP710-PI1SCS_ip IP SAP710-PI1SCS
C:\> hares -add SAP710-PI1SCS_lanman Lanman SAP710-PI1SCS
C:\> hares -add SAP710-PI1SCS_mnt MountV SAP710-PI1SCS
C:\> hares -add SAP710-PI1SCS_vmdg VMDg SAP710-PI1SCS
For more details on creating and modifying resource attributes for NIC, IP, Lanman, VMDg and MountV refer to Cluster Server Bundled Agents Reference Guide.
- Create links between the resources.
C:\> hares -link SAP710-PI1SCS_ip SAP710-PI1SCS_nic
C:\> hares -link SAP710-PI1SCS_lanman SAP710-PI1SCS_ip
C:\> hares -link SAP710-PI1SCS_mnt SAP710-PI1SCS_vmdg
- Create SAPWebAS resource for applications based on SAP NetWeaver
C:\> hares -add SAP710-PI1SCS_scs SAPWebAS SAP710-PI1SCS
Based on the SAP instance you are clustering, modify the resource attributes.
- Create resource dependencies for SAPWebAS resource.
The SAPWebAS resource depends on the Lanman and MountV resources.
C:\> hares -link SAP710-PI1SCS_scs SAP710-PI1SCS_lanman
C:\> hares -link SAP710-PI1SCS_scs SAP710-PI1SCS_mnt
- Verify the final resource dependencies for SAP server group.
Group Parent Child SAP710-PI1SCS SAP710-PI1SCS_scs SAP710-PI1SCS_lanman SAP710-PI1SCS SAP710-PI1SCS_scs SAP710-PI1SCS_mnt SAP710-PI1SCS SAP710-PI1SCS_ip SAP710-PI1SCS_nic SAP710-PI1SCS SAP710-PI1SCS_lanman SAP710-PI1SCS_ip SAP710-PI1SCS SAP710-PI1SCS_mnt SAP710-PI1SCS_vmdg
- Save the cluster configuration.
C:\> haconf -dump -makero