Skip Navigation Links
Exit Print View
| Oracle Solaris Cluster Data Service for SAP NetWeaver Guide Oracle Solaris Cluster 4.1

Search Scope:

- This Document
- Entire Library

## Installing and Configuring SAP NetWeaver

To enable HA for SAP NetWeaver to make SAP NetWeaver highly available, additional installation and configuration operations are required. These operations supplement the standard installation and standard configuration of the SAP NetWeaver.

The procedures in this section describe the installation and configuration of the following components of the SAP NetWeaver.

- SAP central services

- SAP replicated enqueue server

- SAP replicated enqueue preempter

- SAP `sapstartsrv` process

- SAP dialogue instance for one of the following engines:

  - ABAP

  - ABAP+J2EE

  - J2EE

  - ABAP single instance

## How to Enable the SAP NetWeaver to Run in a Cluster

The following resource groups are created in this procedure.

- SAP central services resource group, to contain the following resources:

  - SAP replicated enqueue preempter

  - SAP central services

  - SAP `sapstartsrv`

  - Logical hostname

- SAP replicated enqueue server resource group, to contain the following resources:

  - SAP replicated enqueue server

  - SAP `sapstartsrv`

  - Logical hostname

- SAP primary application instance resource group, to contain the following resources:

  - SAP dialogue instance component

  - SAP `sapstartsrv`

  - Logical hostname for this resource. In the case of a primary application instance it is configured as a failover resource group. Additional dialogue instances can be configured as multiple master resource groups.

Note - If your deployment is ABAP single instance, you do not need the SAP central services resource group nor the SAP replicated enqueue server resource group.

1. Assume the `root` role on a cluster node.
2. Create the resource group for your storage topology.

   The SAP NetWeaver requires shared storage so you must make your storage highly available. For example, you can create a resource group containing the `HAStoragePlus` resource managing the global file systems.

       # clresourcegroup create -S storage-rg

   storage-rg

     Specifies the name of the resource group to be created. Choose a unique name for each resource group within the cluster.

3. Register the `SUNW.HAStoragePlus` resource type.

       # clresourcetype register SUNW.HAStoragePlus

4. Create your storage resource.

       # clresource create -g storage-rg \
       -t SUNW.HAStoragePlus \
       -p filesystemmountpoints=mountpoint-list \
       hsp-rs

   -g storage-rg

     Specifies that the resource is to be added to the SAP storage resource group.

   -t SUNW.HAStoragePlus

     Specifies that the resource is an instance of the `SUNW.HAStoragePlus` resource type.

   -p filesystemmountpoints=mountpoint-list

     Specifies a list of valid mount points for the file system. For more information, see the SUNW.HAStoragePlus(5) man page.

   hsp-rs

     Specifies the name of the resource that you are creating.

   The resource is created in the enabled state.

       # clresourcegroup online -M storage-rg

5. Create a resource group for the SAP central services.

   The SAP central services resource group is a failover resource group to contain the SAP enqueue server resource, the SAP message server resource, and the logical hostname for these resources.

       # clresourcegroup create central-rg

   central-rg

     Specifies the name of the resource group to be created. Choose a unique name for each resource group within the cluster.

6. Add a logical hostname resource to the resource group that you created in Step 5.

       # clreslogicalhostname create -g central-rg central-logical-hostname

   `-g` central-rg

     Specifies that the logical hostname resource is to be added to the resource group named central-rg that you created in Step 5.

   central-logical-hostname

     Specifies that the logical hostname of the SAP central services resource is central-logical-hostname.

   Note - If you require a fully qualified hostname, you must specify the fully qualified name with the `-h` option and you cannot use the fully qualified form in the resource name.

7. Bring online the SAP central services resource group.

       # clresourcegroup online -M central-rg

   `-M`

     Specifies that the resource group is to be brought over into the managed state.

