Skip to Content
Information
Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Requesting an SAP ERP Additional Application Server service

Optional SAP instances can be used to create additional application servers to scale the performance of an SAP system. Like the primary application server instance, an additional application server instance contains the application services for the SAP system. It is identified by an instance number, which is a two-digit number between 00 and 97 that is unique on a host. An additional application server instance typically has multiple work processes for the dialog, update, and background services. The machine on which it runs is called an additional application server instance host. SAP ERP Additional Application Server (AAS) is also known as Dialog Instance.

This section contains the following topics:

Automated installation process of SAP ERP AAS

After your virtual machine is provisioned and customized, BMC Cloud Lifecycle Management triggers the application installation with the help of BMC Server Automation. The following steps outline the automated installation process of SAP ERP AAS:

  1. BMC Cloud Lifecycle Management executes File System Creation script on the target system.
  2. BMC Cloud Lifecycle Management copies the SAP media to the target system, after the File System Creation script is executed.
  3. AAS Source script enables the Central System to prepare it to mount file systems on the target system.
  4. BMC Cloud Lifecycle Management triggers the prerequisite check.
  5. After the prerequisite check is complete, BMC Cloud Lifecycle Management triggers SAP ERP AAS installation. 

To request an SAP ERP Additional Application Server service

  1. Log on to the Cloud Portal.
  2. Navigate to Service Instances.
  3. Click the Service Catalog tab. 
  4. In the Request Service section, click ERP AAS 6.0 EHP5.

    1_CI.jpg

    The SAP ERPAAS60 EHP5 based on NW702 RHEL/Oracle screen appears.

    2_CI.jpg

     

  5.  In the Parameters section, enter the appropriate parameters in the respective fields as described in the table below:

    Label 

    Parameter used

    Description

    AAS/Dialog Instance Number 

    SAP_INSTANCE_NUMBER

    • This number is the technical identifier for internal processes.

    • The instance number consists of a two-digit number between 00 and 97.

    • AIX: Do not use 01 or 02 and 39 as instance number.

    • HP-UX: Do not use 02 and 75 as instance number.

    • Windows: Do not use 43 and 89 as instance number.

    Database Host 

    SAP_SOURCE_HOSTNAME

     • This name is the host name of the database.

    To find out the host name, enter the command "hostname" in the Database Host field.

    SAP System ID (SAPSID) 

    SAP_INST

    • This identifier applies to the SAP Central Instance.

  6. Click Next.

    The second section of the SAP ERPAAS60 EHP5 based on NW702 RHEL/Oracle screen appears.

    3_CI.jpg

  7. Enter the appropriate values in the following mandatory fields:


    • Quantity
    • Instance Name Affix
    • Username
    • Password

    • Confirm Password

      Warning

      Note

      The Username must be root. The quantity must always be 1.

  8. Click Next.

    The last section of the SAP ERPAAS60 EHP5 based on NW702 RHEL/Oracle screen appears.

    4_CI.jpg

     
  9. Verify the information that you entered and click Submit.

    After you submit the request, it takes a couple of hours to complete the SAP ERP AAS provisioning.

SAP ERP AAS limitations

 The following limitations pertain to SAP ERP AAS provisioning:

  • The postinstallation activities within the SAP system need to be performed manually.
  • The <SAPSID> is not validated for restricted <SID>.
  • There is no option to enter the Master password.

To request a distributed SAP ERP Additional Application Server service

A distributed SAP ERP Additional Application Server is used to scale up an existing distributed SAP ERP environment.

  1. Log on to the Cloud Portal.
  2. Navigate to Service Instances.
  3. Click the Service Catalog tab. 
  4. In the Request Service section, click Distributed ERP AAS 6.0 EHP5.

    1.jpg

    The DIST ERPAAS60 EHP5 ABAP based on NW702 RHEL/Oracle screen appears.

    2.jpg

  5.  In the Parameters section, enter the appropriate parameters in the respective fields as described in the table below:
     

    Label 

    Parameter used

    Description

    CI Hostname

    SAP_SOURCE_CIHOSTNAME

     • This name is the host name of the Central Instance database. 

    DB Hostname

    SAP_SOURCE_DBHOSTNAME

     • This name is the host name of the distributed database.

    Enter Instance Number for AAS 

    SAP_INST_NUMBER

    • This identifier applies to the SAP instance number.

    Source Instance ID

    SAP_INST 

    • This identifier applies to the SAP Central Instance.

  6. Click Next.

    The second section of the DIST ERPAAS60 EHP5 ABAP based on NW702 RHEL/Oracle screen appears.

    3.jpg
  7. Enter the appropriate values in the following mandatory fields:
    • Quantity
    • Instance Name Affix
    • Username
    • Password

    • Confirm Password

      Warning

      Note

      The Username must be root. The quantity must always be 1.

  8. Click Next.

    The last section of the DIST ERPAAS60 EHP5 ABAP based on NW702 RHEL/Oracle screen appears.

    4.jpg
  9. Verify the information that you entered and click Submit.

    After you submit the request, it takes a couple of hours to complete the distributed SAP ERP AAS provisioning.

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Cloud Lifecycle Management 3.1