Verifying the SAP Installation

This section contains the procedures you need to verify the SAP installation.

How to Verify SAP and the Database Installation with Central Instance

Use this procedure to verify SAP central instance. Perform the following steps on all of the potential nodes on which the central instance can run.

1. Create the failover resource group to hold the network and central instance resources.

   # scrgadm -a -g sap-ci-resource-group [-h nodelist]

   ---

   Note –

   Use the -h option to the scrgadm(1M) command to select the set of nodes on which the SAP central instance can run.

   ---

2. Verify that you have added to your name service database all of the network resources that you use.

3. Add a network resource (logical hostname) to the failover resource group.

   # scrgadm -a -L -g sap-ci-resource-group -l ci-logical-hostname [-n netiflist]

4. Enable the resource group.

   Run the scswitch(1M) command to move the resource group into a managed state and bring the resource group online.

   # scswitch -Z -g sap-ci-resource-group

5. Log in to the cluster member that hosts the central instance resource group.

6. Ensure that the database is running.

7. Manually start the central instance.

8. Start the SAP GUI using the logical hostname, and verify that SAP initializes correctly.

   The default dispatcher port is 3200.

9. Manually stop the central instance.

10. Switch this resource group to another cluster member that can host the central instance.

    # scswitch -z -h node -g sap-ci-resource-group

11. Repeat Step 5 through Step 9 until you verify startup and shutdown of the central instance on each cluster node that can host the central instance.

Where to Go From Here

Go to How to Verify an SAP Failover Application Server.

How to Verify an SAP Failover Application Server

Use this procedure to verify SAP and the database installation for the failover application server. Perform the following steps on all of the potential nodes on which the failover application server can run.

1. Create the failover resource group to hold the network and application server resources.

   # scrgadm -a -g sap-as-fo-resource-group

   ---

   Note –

   Use the -h option to the scrgadm command to select the set of nodes on which the SAP application server can run.

   # scrgadm -a -g sap-as-fo-resource-group\ [-h nodelist]

   ---

2. Verify that you added to your name service database all of the network resources that you use.

3. Add a network resource (logical hostname) to the failover resource group.

   # scrgadm -a -L -g sap-as-fo-resource-group\ -l as-fo-logical-hostname [-n netiflist]

4. Enable the resource group.

   Run the scswitch(1M) command to move the resource group into a managed state and bring the resource group online.

   # scswitch -Z -g sap-as-of-resource-group

5. Log in to the cluster member that hosts the application server resource group.

6. Manually start the application server.

7. Start the SAP GUI using the logical hostname, and verify that SAP initializes correctly.

8. Manually stop the application server.

9. Switch this resource group to another cluster member that can host the application server.

   # scswitch -z -h node -g sap-as-fo-resource-group

10. Repeat Step 5 through Step 7 until you verify startup and shutdown of the application server on each cluster node that can host the application server.

Where to Go From Here

Go to Installing the Sun Cluster HA for SAP Packages.

How to Verify an SAP Scalable Application Server

If you installed scalable application server instances in How to Install and Enable an SAP Scalable Application Server, you verified the installation of an SAP scalable application server in Step 13 of How to Install and Enable an SAP Scalable Application Server.

Where to Go From Here

Go to Installing the Sun Cluster HA for SAP Packages.