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
Monitor
The monitor function performs the following tasks:
Validates the values of the agent attributes required to monitor the SAP instance.
Performs a first-level monitor check as follows:
The function verifies that the SAP Windows service SAPSAPSID_InstID is running, where InstID is the last two characters of the InstName attribute.
Verifies that all processes that the ProcMon attribute lists are running.
If the value of SecondLevelMonitor attribute is greater than 0, the monitor function performs a more thorough check of the SAP instance as follows:
For APPSERV instances, the function uses the following utilities to perform this check:
SAPWeb Application Server as ABAP
sapcontrol.exe
SAPWeb Application Server as Java
sapcontrol.exe
SAPWeb Application Server as Add-In
sapcontrol.exe
For an Enqueue or Enqueue Replication server instance, the function uses the ensmon.exe utility.
If the MonitorProgram attribute specifies a custom monitor program, the monitor function executes the specified program.
More Information