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 does the Veritas High Availability solution work
- Agent functions
- Installing and configuring the SAP Web Application Server for high availability
- Setting up SAP systems for clustering
- 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
- Troubleshooting common problems
- Reviewing SAP Web Application Server agent log files
- Reviewing error log files
- Troubleshooting the agent for SAP Web Application Server
- Appendix A. Sample Configurations
Agent attributes for SAP Web Application Server
In a virtual environment, the Veritas High Availability Configuration Wizard discovers the required attributes. You can use CLI commands to configure any of the optional attributes.
Table: Required attributes shows the required attributes for configuring a SAP Web Application Server instance.
Required attributes | Description |
---|---|
The logging detail performed by the agent for the resource. The valid values are: INFO: Logs error messages TRACE: Logs error and trace messages. TRACE is very verbose and should only be used during initial configuration or for troubleshooting and diagnostic operations. Type and dimension: string-scalar Default: INFO Example: TRACE | |
Windows user name used to start the SAP instance. This user must be dedicated to all the SAP instances within an SAP system. The format is sapsidadm. Type and dimension: string-scalar Default: No default value Example: piladm | |
Windows domain name to which the SAPAdmin user belongs. Note: If SAPAdmin does not belong to a Windows domain, use the cluster localization settings to specify the local computer name for each system. Type and dimension: string-scalar Default: No default value Example: SYMCORP | |
Password for the SAPAdmin user. Use the vcsencrypt utility to encrypt the password. If you are using the VCS GUI, the GUI automatically encrypts the password. For more information about encrypting agent passwords, see the Cluster Server Administrator's Guide. Type and dimension: string-scalar Default: No default value Example: vxfgh28skbsj | |
Virtual IP host name (LANMAN name) for the SAP instance. If the instance is installed with location hostname, use the local system name as this attribute value. Type and dimension: string-scalar Default: No default value Example: sappi1scs | |
The absolute path to the SAP base directory. This attribute is used to locate programs that the agent uses for start, stop, and clean functions. Example 1: C:\usr\sap\PI1\DVEBMSG00\exe Example 2: C:\usr\sap\PI1\ASCS01\exe Default: No default value | |
Windows user name used to start the SAP Windows service for an SAPSID. This user must be dedicated to all the SAP services under one SAP system, and must not be used by any other SAP service or instance under a different SAP system, even in the same cluster. Note: Do not include the domain name in the value for this attribute. Use the SAPAdminDomain attribute to specify domain information. Type and dimension: string-scalar Default: No default value Example: SAPServicePI1 | |
SAP system name. This attribute starts with an alphabetic character and is exactly 3 characters in length. Ensure that the alphabetic characters used in this attribute are in uppercase only. SAPSID is defined during the SAP installation. Type and dimension: string-scalar Default: No default value Example: PI1 | |
String identifier that classifies and describes the SAP server instance type. The InstType values are not case sensitive. The valid values are: APPSERV: SAP Application Server ENQUEUE: SAP Central Services ENQREP: SAP Enqueue Replication Server SMDA: Solution Manager Diagnostics Agent Type and dimension: string-scalar Default: APPSERV Example: ENQUEUE | |
Uniquely identifies an SAP server instance, along with the SAPSID attribute. The last two characters of this attribute specify the value of the InstID attribute. The InstID and SAPSID attributes together uniquely identify an SAP instance. Some examples include the following:
Type and dimension: string-scalar Default: "" Example: DVEBMGS00 | |
Specifies the full path and file name of the SAP Instance Profile. Typically the InstProfile is found in C:\usr\sap\SAPSID\SYS\profile and has a name of SAPSID_InstName_hostname. Type and dimension: string-scalar Default: No default value Example: C:\usr\sap\PI1\SYS\profile\PI1_DVEBMGS00_sappi1pas | |
The list of SAP processes that the monitor function must monitor during a first-level check of an SAP instance. The entries in this list are separated by a space and can be specified in any order. The valid values are: APPSERV: disp+work.exe igswd.exe jstart.exe gwrd.exe icman.exe ENQUEUE: msg_server.exe enserver.exe gwrd.exe ENQREP: enrepserver.exe SMDA: jstart.exe Type and dimension: vector-scalar Default: No default value Example: disp+work.exe | |
The directory that defines the location of the sapcontrol.exe or ensmon.exe commands. The agent for SAP WebAS uses these commands for second-level monitoring. This functionality is not a part of the base SAP installation. Hence, the value of this attribute may be different from the SAPHome attribute. Type and dimension: string-scalar Default: No default value Example: C:\usr\sap\AAV\SYS\exe\uc\NTAMD64 | |
Specifies the SAP Central Services instance resource name in VCS. This attribute is set only for Enqueue Replication Server (ERS) and will be used by both Enqueue and Enqueue Replication Servers to query others status during startup and failover. Type and dimension: string-scalar Default: No default value Example: SAPPI1SCS_scs |
Table: Optional attributes shows the optional attributes for configuring an SAP Web Application Server instance.
Attribute | Description |
---|---|
Used to enable second-level monitoring and specify the interval for the same. Second-level monitoring is a deeper, more thorough state check of the configured SAP instance. The numeric value specifies how often the second-level monitoring routines are run. 0 means never run the second-level monitoring routines, 1 means run routines every monitor interval, 2 means run routines every second monitor interval, and so on. Note: Exercise caution while setting SecondLevelMonitor to large numbers. For example, if the MonitorInterval is set to 60 seconds and the SecondLevelMonitor is set to 100, then sapcontrol is executed every 100 minutes, which may not be as often as intended. For maximum flexibility, no upper limit is defined for SecondLevelMonitor. For Java and Add-In systems, if SecondLevelMonitor is enabled and if resources are going to unknown state, change ResLogLevel to TRACE. After you change ResLogLevel to TRACE, you might encounter the following error message: J2EEGetProcessList FAIL: HTTP error, HTTP/1.1 401 Unauthorized. If you encounter the above-mentioned error message, edit the instance profile, add the following parameter, and restart the instance service: service/protectedwebmethods = Type and dimension: integer-scalar Default: 0 Example: 1 | |
Full path and file name of an external, user-supplied monitor program. If specified, the monitor function executes this file to perform an additional server state check. There are no restrictions for what actions the external monitor program performs, to determine the state of a SAP instance server. The only constraint is that the external monitor program must return one of the following integer values:
Note: Veritas recommends storing the external monitor program in the shared disk directory to ensure the file is always available on the online system. Arguments are supported. Type and dimension: string-scalar Default: No default value Example 1: C:\usr\sap\PI1\DVEBMGS00\work\mymonitor.bat Example 2: C:\usr\sap\PI1\DVEBMGS00\work\mymonitor.exe arg1 arg2 |