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 NetWeaver BW 7.3 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 NetWeaver Business Warehouse (BW) 7.1 Additional Application Server (AAS) is also known as Dialog Instance.

This section contains the following topics:

Automated installation process of SAP NetWeaver BW 7.3 AAS

Several BMC Server Automation BLPackages work together to install SAP NetWeaver BW 7.3 AAS on a target virtual machine. The target virtual machine is provisioned by using BMC Cloud Lifecycle Management. After your virtual machine is provisioned and customized, BMC Cloud Lifecycle Management triggers the application installation with the help of BMC Server Automation. 

BMC Cloud Lifecycle Management:

  1. Creates the required file system on the underlying physical volume for application installation with the NSH script SAP_BWAAS731_NW731_ABAP_RHEL64_ORA11203_FSC_v1.0.
  2. Copies the SAP media that is required for the installation from the Central Repository to the target virtual machine with the BLPackage SAP_BWAAS731_NW731_ABAP_RHEL64_ORA11203_MEDIA_v1.0.
  3. Creates the required directories and runs a prerequisite check before installing the SAP system with the BLPackage SAP_BWAAS731_NW731_ABAP_RHEL64_ORA11203_SC_v1.0.
  4. Creates the required users for installation with the BLPackage SAP_BWAAS731_NW731_ABAP_RHEL64_ORA11203_PRC_v1.0.
  5. Triggers installation of the required users on the target system and mounts directories from the Central Instance with the BLPackage SAP_BWAAS731_NW731_ABAP_RHEL64_ORA11203_UGRC_v1.0.
  6. Triggers installation of the software on the target system with the BLPackage SAP_BWAAS731_NW731_ABAP_RHEL64_ORA11203_BWI_v1.0.

To request an SAP NetWeaver BW 7.3 AAS service

  1. Log on to the Cloud Portal.
  2. Navigate to Service Instances.
  3. Click the Service Catalog tab.
  4. In the Request Servce section, click Business Warehouse AAS 7.3.

    1.jpg

    The SAP BW AAS 731 ABAP based on NW731 - 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

    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 BW AAS 731 ABAP based on NW731 - 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 be always 1.

  8. Click Next.

    The last section of the SAP BW AAS 731 ABAP based on NW731 - 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 SAP NetWeaver BW 7.3 AAS provisioning.
     

Limitations

The following limitations pertain to SAP NetWeaver BW 7.3 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.

 

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

BMC Cloud Lifecycle Management 3.1