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
Groups
The SAPInst tool creates the following groups during domain installation:
SAP_SAPSID_GlobalAdmin | This global group is a domain level SAP administration group for organizing SAP system administrators. This global group, groups together the users at the domain level so that they can be placed in appropriate local groups. |
SAP_SAPSID_LocalAdmin | These are local groups created and maintained on an application server. A local group has rights only to the system on which the group is located. The system on which the local group is located is part of a particular domain. The local group can contain users and global groups from this domain. |
SAP_LocalAdmin | Though this group is created on all hosts, creating this group on the transport host is necessary. Members of this group have full control over the transport directory, drive:\usr\sap\trans. This directory allows transports to take place between systems. The SAP_SAPSID_GlobalAdmin groups of all the SAP systems that are part of the transport infrastructure are added to the SAP_LocalAdmin group. Therefore, the sapsidadm and SAPServiceSAPSID users of all systems in the transport infrastructure are members of the SAP_LocalAdmin group. These users have the rights necessary to initiate and execute transports. |