Cluster Server 7.4.2 Configuration Guide for SAP Web Application Server - Windows

Last Published:
Product(s): InfoScale & Storage Foundation (7.4.2)
Platform: Windows
  1. Section I. Getting Started
    1. Introducing the Veritas High Availability Agent for SAP Web Application Server
      1. About the Veritas High Availability agent for SAP Web Application Server
        1.  
          Typical SAP Web Application Server configuration in a VCS cluster
      2.  
        How application availability is achieved in a physical environment
      3. How does the Veritas High Availability solution work
        1.  
          How the VMwareDisks agent communicates with the vCenter Server instead of the ESX/ESXi host
        2.  
          Typical VCS cluster configuration in a virtual environment
      4. Agent functions
        1.  
          Online
        2.  
          Offline
        3.  
          Monitor
        4.  
          Clean
      5.  
        Agent attributes for SAP Web Application Server
      6.  
        Installing the agent for SAP Web Application Server
    2. Installing and configuring the SAP Web Application Server for high availability
      1.  
        Monitoring an SAP instance
      2.  
        About installing SAP Web Application Server for high availability
      3.  
        About configuring SAP Web Application Server for high availability
      4. Setting up SAP systems for clustering
        1.  
          Installing SAP systems using a virtual hostname
      5.  
        Installing SAP system using Virtual Hostname
      6.  
        Configuring the agent for message server restart
      7. Configuring the Enqueue Replication Server
        1.  
          Configuring the Enqueue Replication Server manually
        2.  
          Configuring the Enqueue Replication Server using SAPInst
      8. Clustering an SAP instance
        1.  
          Configuring the first node in the cluster
        2.  
          Configuring all other nodes in the cluster
        3. Creating and adding domain groups and users
          1.  
            User accounts
          2.  
            Groups
          3.  
            Adding new domain groups and users
          4.  
            Creating SAP system users, sapsidadm and SAPServiceSAPSID
          5.  
            Adding the sapsidadm user to the SAP_SAPSID_GlobalAdmin Group
          6.  
            To add the SAPServiceSAPSID user to the SAP_SAPSID_GlobalAdmin Group
        4.  
          Creating and adding local groups and users
        5.  
          Creating and adding local groups and users
        6.  
          Creating sapmnt and saploc share directories
  2. Section II. Configuring the application for high availability
    1. Configuring the application in a physical environment
      1.  
        Overview
      2.  
        Before configuring the service groups for SAP Web Application Server
      3.  
        Configuring service groups with the SAP Web Application Server agent
      4.  
        Configuring the SAPWebAS preonline script
    2. Configuring the application in a VMware environment
      1.  
        About configuring application monitoring with Veritas High Availability solution for VMware
      2. Configuring application monitoring for SAP Web Application Server
        1.  
          Configuring the VCS cluster
        2.  
          Configuring the application
    3. Optional configuration tasks for the SAP Web Application Server agent
      1.  
        Setting the SAPMonHome attribute
      2.  
        Configuring the execution period for agent functions
      3.  
        Executing a custom monitor program
      4.  
        Preventing early faulting of Java and Add-In instances
  3. Section III. Troubleshooting the Agent
    1. Troubleshooting the agent for SAP Web Application Server
      1.  
        Starting the SAP Web Application Server outside a cluster
      2. Troubleshooting common problems
        1.  
          Unable to see an entry in the SAP MMC for an SAP instance
        2.  
          The agent for SAP Web Application Server fails to bring online an SAP instance resource through VCS
        3.  
          SAP instance does not come online, and the startsap.exe command exits with exit code -1
        4.  
          In case of an Enqueue server failure, the Enqueue server instance fails to take over the lock table from the Enqueue Replication server instance
        5.  
          The ensmon.exe command returns exit code 4 for a Enqueue server instance
        6.  
          The return code of the ensmon.exe command is 8 for an Enqueue Replication server instance
        7.  
          The Enqueue server instance does not fail over to the correct Enqueue Replication server instance
        8.  
          In case of a resource fault, the Service Group does not fail over
      3. Reviewing SAP Web Application Server agent log files
        1.  
          Using SAP instance log files
        2.  
          Using SAP log files
      4. Reviewing error log files
        1.  
          Using SAP NetWeaver instance files
        2.  
          Reviewing cluster log files
        3.  
          Using trace level logging
      5.  
        Checks for an SAP Add-In Usage Types
  4. Appendix A. Sample Configurations
    1.  
      About the sample configuration for the agent for SAP Web Application Server
    2.  
      Sample agent type definition for SAP WebAS
    3. Sample SAP resource configuration in a physical environment
      1.  
        Sample SAP primary application server instance
      2.  
        Sample SAP additional application server instance
      3.  
        Sample SAP Central Services instance
      4.  
        Sample SAP Enqueue Replication server instance
    4. Sample service group configurations in a physical environment
      1.  
        Sample service group configuration for ABAP and Java Usage types
      2.  
        Sample service group dependency for SAP Web Application Server
    5.  
      Sample configuration in a virtual environment

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.

Table: Required attributes

Required attributes

Description

ResLoglevel

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

SAPAdmin

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

SAPAdminDomain

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

SAPAdminPassword

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

SAPHost

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

SAPHome

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

SAPServiceUser

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

SAPSID

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

InstType

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

InstName

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:

  • ASCS03: SAP Central Services (ABAP)

  • SCS07: SAP Central Services (Java)

  • DVEBMGS00: SAP Primary Application Server (ABAP)

  • D05: SAP Additional Application Server (ABAP)

  • J06: SAP (Primary/Additional) Application Server (Java)

  • ERS04: SAP Enqueue Replication server

  • SMDA97: Solution Manager Diagnostics Agent

Type and dimension: string-scalar

Default: ""

Example: DVEBMGS00

InstProfile

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

ProcMon

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

SAPMonHome

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

EnqSrvResName

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.

Table: Optional attributes

Attribute

Description

SecondLevelMonitor

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

MonitorProgram

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:

  • 0 (server is online)

  • 110 (server is online)

  • 100 (server is offline)

  • 1 (server is offline)

  • 99 or anything else (server state is unknown)

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