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

Configuring the application

Perform the following steps to configure the SAP Web Application Server for high availability on a virtual machine.

To configure the application

  1. Launch the vSphere Client and connect to the vCenter Server that manages the virtual machine. On the Inventory view of the vCenter Server, in the left pane, select the virtual machine where you want to configure application monitoring. Then, in the right pane, select the Veritas High Availability tab.

    Note:

    Ensure that the disk residing on the shared datastore is attached and the volumes are mounted on the selected virtual machine.

  2. On the Veritas High Availability tab, click Configure Application for High Availability. This option is available only after a cluster has been configured. Unless you configure a cluster, you cannot configure an application for monitoring.
  3. On the Welcome panel of the Veritas High Availability Configuration wizard, review the pre-requisites and then click Next.
  4. On the Application Selection panel, select SAP from the Supported Applications list and then click Next.

    Alternatively, you can use the Search box to find the application and then click Next.

    If you want to download any of the Veritas High Availability agents, click the Download Application Agents (SORT) link to download the agents from the Veritas Services and Operations Readiness Tools (SORT) site.

    https://sort.veritas.com/agents

  5. On the SAP Instance Selection panel, select the instance that you want to configure, enter the SAP administrator's password, and click Next.

    Note:

    The wizard does not display those SAP instances that are already configured for monitoring.

  6. On the Configuration Inputs panel, select the VCS cluster systems on which you want to configure the application for high availability and move them to the Application failover targets list. The local system is selected by default.

    Using the up-down arrow keys, you can define the priority order for the failover systems.

    For each system that you assign as a failover target, you must specify the domain user account details in the appropriate fields on the Edit System dialog box. The VCS agents use these details to perform domain operations such as Active Directory updates.

  7. On the Virtual Network Details panel, specify the virtual IP and the network details for the application to be configured and then click Next.

    To specify the virtual IP and network details, select the IP version and then specify the following details for each failover system:

    Note:

    You must select the same IP version as that selected during the VCS cluster configuration.

    Virtual IP address

    Specify a unique virtual IP address.

    Subnet mask

    Specify the subnet mask to which the IP address belongs.

    Virtual name

    Specify a virtual name.

    Network Adapter column

    Select the network adapter that will host the virtual IP.

    If you want to add another virtual IP address, click Add virtual IP address. A virtual IP input panel appears, in which you can enter the details as described earlier in this step.

    Note:

    You can only provide either a set of IPv4 addresses or a set of IPv6 addresses, not both.

  8. On the Target ESX/ESXi Host Details panel, specify the hosts and the administrative user account details for each host, and then click Next.

    Note:

    This panel appears only if you have selected multiple application failover targets on the Configuration Inputs panel.

    To specify the hosts, click Add ESX/ESXi Host, and on the Add ESX/ESXi Host dialogue box, specify the following details:

    ESX/ESXi hostname or IP address

    Specify the target ESX hostname or IP address.

    The virtual machines will fail over on this ESX host during vMotion.

    The mount points configured on the ESX host where the application is currently running must be available on the target ESX host.

    User name

    Specify a user account for the ESX host.

    The user account must have administrator privileges on the specified ESX host.

    Password

    Specify the password for the user account provided in the User name text box.

    The wizard validates the user account and the storage details on the specified hosts.

  9. On the Configuration Summary panel, review the application configuration details.

    The wizard assigns a unique name to the application service group. Click Rename to rename the service group.

    Click Next to initiate the application monitoring configuration.

  10. On the Implementation panel, the wizard performs the application configuration tasks.

    The wizard displays the status of each task. After all the tasks are complete, click Next.

    If the configuration tasks fail, click Diagnostic information to check the details of the failure. Rectify the cause of the failure, and run the wizard again to configure application monitoring.

  11. On the Finish panel, click Finish to complete the wizard workflow. This configures the application for high availability on the selected VCS cluster systems.

    The Veritas High Availability view now displays the application status and its component dependency.

    If the application status shows as not running, click Start to start the configured components on the system.