Cluster Server 7.4.2 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
 
 
- 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 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
Sample service group configuration for ABAP and Java Usage types
The service group configuration in a cluster depends on some common characteristics that must be part of the configuration design.
These characteristics include the following:
- The SAP application server must be dependent on the database server 
- Each SAP instance (Application Server, Enqueue, and Enqueue Replication) should have a separate virtual IP address assigned to facilitate network transparency. 
- Each SAP instance (Application Server, Enqueue and Enqueue Replication) should be placed on shared disk to facilitate cluster node transparency. 
- Common file systems to include the profile, global and transaction file systems should be managed from one or more shared disk objects. These systems must be available to the SAP application via UNC path with SAPGLOBALHOST. 
Figure: Service group configuration for Application Server shows the service group configuration for Application Server
Figure: Service group configuration for SAP Central services instance shows the service group configuration for SAP Central services instance
Figure: Service group configuration for Enqueue Replication Server instance shows the service group configuration for Enqueue Replication Server instance