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 VCS cluster

VCS cluster configuration involves selecting the virtual machines on which you want to configure high availability and setting up the network communication links between the selected virtual machines.

To configure the VCS cluster

  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.
  2. Skip this step if you have already configured the single sign-on during the guest installation.

    On the Veritas High Availability view, specify the credentials of a user account that has administrative privileges on the system and then click Configure.

    The single sign-on configuration enables the Veritas High Availability Console to set up a permanent authentication for the user account. After the authentication is successful, the Veritas High Availability view refreshes and displays the link to configure the VCS cluster.

  3. On the Veritas High Availability view, click Configure a VCS Cluster. This launches the VCS cluster configuration wizard. Unless you configure a cluster, you cannot configure an application for monitoring.
  4. On the Welcome panel, review the pre-requisites and then click Next.
  5. On the Configuration Inputs panel, specify the systems for the VCS cluster operations and the user account details for each system.

    Note:

    The specified user account must have administrative privileges on the system.

    The Cluster systems lists the systems that are included in the cluster configuration. The local system is selected by default.

    To add more systems, click Add System and then on the Add System dialog box, specify the following details of the system that you want to add to the VCS cluster.

    System Name or IP address

    Specify the name or IP address of the system that you want to add to the VCS cluster.

    User name

    Specify the user account for the system. The user name must be in the domain.com\username.

    Note:

    The specified user must be a domain user having administrative privileges on all the selected system.

    Password

    Specify the password for the user account mentioned.

    Use the specified user account on all systems

    Uses the specified user account on all the cluster systems. This option is selected by default.

    The wizard validates the system details and then adds the system to VCS cluster system list.

  6. Skip this step if you do not want to modify the default security settings for your cluster.

    To modify the security settings for the cluster, on the Configuration Inputs panel, click Advanced Settings . In the Advanced settings dialog box, specify the following details and then click OK.

    Use Single Sign-on

    Select to configure single sign-on using VCS Authentication Service for cluster communication.

    This option is enabled by default.

    Use VCS user privileges

    Select to configure a user with administrative privileges to the cluster.

    Specify the user name and password and click OK.

  7. On the Network Details panel, select the type of communication for the VCS cluster and then select the adapters to configure the communication links.

    Depending on the network over which you want to configure the links, select:

    • Use MAC address for cluster communication (LLT over Ethernet) : The LLT over Ethernet communication configures the links over the non-routed network. Choose this mode only if the failover target systems reside in the same subnet.

    • Use IP address for cluster communication (LLT over UDP): The LLT over UDP communication configures the links over the routed network. You can choose this mode regardless of whether the failover target systems reside in the same subnet or in different subnets. You can select only those adapters that have an IP address.

    You must select a minimum of two adapters per system.

    Veritas recommends the following:

    • IP addresses that are assigned to the selected adapters should be in different subnets.

    • One of the network adapters must be a public adapter. You may assign low priority to the VCS cluster communication link that uses the public adapter.

    Network Adapter

    Select a network adapter for the communication links.

    You must select a different network adapter for each communication link.

    To configure links over UDP, select the IP version and then specify the required details for each communication link.

    Note:

    Do not select the teamed network adapters and the independently listed adapters that are a part of the teamed NIC.

    IP Address

    Specify the IP address for cluster communication over the specified UDP port.

    Port

    Specify a unique port number for each link. You can use ports in the range 49152 to 65535.

    A specified port for a link is used for all the cluster systems on that link.

    Subnet mask

    Displays the subnet masks to which the specified IP belongs.

    By default, the VCS cluster communication link that uses the public adapter is configured as low-priority link. To change the priority, click Modify. In the Modify low-priority link dialog box, select the link and click OK.

    For information about adding or changing the selected network links after the configuration workflow is complete, see the Cluster Server Administrator's Guide.

  8. On the Configuration Summary panel, specify a cluster name and a cluster ID of your choice.

    Review the VCS cluster configuration details and then click Next to initiate the configuration.

    If the network contains multiple clusters, the wizard verifies the cluster ID with the IDs assigned to all the accessible clusters in the network. The wizard does not validate the assigned ID with the clusters that are not accessible during the validation. Veritas recommends you to validate the uniqueness of the assigned ID in the existing network.

  9. On the Implementation panel, the wizard displays the VCS cluster configuration tasks and 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 the VCS cluster.

  10. On the Finish panel, click Finish to complete the wizard workflow. This step completes the VCS cluster configuration.

    The Veritas High Availability view now displays the link to configure an application for high availability.