Installation sequence

Edit online

The information in this sequence describes the SAP installation process.

About this task

The following sequence describes an SAP installation.

Install at least one instance on each LPAR, on which you want to run the SAP Central Services. In a two-LPAR environment, that means, for example, to install the ASCS instance on LPAR1 and the ERS instance on LPAR2. That ensures that the SAP environment is correctly set up on each of the two LPARs.

Install a SAP system in the following sequence:

Procedure

  1. Install ASCS or SCS for Java. The ASCS or SCS virtual host name must be active
  2. Install ERS for ASCS or SCS on a different LPAR. The ABAP or Java ERS virtual host name must be active
  3. Restart ASCS or SCS to activate the enqueue replication function
  4. Install/load the SAP Db2® database
  5. Install the primary application server (PAS)
  6. Install one or more additional application servers (AAS)

Results

A prerequisite for the ERS installation is that its corresponding ASCS or SCS are installed.

Ensure that the corresponding VIPAs are active on the systems where the SAP instances are to be started. Start the SAP system manually in the following sequence:
  1. Start ASCS or SCS for Java
  2. Start ABAP or Java ERS on different systems
  3. Start Db2
  4. Start the primary application server (PAS)
  5. Start one or more additional application servers (AAS)
Note:
  • If you installed your application servers that use virtual host names, make sure that their VIPAs are active and the host names can be reached in your network before you start SAP.
  • With SAP NetWeaver 7.5, the concept of an ABAP primary application server instance with instance name DVEBMGS<nn> are removed. All SAP ABAP instances are now installed with instance names D<nn> and are functionally equivalent.