Installing SAP

1. ASCS should be installed based on “virtual hostname” based on “virtual IP”, which should have been added to host files during earlier installation steps. Please be sure to do so if they have not already been done prior to installing SAP.

• • When installing SAP (specifically ASCS or SCS) you need to specify the SAPINST_USE_HOSTNAME=vip option. This is not required for ERS. (Note: Document the SAPINST_USE_HOSTNAME virtual IP address as it will be used later during creation of the SAP resources in LifeKeeper.)
    

Note: Specify sapinst SAPINST_USE_HOSTNAME=vip where vip is the virtual IP that will float between the nodes.

Run ./sapinst SAPINST_USE_HOSTNAME= {hostname}

• • In seven phases, the Core Services should be created and started. If permission errors occur on jdbcconnect.jar, go to /sapmnt/STC/exe/uc/linuxx86_64 and make that directory as well as file jdbcconnect.jar writable (chmod 777 —-).
    

ASCS profiles should be pointing to local mount point containing /usr/sap, sapmnt or any other necessary for SAP files in your environment.

In the instance profiles of ASCS instances the entries must be changed, to prevent the services from getting automatically restarted, after that you have to restart the “sapstartsrv” of ASCS and e.g ----

Autostart = 1

Restart_Program_00 = local $(_ER) pf=$(_PFL) NR=$(SCSID)

to

Autostart = 0

Start_Program_00 = local $(_ER) pf=$(_PFL) NR=$(SCSID)

2. Sapstop SAP on node 1

3. Using the LifeKeeper GUI, right click on the IP address resource created for ASCS, select “In-Service” and select node 2 to switch the IP onto node 2.

4. Repeat step 1 to install SAP onto node 2 and ensure that it’s able to run correctly

5. Sapstop SAP on node 2

6. Using the LifeKeeper GUI, right click on the IP address resource created for ASCS, select “In-Service” and select node1 to switch the IP back onto node 1.

7. Sapstart SAP on node 1 and ensure that it’s able to run correctly