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
Installing SAP systems using a virtual hostname
An SAP system can be installed in HA environment directly using virtual hostnames. To install an SAP system using a virtual hostname, perform the following steps:
Note:
Before installing an SAP system refer to the SAP installation documentation.
To install an SAP system using a virtual hostname
- Log in as a user with domain administrator rights.
- Create a service group with IP and Lanman resources for SAP instance.
- Bring the service group online.
- On the node that has the service group online, start the SAP instance installation.
Note:
Do not double-click the sapinst.exe file to launch the SAP installation GUI. Use the SAPINST_USE_HOSTNAME parameter to launch the SAP installation GUI in a virtual environment.
- On the Master DVD, navigate to the directory havingsapinst.exe tool.
At the command prompt, run the command:
path\sapinst.exe SAPINST_USE_HOSTNAME=Virtual Host Name
Where,
Virtual Host Name is the virtual Lanman name that you created in step 2 above.
- From the installation GUI, select High Availability System >Based on [AS ABAP/AS Java/AS ABAP and AS Java].
Select the appropriate option based on the usage type of the system you are planning to install and follow the instructions to complete the installation.