Cluster Server 8.0 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
Checks for an SAP Add-In Usage Types
For an SAP Add-In system, you must perform the following checks before further investigations:
The SAP resources running the ABAP and Java Central Services instances are in the same Service Group.
The SAP resources running the ABAP and Java Enqueue Replication server instances, are in the same Service Group.
Note:
Veritas recommends to configure the Central Services and Enqueue Replication server instances for an Add-In usage type in different service groups to minimize the SPOFs in a service group.
Ensure the following:
The EnqSrvResName attribute of the Java Enqueue Replication server instance is set to the VCS resource that is running the corresponding Java Central Services instance (SCS).
The EnqSrvResName attribute of the ABAP Enqueue Replication server instance is set to the VCS resource that is running the corresponding ABAP Central Services instance (ASCS).