Cluster Server 7.4 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
Typical VCS cluster configuration in a virtual environment
A typical VCS cluster configuration in a VMware virtual environment involves two or more virtual machines. The virtual machine on which the application is active, accesses a non-shared VMware VMDK or RDM disk that resides on a VMware datastore.
The virtual machines involved in the VCS cluster configuration may belong to a single ESX host or could reside on separate ESX hosts. If the virtual machines reside on separate ESX hosts, the datastore on which the VMware VMDK or RDM disks (on which the application data is stored) reside must be accessible to each of these ESX hosts.
The application binaries are installed on the virtual machines and the data files are installed on the VMware disk drive. The VCS agents monitor the application components and services, and the storage and network components that the application uses.
During a failover, the VCS storage agents (MountV-VMNSDg-VMwareDisks in case of SFW storage, Mount-NativeDisks-VMwareDisks in case of LDM storage) move the VMware disks to the new system. The VCS network agents bring the network components online, and the application-specific agents then start the application services on the new system.
In a site recovery environment, Veritas High Availability solution additionally provides script files for the following tasks. These files are invoked when the SRM recovery plan is executed.
Set up communication between the vCenter Server and the SRM Server at the recovery site and the virtual machines at the protected site.
Assign a SiteID to both the sites.
Specify attribute values for the application components at the respective site.
Retrieve the application status in the SRM recovery report, after the virtual machine is started at the recovery site.