8. Create a resource group for the SAP replicated enqueue server.

   Note - If your deployment is ABAP single instance, you do not need the SAP replicated enqueue server resource group.

   The SAP replicated enqueue server resource group is a failover resource group to contain the SAP replicated enqueue server, a `sapstartsrv` resource, and the logical hostname for this resource.

       # clresourcegroup create repl-rg

9. Add a logical hostname resource to the resource group that you created in Step 8.

       # clreslogicalhostname create -g repl-rg saprepl-logical-hostname

   `-g` repl-rg

     Specifies the name of the resource group.

   saprepl-logical-hostname

     Specifies the logical hostname of the SAP replica server resource.

   Note - If you require a fully qualified hostname, you must specify the fully qualified name with the `-h` option and you cannot use the fully qualified form in the resource name.

10. Bring online the SAP replica server resource group.

        # clresourcegroup online -M repl-rg

    `-M`

      Specifies that the resource group is to be brought into the managed state.

11. Set weak positive affinity between the SAP central services resource group and the SAP replicated enqueue server resource group.

    The weak positive affinity setting ensures that, in case of failover, the SAP central services resource group fails over to the node where the SAP replicated enqueue server resource group has been running. If you want to configure the central services and the replicated enqueue server on the same instance number you must set the strong negative affinities between replicated enqueue resource group and the central service resource group. Do not do this if you run every instance on its own instance number which is the default SAP installation. .

        # clresourcegroup set -p RG_affinities=+repl-rg central-rg

    central-rg

      Specifies the name of the resource group to be modified.

    `-p RG_affinities=+`repl-rg

      Specifies that the central-rg resource group has weak positive affinity with the repl-rg resource group.

12. Create a resource group for the SAP dialogue instance component.

    The SAP dialogue instance resource group can be configured as a failover or multiple master resource group to contain the resource for the SAP dialogue instance component and its `sapstartsrv` resource. If the SAP dialogue instance is configured as a failover resource, the logical hostname for this resource is also contained in the SAP dialogue instance resource group.

    - To create a failover resource group, run the following command:

          # clresourcegroup create diag-rg

    - To create a multiple master resource group, run the following command:

          # clresourcegroup create \
          -p Maximum_primaries=value \
           -p Desired_primaries=value \
          diag-rg

    `-p Maximum_primaries=`value

      Specifies the maximum number of primary nodes for this multiple master resource group.

    `-p Desired_primaries=`value

      Specifies the desired number of primary nodes for this multiple master resource group.

    diag-rg

      Specifies the name of the resource group to be added. This name can be your choice but must be unique for the resource groups within the cluster.

13. If the resource group that you created in Step 12 is configured as a failover resource group, add a logical hostname resource to the resource group.

    If the resource group that you created in Step 12 is configured as a multiple master resource group, skip this step.

        # clreslogicalhostname create -g diag-rg diag-logical-hostname

    `-g` diag-rg

      Specifies the name of the resource group.

    diag-logical-hostname

      Specifies the logical hostname diag-logical-hostname of the SAP dialogue instance server resource. By default the name of the logical-host resource is set to the same name as this. If you wish to specify a separate name then place the name of the resource at the end of the command listing.

    Note - If you require a fully qualified hostname, you must specify the fully qualified name with the `-h` option and you cannot use the fully qualified form in the resource name.

14. Bring online the SAP NetWeaver resource group.

        # clresourcegroup online -M diag-rg

    `-M`

      Specifies that the resource group is to be brought into the managed state.

    diag-rg

      Specifies the name of the resource group that needs to be brought online.

15. Install the SAP NetWeaver software.

    Follow the instructions in the SAP NetWeaver installation manual to install the SAP NetWeaver software. To understand the SAP NetWeaver high availability concepts, refer to the SAP documentation at http://service.sap.com/ha.

16. Copy all system files that were changed during the SAP NetWeaver installation and configuration process to all the nodes that are to run the SAP NetWeaver resources.

    These files might include the following:

    - `/etc/user_attr`

    - `/etc/hosts`

    - `/etc/group`

    - `/etc/passwd`

    - `/etc/services`

    - `/etc/project`

Copyright © 2012, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |