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

Last Published:
Product(s): InfoScale & Storage Foundation (8.0)
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

Configuring all other nodes in the cluster

Perform the following tasks on the other remaining cluster nodes:

  • Create the required SAP users and groups.

  • Set the system and user environment for the SAP system.

  • Enter the required port numbers in the Windows services files.

  • Install Host Agent using sapinst.exe.

  • Create the Windows service for the SAP instance.

To configure all other nodes in the cluster

  1. Log in as a domain administrator.
  2. Create the following local groups.
    • SAP_SAPSID_LocalAdmin

    • SAP_SAP_LocalAdmin

    • SAP_LocalAdmin

  3. Add the SAP_SAPSID_GlobalAdmin domain group to the SAP_SAPSID_LocalAdmin and SAP_LocalAdmin group.
  4. Add the SAP_SAP_GlobalAdmin domain group to the SAP_SAP_LocalAdmin and SAP_LocalAdmin
  5. Add the SAP_SAPSID_GlobalAdmin and SAP_SAP_GlobalAdmin domain group to the local Administrators group.

    For details on creating and adding a new local group and users:

    See Creating and adding local groups and users.

  6. Click Start > Programs > Administrative Tools > Local Security Policy > Local Policies > User Right Assignment.
  7. Add the following privileges for the sapsidadm user.
    • Act as a part of the Operating System (SeTcbPrivilege)

    • Replace a process-level token (SeAssignPrimaryTokenPrivilege)

    • Adjust memory quotas for a process (SeIncreaseQuotaPrivilege)

  8. Add the following privileges for the SAPServiceSAPSID user.
    • Log on as a Service (SeServiceLogonRight).

    • Adjust memory quotas for a process (SeIncreaseQuotaPrivilege)

    • Access this computer from the network (SeNetworkLogonRight)

    • Deny Log on Locally and Deny Log on through Terminal Services (SeDenyInteractiveLogOnRight)

  9. Change the sapsidadm user environment as follows:
    • At the command prompt enter,

      runas /profile /user:domain\sapsidadm regedit

    • On the Registry Editor panel, click HKEY_CURRENT_USER > Environment.

    • Modify the user environment based on your Database, SAP Usage Type and SAPSID.

    For example, the following table depicts the registry environment with Oracle database (PI1) and Add-In installation with SAPSID PI1.

    Name

    Type

    Data

    Default

    REG_SZ

    value not set

    DBMS_TYPE

    REG_SZ

    ora

    dbs_ora_schema

    REG_SZ

    SAPSR3

    dbs_ora_tnsname

    REG_SZ

    PI1

    JAVA_HOME

    REG_SZ

    C:\j2sdk1.4.2_19-x64

    NLS_LANG

    REG_SZ

    AMERICAN_AMERICA.UTF8

    ORACLE_HOME

    REG_EXPAND_SZ

    E:\oracle\PI1\102

    ORACLE_SID

    REG_EXPAND_SZ

    PI1

    PATH

    REG_EXPAND_SZ

    E:\usr\sap\PI1\SYS\exe\uc\NTAMD64;\

    \sappi1scs\sapmnt\PI1\SYS\exe\uc\NTAMD64;

    E:\oracle\PI1\102\BIN

    SAPDATA_HOME

    REG_EXPAND_SZ

    E:\oracle\PI1

    SAPEXE

    REG_SZ

    \\sapi1scs\sapmnt\PI1\SYS\exe\uc\NTAMD64

    SAPLOCALHOST

    REG_SZ

    sappi1aas

    SAPSYSTEMNAME

    REG_SZ

    PI1

    TEMP

    REG_EXPAND_SZ

    E:\usr\sap\PI1\tmp

    TMP

    REG_EXPAND_SZ

    E:\usr\sap\PI1\tmp

    TNS_ADMIN

    REG_EXPAND_SZ

    \\sappi1scs\sapmnt\PI1\SYS\profile\oracle

  10. From the first node in the cluster, copy the following service entries for the SAP instance, from the services file in the %windir%\system32\drivers\etc directory to the corresponding services file on all other nodes in the cluster.
    sapdp<No.> 	   32<No.>/tcp 	 # SAP System Dispatcher Port
    sapdp<No.>s 		 47<No.>/tcp   # SAP System Dispatcher Security Port
    sapgw<No.> 	   33<No.>/tcp   # SAP System Gateway Port
    sapgw<No.>s 	  48<No.>/tcp   # SAP System Gateway Security Port
    sapms<SAPSID>	 36<No.>/tcp 	 # SAP System Message Port Number
    

    where,

    The value for <No.> is the value of an Instance ID.

  11. Move the Service Group from the first node to the node that you are currently configuring and ensure that the drive:\usr\sap directory is shared with the names, sapmnt and saploc.

    See Creating sapmnt and saploc share directories.

  12. Install SAP Host Agent with SAPInst. Follow the steps below to install the SAP Host agent.
    • In the Master DVD, navigate to the directory containing the sapinst.exe tool.

    • Double-click the sapinst.exe file to launch the SAP installation GUI.

    • Select High Availability System > Based on [AS ABAP/AS Java/AS ABAP and AS Java] > Host Agent based on the usage type of system you installed.

    • Follow the instructions to complete the installation.

  13. Create the SAPSAPSID_No service as follows:
    • At the command prompt, navigate to the drive:\usr\sap\SAPSID\InstName\exe directory.

    • Run the sapstartsrv.exe command.

    • In the SAP Service Install/Uninstall dialog box, enter the following values:

      SID

      SAPSID

      NR

      InstanceNumber

      Profile

      If, SAPLOCALHOST=SAPGLOBALHOST, then enter the value as:

      drive:\usr\sap\SAPSID
      \SYS\profile\SAPSID_InstName
      _VirtualHostName

      If, SAPLOCALHOST is not equal to SAPGLOBALHOST, then enter the value as:

      \\SAPGLOBALHOST\sapmnt\SAPSID
      \SYS\profile\SAPSID_InstName
      _VirtualHostName

      User

      domain\SAPServiceSAPSID

      Password

      SAPServiceSAPSID password

      Startup type

      manual

      Use Environment of User

      domain\sapsidadm

  14. Click OK.
  15. Re-register the type library as follows:
    • At the command prompt, navigate to the Drive:\Path\SAP\hostctrl\exe directory.

    • Run the sapstartsrv.exe command.

    • In the SAP Service Install/Uninstall dialog box, select Register COM Typelibrary Only in the Operation field

    • Click OK.

  16. Create registry entries for the SAPSAPSID_No service.

    For example,

    Name

    Type

    Data

    Default

    REG_SZ

    value not set

    EventMessageFile

    REG_SZ

    \\sappi1scs\sapmnt\PI1\SYS\exe\

    uc\NTAMD64\sapevents.dll

    TypesSupported

    REG_DWORD

    0x00000007(7)

  17. If an SAP Microsoft Management Console (MMC) is not configured on the node, register the SAP MMC using the following steps:
    • Access the file sapmmcX64u.msi or sapmmcIA64u.msi from Kernel Install DVD depending on the OS architecture.

    • Install SAP MMC by executing the msi package.

Note:

Veritas recommends that you cluster the SAP Central Services instances for both ABAP and Java in an Add-In Usage Type in the same service group.

Also, cluster the Enqueue Replication servers for both ABAP and Java in an Add-In Usage Type in a single Service Group.