Request to Fulfill Value Stream with SAP Best Practices

 

Overview

This document at current released state focuses on the activities that bridge the gap between HP's Cloud Service Automation portfolio and the SAP Installation tools. This is accomplished by integrating with the following products:

Additional integrations with Linux Redhat or Suse distribution with SAP may be covered in future automation‑related papers covering such topics as integrating with the SAP Cloud Appliance Library, SAP Landscape Virtualization Manager, and other SAP automation techniques. This also includes HP Cloud System version 8.x, HP Helion OpenStack, and HP CSA Topology Designs. However, content for a SAP LVM integration, as well as an integration with the SAP BAPI layer, is already available as an OO Content Pack. For details, see HP Live Network—for example, see SAP Landscape Virtualization Management (LVM) Content for HP Operations Orchestration.

For troubleshooting information, see the Request to Fulfill Value Stream with SAP Version 1.3 Best Practices Guide and Content.

Supported Versions

Note: For the hardware and software requirements, see the product documentation.

Product Version Instructions
HP Cloud Service Automation
  • 4.50 or later
For installation instructions, see HP Cloud Service Automation Version 4.50 Installation Guide.
HP Operation Orchestration
  • 10.22 or later
For installation instructions, see HP Operations Orchestration Version 10.20 Installation Guide.

Note: Make sure that each application you install is up and running before you perform any configuration steps.

Enterprise Hardware and Software Requirements

Note: The following tables detail the deployment environments that have been rigorously tested by HPE quality assurance personnel.

For the complete listing of hardware and software requirements, see the relevant Support Matrix for each product.

What do you want to do?

Select one of the following options:

ClosedDownloading and Importing Content for SAP S/4HANA with VMware vCenter on Linux

ClosedDownloading and Importing Content for SAP Standard System with VMware vCenter on Linux

ClosedDownloading and Importing Content for SAP Distributed System with VMware vCenter on Linux

ClosedSuspending and Resuming SAP System in the CSA Marketplace

ClosedAdding Application Server in the CSA Marketplace

ClosedCancelling an Order for the SAP System in the CSA Marketplace

To download the relevant content, go to Request to Fulfill Value Stream with SAP on HPE Live Network.

Prepare the Environment Content

Additional software requirement

Use the following third-party products to prepare the environment content for SAP S/4HANA with VMware vCenter on Linux:

Set up the VMware vCenter

Note: This document refers to only a single-node installation.

The following prerequisites must be configured in the VMware vCenter before deploying the SAP S/4HANA with VMware vCenter on Linux.

SAP Software Depot

To support repeatable, automated SAP installations, it is crucial to store all necessary installation media at a central location—a software depot.

Software Depot Creation

Depending on your environment, you can host the software depot on any server that is reachable in your environment. You can share the software depot on Windows using the Common Internet File System (CIFS) or on Linux using the Network File System (NFS).

Option 1: Software Depot on Windows (CIFS)

  1. Create a folder on your Windows server for the software depot, such as C:\SWDEPOT.

  2. To share the software depot folder, right-click SWDEPOT and select Share with > Specific people.

  3. Ensure that at least one user has full access to the folder by adding an appropriate user and sharing the folder.

Option 2: Software Depot on Linux (NFS)

  1. Create a folder on your Linux server for the software depot. # mkdir /SWDEPOT

  2. Install the NFS Server package on your Linux host, if not already done.

  3. Modify the exports file. # vi /etc/exports

  4. Make the following entry for your share. /SWDEPOT *(fsid=0,ro,root_squash,sync)

  5. Run exportfs to make the changes effective. # exportfs –a

Download the SAP Media Archives

Once the software depot folder has been shared, you can begin storing SAP installation media. The installation media for SAP customers is available at SAP Software Download Center.

Be sure to download the appropriate media archives, because some of them are operating system dependent.

SAP Software Provisioning Manager (SWPM)

You will also need to download the SAP Software Provisioning Manager (SWPM) tool, which is responsible for the installation of SAP S/4HANA or SAP Business Suite products.

On the left menu of the SAP Software Download Center, click Support Packages and Patches > Browse Download Catalog > SAP Technology Components > SL TOOLSET > SL TOOLSET 1.0 > Entry by Component > Software Provisioning Manager > SOFTWARE PROVISIONING MGR 1.0 > Support Package Patches > Linux on x86_64 64bit.

Next download the latest version of the SAP Software Provisioning Manager for NetWeaver—Version 7.0x or later—from the SAP Software Download Center.

Software Depot Directory Structure

Create a folder for each SAP product you want to install—for example, copying the desired SAP media archives into the S4HANAONPREM1511 folder on the software depot. The folder must be named with the exact value defined in Appendix A for the SapVersion property of the SAP product. For more information, see Appendix A: CSA Properties.

Note: For a HANA database, the depot directory can be named without limitation since it is not related to SapVersion property. Save the name of the depot directory for use in the deployment phase.

If the media archives have the file extension .sar, you need the SAPCAR tool to extract them. The SAPCAR tool is inside the Kernel archive (depending on the operating system). If you need the SAPCAR for another operating system, download it from SAP Software Download Center.

The SAPCAR syntax is the same as for tar—for example, on Linux:

# ./SAPCAR –xvf your-archive-file.sar

Now you can extract the archives. Extract one archive after the other and rename the extracted folder.

For example, after the extraction of the Kernel, use a meaningful name like Kernel_745_Linux_x86_64 to better identify its content. Repeat this for all extracted archive files. After completion, you will have a folder structure similar to the following example:

Next, verify that the CDLABEL and LABEL files are visible inside each of these folders. Otherwise the automated installation will fail because the SAP installer SWPM will not find the appropriate media files. The following screen shot is an example of the content of the Kernel directory Kernel_745_Linux_x86_64.

Downloading and Importing Content for SAP S/4HANA with VMware vCenter on Linux

Step 1: Import the Content Package in HP Operations Orchestration Package Manager.

  1. Log on to HP Operations Orchestration (HP OO).

    1. Go to https://"<OO Server>":8443/oo.

    2. Log on as a user with administrative privileges.

    The OO Web Client main window opens.

  2. In the left pane of the HP OO window, select Content Management.

  3. In the Content Management pane, select Content Packs.

  4. In the Content Packs pane, click the Deploy New Content icon.

  5. In the Deploy New Content pane, click the Add files for deployment button.

  6. Browse to the location of the content pack and select it.

  7. Click Open and then click Deploy.

Step 2: Add VMware vCenter instance to Cloud Service Automation providers.

  1. Log on to the Cloud Service Automation (CSA) application management console.

    1. Go to https://"<CSA server>":8444/csa/login.

    2. Log on as a user with administrative privileges.

    The Cloud Service Automation management console opens.

  2. Click Providers.

  3. On the left side of the Providers pane, select VMware vCenter

  4. On the right side of the Providers pane, the VMware vCenter opens. Click Create.

  5. In the Create Resource Provider pane, complete the following details:

    Name Description
    Display Name Name you provide for the provider
    Description Description you provide for the provider (not mandatory)
    User ID User ID for the specified Service Access Point
    Password

    Password for the specified Service Access Point

    Note: Re-type the password in the Confirm Password field.

    Service Access Point

    Specify a URL for connecting to the provider:

    • "<Service Access Point: https://"<Provider Name>":443>"

    When creating or updating a provider, HPE attempts to contact the provider at the specified URL.

    HPE uses a six (6) second timeout to attempt to validate the provider URL (for HTTP and HTTPS only). If the URL is not successfully contacted before the timeout expires, a validation failure message is displayed, and the option is provided to ignore the validation failure or to correct the URL and try again.

    Note: User credentials are not validated at this time.

    Image

    Image used to represent the provider instance (not mandatory)

    Enabled

    This value determines whether the provider will be selected when provisioning a new service. The setting is either Enabled (when selected) or Disabled (when not selected).

    When Disabled is selected, the provider will not be selected when provisioning new services. Disabling a provider has no effect on existing services that are using that provider.

  6. Click Create.

  7. On the "<Provider Name>" page, select the Properties tab and click DATACENTERNAME.

  8. In the Edit Property dialog box, enter the following information:

    • Display name. Name you provide for the Data Center property

    • Property Value. Name of the Data Center as it appears in the SAP S/4HANA with VMware vCenter on Linux graphical user interface

    Click Save.

  9. Click Save.

Step 3: Import SAP Topology Design into CSA.

  1. Log on to the Cloud Service Automation application management console.

    1. Go to https://"<CSA server>":8444/csa/login.

    2. Log on as a user with administrative privileges.

    The Cloud Service Automation management console opens.

  2. Navigate to Designs > Topology > Designer.

    The Topology Designs window opens.

  3. In the left pane, select All Designs.

  4. On the bottom of the right pane, click Import.

  5. In the Import Design dialog box:

    1. For the Archive File, click the Open button.

    2. From the Open dialog box, select the R2F_SAP_S/4HANA_vCenter.zip zip file that was downloaded in the package.

    3. Confirm that the Option field is set to Import.

    4. Click Import.

    5. In the Import Summary confirmation box, click OK.

      The Import Design dialog box closes.

  6. After the importing is complete, click the version number of the SAP S/4HANA System design.

    The SAP S/4HANA System window opens.

  7. Click the Designer tab. The topology design opens.

  8. For every component, the Properties pane appears on the right side of the window.

    Select every component and complete the values for the mandatory parameters according to the table in Appendix A: CSA Properties.

    Note: The mandatory parameters are marked with a red asterisk.

  9. After selecting each component, click Save in the Properties pane.

Step 4: Publish an offering in the CSA Marketplace Portal.

Note: For information on how to handle errors, see CSA Troubleshooting Guide.

  1. Log on to the Cloud Service Automation application management console.

    1. Go to https://"<CSA server>":8444/csa/login.

    2. Log on as a user with administrative privileges.

      The Cloud Service Automation management console opens.

  2. Navigate to Designs > Topology > Designer.

    The Topology Designs window opens.

  3. In the Search field in the right pane, enter SAP S/4HANA System.

  4. In the left pane, select the SAP S/4HANA System topology design.

  5. In the Topology Design Overview page, click Publish.

  6. In the Confirmation Required dialog box, click Yes.

    On the Topology Design Overview page, the green Published icon is visible—confirming publication.

  7. Click the Return button four times to return to the CSA management console home page and click Offerings.

  8. On the Offerings page, click Create.

  9. On the bottom of the right pane, click Import.

  10. In the Import Offering dialog box:

    1. For the Archive File, click the Open button.

    2. From the Open dialog box, select the SAP S/4HANA Offering zip file that was downloaded in the package.

    3. Confirm that the Option field is set to Import.

    4. Click Import.

    5. In the Import Summary confirmation box, click OK.

      The Import Offering dialog box closes.

  11. In the Search field in the right pane, enter SAP S/4HANA Offering.

  12. In the Search results, select the SAP S/4HANA Offering offering.

  13. In the Offerings pane, select the Publishing tab and click Publish.

    The Publish Service Offering dialog box opens.

  14. Complete the following and click Publish.

    1. To Catalog. Select Global Shared Catalog.

    2. In Category. Select Application Services.

Step 5: Validate the implementation.

  1. Log on to the Cloud Service Automation Marketplace Portal.

    1. Go to https://localhost:8444/mpp.

    2. Log on as a user with Administrative privileges.

      The Cloud Service Automation Marketplace Portal opens.

  2. In the Sidebar Menu, select Browse Catalog.

    The Browse Catalog pane opens.

  3. In the Search field, search for SAP S/4HANA Offering. When you see the SAP S/4HANA Offering offering, the validation is complete.

Step 6: Deploy the integration.

  1. Log on to the Cloud Service Automation Marketplace Portal.

    1. Go to https://localhost:8444/mpp.

    2. Log on as a user with Administrative privileges.

      The Cloud Service Automation Marketplace Portal opens.

  2. In the Sidebar Menu, select Browse Catalog.

    The Browse Catalog pane opens.

  3. In the Search field, search for SAP S/4HANA Offering.

  4. Select the SAP S/4HANA Offering and complete all of the properties according to the table in Appendix A: CSA Properties.

  5. Click Checkout.

    The Service Checkout window opens.

  6. In the Service Checkout window, complete the required information and click Submit Request. A confirmation message is displayed saying the request has been placed.

Appendix A: CSA Properties

For a SAP component

The values in brackets in the Name column are the corresponding parameters/variables for the local_input.ini file.

Name Possible Values Description
CifsPassword
(scrCifsPassword)
  When cifs are the protocol for the DepotHost, you will probably need a password to access the Windows share.
CifsUsername
(scrCifsUsername)
Administrator When cifs are the protocol for the DepotHost, you will probably need a username to access the Windows share.
DatabaseVendor
(scrDatabaseVendor)
ADA
DB6
HDB
ORA
SYB

String denominating the database vendor:

ADA = MaxDB
DB6 = DB2
HDB = HANA DB
ORA = Oracle
SYB = Sybase ASE
DeploymentIpAddr (scrDeploymentIpAddr)   IP address on the management network used for deployment and configuration
DeploymentIpAddr_HDB (scrDeploymentIpAddr_HDB)   IP address of the SAP HANA database on the management network used for deployment and configuration
DepotHost (scrDepotHost) cifs:172.16.0.15 or nfs:172.16.0.15 Protocol and host name of the server hosting the software depot. Protocol can be either cifs (when using Windows shares) or nfs (when using Linux shares). <protocol>:<hostname/IP-address>
DepotName (scrDepotName) SWDEPOT Name of the export / share on the file server
DepotSapDirectory (scrDepotSapDirectory)   Name of the directory where the software is located on the export / share
DryRun
(scrDryRun)
true
false
If true, then a test run is executed without the SAP installation. Default: false
HostFunction (scrHostFunction)
standard
ascs
scs
pas
db
aas

The value of this input parameter controls the type of SAP component to be installed.

standard = 2-tier - ASCS/SCS, DB and PAS on one Host
ascs = 3-tier – Central Services for ABAP (ASCS instance)
scs = 3-tier – Central Services for Java (SCS instance)
pas = 3-tier - Primary Application Server (PAS instance)
db = 3-tier – Database (DB)
aas = Additional Application Server (AAS instance)
HostnameFQDN (scrHostnameFQDN)   Fully qualified domain name (FQDN) of the host on the production network
HostnameFQDN_HDB (scrHostnameFQDN_HDB)   FQDN of the SAP HANA database host on the production network
InstanceNumber (scrInstanceNumber)   Two-digit SAP Instance Number of the SAP system scheduled to be deployed
InstanceNumber_HDB (scrInstanceNumber_HDB)   Two-digit SAP HANA database instance number
IpAddr (scrIpAddr)   Corresponding IP address on the production network
IpAddr_HDB (scrIpAddr_HDB)   Corresponding IP address of the SAP HANA database on the production network
MasterPW_HDB (scrMasterPW_HDB)   Master password of the SAP HANA database
multipleOS (scrMultipleOS)
true
false
Only necessary for heterogeneous installations. Currently, only Linux is supported. Default: false
OperatingSystem Linux Currently, only Linux is supported.
OperatingSystem_HDB Linux Only Linux is supported for a SAP HANA database.
SapApplication (scrSapApplication)   Name of the SAP application to be installed
SapFlavour (scrSapFlavour)
ABAP
JAVA
Either ABAP or JAVA, depending on what kind of application stack will be installed
SapVersion (scrSapVersion)
*BS2013SR1
*BS2013SR2
*S4HANAONPREM1511

SAP version to be installed

BS2013SR1 = SAP Business Suite innovations 2013 SR1
BS2013SR2 = SAP Business Suite innovations 2013 SR2
S4HANAONPREM1511 = SAP S/4HANA on-premise 1511
SID (scrSID)   SAP System Identification (SID). Only three characters are allowed.
SID_HDB (scrSID_HDB)   SAP System Identification of the SAP HANA database host
sshPort 22 ssh port of the host to connect to
sshRootPassword   ssh root password of the host to connect to
sshRootUsername root ssh root user of the host to connect to

For a vCenter component

The values in brackets in the Name column are the corresponding parameters/variables for the local_input.ini file.

Name Description
clusterName Cluster Name that should be used
cpuCount Amount of CPUs to allocate to the virtual machine (VM)
customizationSpec Name of the vCenter Customization Specification to use for the VM
dataStore Data store to use for the deployment
hostSystem ESXi host where the VM should be deployed
memorySize Amount of memory in megabytes to allocate to the VM
password Not necessary
privateKey Not necessary
username Not necessary
vmFolder Name of the Vmware folder the VM should create
vmNamePrefix VM prefix that should be used for the Vmware name
vmResourcePool Resource pool that should be used
vmTemplateReference Name of the VMware template that should be deployed

If you have any comments or suggestions regarding this document, please send them by email to sw-doc@hpe.com.

Suspending and Resuming SAP System

Log on to MPP. Use the dashboard to navigate to More Actions > My Services. Select the relevant online service. Click the button to stop / start the SAP system and suspend / resume the underlying virtual machine.

After the system is suspended, select the Resume SAP System entry to reboot the system and restore the server.

Adding Application Server

This action executes an OO flow that is responsible for provisioning a new virtual machine (VM), copying the installation script to that VM, and starting and conducting the SAP installation tool on it.

Click the button on the server group to deploy a new application server and copy the installation script.

After the OO flow is completed, the new application server details are also added to the service details page.

Cancelling an Order for the SAP System

To delete the installation and clean the virtual machine, log in to the Marketplace Portal (MPP) and search for the relevant subscription to be deleted.

To begin the deletion process, on the Subscription Details page in the MPP, click the Cancel Subscription button. This deletes the required files and removes the virtual machine.

Prepare the Environment Content

Additional software requirement

Use the following third-party products to prepare the environment content for SAP Standard System with VMware vCenter on Linux:

Set up the VMware vCenter

The following prerequisites must be configured in the VMware vCenter before deploying the SAP Standard System with VMware vCenter on Linux.

SAP Software Depot

To support repeatable, automated SAP installations, it is crucial to store all necessary installation media at a central location—a software depot.

Software Depot Creation

Depending on your environment, you can host the software depot on any server that is reachable in your environment. You can share the software depot on Windows using the Common Internet File System (CIFS) or on Linux using the Network File System (NFS).

Option 1: Software Depot on Windows (CIFS)

  1. Create a folder on your Windows server for the software depot, such as C:\SWDEPOT.

  2. To share the software depot folder, right-click SWDEPOT and select Share with > Specific people.

  3. Ensure that at least one user has full access to the folder by adding an appropriate user and sharing the folder.

Option 2: Software Depot on Linux (NFS)

  1. Create a folder on your Linux server for the software depot. # mkdir /SWDEPOT

  2. Install the NFS Server package on your Linux host, if not already done.

  3. Modify the exports file. # vi /etc/exports

  4. Make the following entry for your share. /SWDEPOT *(fsid=0,ro,root_squash,sync)

  5. Run exportfs to make the changes effective. # exportfs –a

Download the SAP Media Archives

Once the software depot folder has been shared, you can begin storing SAP installation media. The installation media for SAP customers is available at SAP Software Download Center.

Be sure to download the appropriate media archives, because some of them are operating system dependent.

SAP Software Provisioning Manager (SWPM)

You will also need to download the SAP Software Provisioning Manager (SWPM) tool, which is responsible for the installation of SAP S/4HANA or SAP Business Suite products.

On the left menu of the SAP Software Download Center, click Support Packages and Patches > Browse Download Catalog > SAP Technology Components > SL TOOLSET > SL TOOLSET 1.0 > Entry by Component > Software Provisioning Manager > SOFTWARE PROVISIONING MGR 1.0 > Support Package Patches > Linux on x86_64 64bit.

Next download the latest version of the SAP Software Provisioning Manager for NetWeaver—Version 7.0x or later—from the SAP Software Download Center.

Software Depot Directory Structure

Create a folder for each SAP product you want to install—for example, copying the desired SAP media archives into the S4HANAONPREM1511 folder on the software depot. The folder must be named with the exact value defined in Appendix A for the SapVersion property of the SAP product. For more information, see Appendix A: CSA Properties.

Note: For a HANA database, the depot directory can be named without limitation since it is not related to SapVersion property. Save the name of the depot directory for use in the deployment phase.

If the media archives have the file extension .sar, you need the SAPCAR tool to extract them. The SAPCAR tool is inside the Kernel archive (depending on the operating system). If you need the SAPCAR for another operating system, download it from SAP Software Download Center.

The SAPCAR syntax is the same as for tar—for example, on Linux:

# ./SAPCAR –xvf your-archive-file.sar

Now you can extract the archives. Extract one archive after the other and rename the extracted folder.

For example, after the extraction of the Kernel, use a meaningful name like Kernel_745_Linux_x86_64 to better identify its content. Repeat this for all extracted archive files. After completion, you will have a folder structure similar to the following example:

Next, verify that the CDLABEL and LABEL files are visible inside each of these folders. Otherwise the automated installation will fail because the SAP installer SWPM will not find the appropriate media files. The following screen shot is an example of the content of the Kernel directory Kernel_745_Linux_x86_64.

Download and Import Content for SAP Standard System with VMware vCenter on Linux

Step 1: Import the Content Package in HP Operations Orchestration Package Manager.

  1. Log on to HP Operations Orchestration (HP OO).

    1. Go to https://"<OO Server>":8443/oo.

    2. Log on as a user with administrative privileges.

    The OO Web Client main window opens.

  2. In the left pane of the HP OO window, select Content Management.

  3. In the Content Management pane, select Content Packs.

  4. In the Content Packs pane, click the Deploy New Content icon.

  5. In the Deploy New Content pane, click the Add files for deployment button.

  6. Browse to the location of the content pack and select it.

  7. Click Open and then click Deploy.

Step 2: Add a VMware vCenter instance to Cloud Service Automation providers.

  1. Log on to the Cloud Service Automation (CSA) application management console.

    1. Go to https://"<CSA server>":8444/csa/login.

    2. Log on as a user with administrative privileges.

    The Cloud Service Automation management console opens.

  2. Click Providers.

  3. On the left side of the Providers pane, select VMware vCenter.

  4. On the right side of the Providers pane, the VMware vCenter opens. Click Create.

  5. In the Create Resource Provider pane, complete the following details:

    Name Description
    Display Name Name you provide for the provider
    Description Description you provide for the provider (not mandatory)
    User ID User ID for the specified Service Access Point
    Password

    Password for the specified Service Access Point

    Note: Re-type the password in the Confirm Password field.

    Service Access Point

    Specify a URL for connecting to the provider:

    • "<Service Access Point: https://"<Provider Name>":443>"

    When creating or updating a provider, HPE attempts to contact the provider at the specified URL.

    HPE uses a six (6) second timeout to attempt to validate the provider URL (for HTTP and HTTPS only). If the URL is not successfully contacted before the timeout expires, a validation failure message is displayed, and the option is provided to ignore the validation failure or to correct the URL and try again.

    Note: User credentials are not validated at this time.

    Image

    Image used to represent the provider instance (not mandatory)

    Enabled

    This value determines whether the provider will be selected when provisioning a new service. The setting is either Enabled (when selected) or Disabled (when not selected).

    When Disabled is selected, the provider will not be selected when provisioning new services. Disabling a provider has no effect on existing services that are using that provider.

  6. Click Create.

  7. On the "<Provider Name>" page, select the Properties tab and click DATACENTERNAME.

  8. In the Edit Property dialog box, enter the following information:

    • Display name. Name you provide for the Data Center property

    • Property Value. Name of the Data Center as it appears in the SAP Standard System with VMware vCenter on Linux graphical user interface

    Click Save.

  9. Click Save.

Step 3: Import SAP Topology Design into CSA.

  1. Log on to the Cloud Service Automation application management console.

    1. Go to https://"<CSA server>":8444/csa/login.

    2. Log on as a user with administrative privileges.

    The Cloud Service Automation management console opens.

  2. Navigate to Designs > Topology > Designer.

    The Topology Designs window opens.

  3. In the left pane, select All Designs.

  4. On the bottom of the right pane, click Import.

  5. In the Import Design dialog box:

    1. For the Archive File, click the Open button.

    2. From the Open dialog box, select the R2F_SAP_Standard_vCenter.zip zip file that was downloaded in the package.

    3. Confirm that the Option field is set to Import.

    4. Click Import.

    5. In the Import Summary confirmation box, click OK.

      The Import Design dialog box closes.

  6. After the importing is complete, click the version number of the SAP Standard System design.

    The SAP Standard System window opens.

  7. Click the Designer tab. The topology design opens.

  8. For every component, the Properties pane appears on the right side of the window.

    Select every component and complete the values for the mandatory parameters according to the table in Appendix A: CSA Properties.

    Note: The mandatory parameters are marked with a red asterisk.

  9. After selecting each component, click Save in the Properties pane.

Step 4: Publish an offering in the CSA Marketplace Portal.

Note: For information on how to handle errors, see CSA Troubleshooting Guide.

  1. Log on to the Cloud Service Automation application management console.

    1. Go to https://"<CSA server>":8444/csa/login.

    2. Log on as a user with administrative privileges.

      The Cloud Service Automation management console opens.

  2. Navigate to Designs > Topology > Designer.

    The Topology Designs window opens.

  3. In the Search field in the right pane, enter SAP Standard System.

  4. In the left pane, select the SAP Standard System topology design.

  5. In the Topology Design Overview page, click Publish.

  6. In the Confirmation Required dialog box, click Yes.

    On the Topology Design Overview page, the green Published icon is visible—confirming publication.

  7. Click the Return button four times to return to the CSA management console home page and click Offerings.

  8. On the Offerings page, click Create.

  9. On the bottom of the right pane, click Import.

  10. In the Import Offering dialog box:

    1. For the Archive File, click the Open button.

    2. From the Open dialog box, select the SAP Standard System Offering zip file that was downloaded in the package.

    3. Confirm that the Option field is set to Import.

    4. Click Import.

    5. In the Import Summary confirmation box, click OK.

      The Import Offering dialog box closes.

  11. In the Search field in the right pane, enter SAP Standard System Offering.

  12. In the Search results, select the SAP Standard System Offering offering.

  13. In the Offerings pane, select the Publishing tab and click Publish.

    The Publish Service Offering dialog box opens.

  14. Complete the following and click Publish.

    1. To Catalog. Select Global Shared Catalog.

    2. In Category. Select Application Services.

Step 5: Validate the implementation.

  1. Log on to the Cloud Service Automation Marketplace Portal.

    1. Go to https://localhost:8444/mpp.

    2. Log on as a user with Administrative privileges.

      The Cloud Service Automation Marketplace Portal opens.

  2. In the Sidebar Menu, select Browse Catalog.

    The Browse Catalog pane opens.

  3. In the Search field, search for SAP Standard System Offering. When you see the SAP Standard System Offering offering, the validation is complete.

Step 6: Deploy the integration.

  1. Log on to the Cloud Service Automation Marketplace Portal.

    1. Go to https://localhost:8444/mpp.

    2. Log on as a user with Administrative privileges.

      The Cloud Service Automation Marketplace Portal opens.

  2. In the Sidebar Menu, select Browse Catalog.

    The Browse Catalog pane opens.

  3. In the Search field, search for SAP Standard System Offering.

  4. Select the SAP Standard System Offering and complete all of the properties according to the table in Appendix A: CSA Properties.

  5. Click Checkout.

    The Service Checkout window opens.

  6. In the Service Checkout window, complete the required information and click Submit Request. A confirmation message is displayed saying the request has been placed.

Appendix A: CSA Properties

For a SAP component

The values in brackets in the Name column are the corresponding parameters/variables for the local_input.ini file.

Name Possible Values Description
CifsPassword
(scrCifsPassword)
  When cifs are the protocol for the DepotHost, you will probably need a password to access the Windows share.
CifsUsername
(scrCifsUsername)
Administrator When cifs are the protocol for the DepotHost, you will probably need a username to access the Windows share.
DatabaseVendor
(scrDatabaseVendor)
ADA
DB6
HDB
ORA
SYB

String denominating the database vendor:

ADA = MaxDB
DB6 = DB2
HDB = HANA DB
ORA = Oracle
SYB = Sybase ASE
DeploymentIpAddr (scrDeploymentIpAddr)   IP address on the management network used for deployment and configuration
DeploymentIpAddr_HDB (scrDeploymentIpAddr_HDB)   IP address of the SAP HANA database on the management network used for deployment and configuration
DepotHost (scrDepotHost) cifs:172.16.0.15 or nfs:172.16.0.15 Protocol and host name of the server hosting the software depot. Protocol can be either cifs (when using Windows shares) or nfs (when using Linux shares). <protocol>:<hostname/IP-address>
DepotName (scrDepotName) SWDEPOT Name of the export / share on the file server
DepotSapDirectory (scrDepotSapDirectory)   Name of the directory where the software is located on the export / share
DryRun
(scrDryRun)
true
false
If true, then a test run is executed without the SAP installation. Default: false
HostFunction (scrHostFunction)
standard
ascs
scs
pas
db
aas

The value of this input parameter controls the type of SAP component to be installed.

standard = 2-tier - ASCS/SCS, DB and PAS on one Host
ascs = 3-tier – Central Services for ABAP (ASCS instance)
scs = 3-tier – Central Services for Java (SCS instance)
pas = 3-tier - Primary Application Server (PAS instance)
db = 3-tier – Database (DB)
aas = Additional Application Server (AAS instance)
HostnameFQDN (scrHostnameFQDN)   Fully qualified domain name (FQDN) of the host on the production network
HostnameFQDN_HDB (scrHostnameFQDN_HDB)   FQDN of the SAP HANA database host on the production network
InstanceNumber (scrInstanceNumber)   Two-digit SAP Instance Number of the SAP system scheduled to be deployed
InstanceNumber_HDB (scrInstanceNumber_HDB)   Two-digit SAP HANA database instance number
IpAddr (scrIpAddr)   Corresponding IP address on the production network
IpAddr_HDB (scrIpAddr_HDB)   Corresponding IP address of the SAP HANA database on the production network
MasterPW_HDB (scrMasterPW_HDB)   Master password of the SAP HANA database
multipleOS (scrMultipleOS)
true
false
Only necessary for heterogeneous installations. Currently, only Linux is supported. Default: false
OperatingSystem Linux Currently, only Linux is supported.
OperatingSystem_HDB Linux Only Linux is supported for a SAP HANA database.
SapApplication (scrSapApplication)   Name of the SAP application to be installed
SapFlavour (scrSapFlavour)
ABAP
JAVA
Either ABAP or JAVA, depending on what kind of application stack will be installed
SapVersion (scrSapVersion)
*BS2013SR1
*BS2013SR2
*S4HANAONPREM1511

SAP version to be installed

BS2013SR1 = SAP Business Suite innovations 2013 SR1
BS2013SR2 = SAP Business Suite innovations 2013 SR2
S4HANAONPREM1511 = SAP S/4HANA on-premise 1511
SID (scrSID)   SAP System Identification (SID). Only three characters are allowed.
SID_HDB (scrSID_HDB)   SAP System Identification of the SAP HANA database host
sshPort 22 ssh port of the host to connect to
sshRootPassword   ssh root password of the host to connect to
sshRootUsername root ssh root user of the host to connect to

For a vCenter component

The values in brackets in the Name column are the corresponding parameters/variables for the local_input.ini file.

Name Description
clusterName Cluster Name that should be used
cpuCount Amount of CPUs to allocate to the virtual machine (VM)
customizationSpec Name of the vCenter Customization Specification to use for the VM
dataStore Data store to use for the deployment
hostSystem ESXi host where the VM should be deployed
memorySize Amount of memory in megabytes to allocate to the VM
password Not necessary
privateKey Not necessary
username Not necessary
vmFolder Name of the Vmware folder the VM should create
vmNamePrefix VM prefix that should be used for the Vmware name
vmResourcePool Resource pool that should be used
vmTemplateReference Name of the VMware template that should be deployed

If you have any comments or suggestions regarding this document, please send them by email to sw-doc@hpe.com.

Prepare the Environment Content

Additional software requirement

Use the following third-party products to prepare the environment content for SAP Distributed System with VMware vCenter on Linux:

Set up the VMware vCenter

The following prerequisites must be configured in the VMware vCenter before deploying the SAP Distributed System with VMware vCenter on Linux.

SAP Software Depot

To support repeatable, automated SAP installations, it is crucial to store all necessary installation media at a central location—a software depot.

Software Depot Creation

Depending on your environment, you can host the software depot on any server that is reachable in your environment. You can share the software depot on Windows using the Common Internet File System (CIFS) or on Linux using the Network File System (NFS).

Option 1: Software Depot on Windows (CIFS)

  1. Create a folder on your Windows server for the software depot, such as C:\SWDEPOT.

  2. To share the software depot folder, right-click SWDEPOT and select Share with > Specific people.

  3. Ensure that at least one user has full access to the folder by adding an appropriate user and sharing the folder.

Option 2: Software Depot on Linux (NFS)

  1. Create a folder on your Linux server for the software depot. # mkdir /SWDEPOT

  2. Install the NFS Server package on your Linux host, if not already done.

  3. Modify the exports file. # vi /etc/exports

  4. Make the following entry for your share. /SWDEPOT *(fsid=0,ro,root_squash,sync)

  5. Run exportfs to make the changes effective. # exportfs –a

Download the SAP Media Archives

Once the software depot folder has been shared, you can begin storing SAP installation media. The installation media for SAP customers is available at SAP Software Download Center.

Be sure to download the appropriate media archives, because some of them are operating system dependent.

SAP Software Provisioning Manager (SWPM)

You will also need to download the SAP Software Provisioning Manager (SWPM) tool, which is responsible for the installation of SAP S/4HANA or SAP Business Suite products.

On the left menu of the SAP Software Download Center, click Support Packages and Patches > Browse Download Catalog > SAP Technology Components > SL TOOLSET > SL TOOLSET 1.0 > Entry by Component > Software Provisioning Manager > SOFTWARE PROVISIONING MGR 1.0 > Support Package Patches > Linux on x86_64 64bit.

Next download the latest version of the SAP Software Provisioning Manager for NetWeaver—Version 7.0x or later—from the SAP Software Download Center.

Software Depot Directory Structure

Create a folder for each SAP product you want to install—for example, copying the desired SAP media archives into the S4HANAONPREM1511 folder on the software depot. The folder must be named with the exact value defined in Appendix A for the SapVersion property of the SAP product. For more information, see Appendix A: CSA Properties.

Note: For a HANA database, the depot directory can be named without limitation since it is not related to SapVersion property. Save the name of the depot directory for use in the deployment phase.

If the media archives have the file extension .sar, you need the SAPCAR tool to extract them. The SAPCAR tool is inside the Kernel archive (depending on the operating system). If you need the SAPCAR for another operating system, download it from SAP Software Download Center.

The SAPCAR syntax is the same as for tar—for example, on Linux:

# ./SAPCAR –xvf your-archive-file.sar

Now you can extract the archives. Extract one archive after the other and rename the extracted folder.

For example, after the extraction of the Kernel, use a meaningful name like Kernel_745_Linux_x86_64 to better identify its content. Repeat this for all extracted archive files. After completion, you will have a folder structure similar to the following example:

Next, verify that the CDLABEL and LABEL files are visible inside each of these folders. Otherwise the automated installation will fail because the SAP installer SWPM will not find the appropriate media files. The following screen shot is an example of the content of the Kernel directory Kernel_745_Linux_x86_64.

Download and Import Content for SAP Distributed System with VMware vCenter on Linux

Step 1: Import the Content Package in HP Operations Orchestration Package Manager.

  1. Log on to HP Operations Orchestration (HP OO).

    1. Go to https://"<OO Server>":8443/oo.

    2. Log on as a user with administrative privileges.

    The OO Web Client main window opens.

  2. In the left pane of the HP OO window, select Content Management.

  3. In the Content Management pane, select Content Packs.

  4. In the Content Packs pane, click the Deploy New Content icon.

  5. In the Deploy New Content pane, click the Add files for deployment button.

  6. Browse to the location of the content pack and select it.

  7. Click Open and then click Deploy.

Step 2: Add a VMware vCenter instance to Cloud Service Automation providers.

  1. Log on to the Cloud Service Automation (CSA) application management console.

    1. Go to https://"<CSA server>":8444/csa/login.

    2. Log on as a user with administrative privileges.

    The Cloud Service Automation management console opens.

  2. Click Providers.

  3. On the left side of the Providers pane, select VMware vCenter.

  4. On the right side of the Providers pane, the VMware vCenter opens. Click Create.

  5. In the Create Resource Provider pane, complete the following details:

    Name Description
    Display Name Name you provide for the provider
    Description Description you provide for the provider (not mandatory)
    User ID User ID for the specified Service Access Point
    Password

    Password for the specified Service Access Point

    Note: Re-type the password in the Confirm Password field.

    Service Access Point

    Specify a URL for connecting to the provider:

    • "<Service Access Point: https://"<Provider Name>":443>"

    When creating or updating a provider, HPE attempts to contact the provider at the specified URL.

    HPE uses a six (6) second timeout to attempt to validate the provider URL (for HTTP and HTTPS only). If the URL is not successfully contacted before the timeout expires, a validation failure message is displayed, and the option is provided to ignore the validation failure or to correct the URL and try again.

    Note: User credentials are not validated at this time.

    Image

    Image used to represent the provider instance (not mandatory)

    Enabled

    This value determines whether the provider will be selected when provisioning a new service. The setting is either Enabled (when selected) or Disabled (when not selected).

    When Disabled is selected, the provider will not be selected when provisioning new services. Disabling a provider has no effect on existing services that are using that provider.

  6. Click Create.

  7. On the "<Provider Name>" page, select the Properties tab and click DATACENTERNAME.

  8. In the Edit Property dialog box, enter the following information:

    • Display name. Name you provide for the Data Center property

    • Property Value. Name of the Data Center as it appears in the SAP Distributed System with VMware vCenter on Linux graphical user interface

    Click Save.

  9. Click Save.

Step 3: Import SAP Topology Design into CSA.

  1. Log on to the Cloud Service Automation application management console.

    1. Go to https://"<CSA server>":8444/csa/login.

    2. Log on as a user with administrative privileges.

    The Cloud Service Automation management console opens.

  2. Navigate to Designs > Topology > Designer.

    The Topology Designs window opens.

  3. In the left pane, select All Designs.

  4. On the bottom of the right pane, click Import.

  5. In the Import Design dialog box:

    1. For the Archive File, click the Open button.

    2. From the Open dialog box, select the R2F_SAP_Distributed_vCenter.zip zip file that was downloaded in the package.

    3. Confirm that the Option field is set to Import.

    4. Click Import.

    5. In the Import Summary confirmation box, click OK.

      The Import Design dialog box closes.

  6. After the importing is complete, click the version number of the SAP Distributed System design.

    The SAP Distributed System window opens.

  7. Click the Designer tab. The topology design opens.

  8. For every component, the Properties pane appears on the right side of the window.

    Select every component and complete the values for the mandatory parameters according to the table in Appendix A: CSA Properties.

    Note: The mandatory parameters are marked with a red asterisk.

  9. After selecting each component, click Save in the Properties pane.

Step 4: Publish an offering in the CSA Marketplace Portal.

Note: For information on how to handle errors, see CSA Troubleshooting Guide.

  1. Log on to the Cloud Service Automation application management console.

    1. Go to https://"<CSA server>":8444/csa/login.

    2. Log on as a user with administrative privileges.

      The Cloud Service Automation management console opens.

  2. Navigate to Designs > Topology > Designer.

    The Topology Designs window opens.

  3. In the Search field in the right pane, enter SAP Distributed System.

  4. In the left pane, select the SAP Distributed System topology design.

  5. In the Topology Design Overview page, click Publish.

  6. In the Confirmation Required dialog box, click Yes.

    On the Topology Design Overview page, the green Published icon is visible—confirming publication.

  7. Click the Return button four times to return to the CSA management console home page and click Offerings.

  8. On the Offerings page, click Create.

  9. On the bottom of the right pane, click Import.

  10. In the Import Offering dialog box:

    1. For the Archive File, click the Open button.

    2. From the Open dialog box, select the SAP Distributed System Offering zip file that was downloaded in the package.

    3. Confirm that the Option field is set to Import.

    4. Click Import.

    5. In the Import Summary confirmation box, click OK.

      The Import Offering dialog box closes.

  11. In the Search field in the right pane, enter SAP Distributed System Offering.

  12. In the Search results, select the SAP Distributed System Offering offering.

  13. In the Offerings pane, select the Publishing tab and click Publish.

    The Publish Service Offering dialog box opens.

  14. Complete the following and click Publish.

    1. To Catalog. Select Global Shared Catalog.

    2. In Category. Select Application Services.

Step 5: Validate the implementation.

  1. Log on to the Cloud Service Automation Marketplace Portal.

    1. Go to https://localhost:8444/mpp.

    2. Log on as a user with Administrative privileges.

      The Cloud Service Automation Marketplace Portal opens.

  2. In the Sidebar Menu, select Browse Catalog.

    The Browse Catalog pane opens.

  3. In the Search field, search for SAP Distributed System Offering. When you see the SAP Distributed System Offering offering, the validation is complete.

Step 6: Deploy the integration.

  1. Log on to the Cloud Service Automation Marketplace Portal.

    1. Go to https://localhost:8444/mpp.

    2. Log on as a user with Administrative privileges.

      The Cloud Service Automation Marketplace Portal opens.

  2. In the Sidebar Menu, select Browse Catalog.

    The Browse Catalog pane opens.

  3. In the Search field, search for SAP Distributed System Offering.

  4. Select the SAP Distributed System Offering and complete all of the properties according to the table in Appendix A: CSA Properties.

  5. Click Checkout.

    The Service Checkout window opens.

  6. In the Service Checkout window, complete the required information and click Submit Request. A confirmation message is displayed saying the request has been placed.

Appendix A: CSA Properties

For a SAP component

The values in brackets in the Name column are the corresponding parameters/variables for the local_input.ini file.

Name Possible Values Description
CifsPassword
(scrCifsPassword)
  When cifs are the protocol for the DepotHost, you will probably need a password to access the Windows share.
CifsUsername
(scrCifsUsername)
Administrator When cifs are the protocol for the DepotHost, you will probably need a username to access the Windows share.
DatabaseVendor
(scrDatabaseVendor)
ADA
DB6
HDB
ORA
SYB

String denominating the database vendor:

ADA = MaxDB
DB6 = DB2
HDB = HANA DB
ORA = Oracle
SYB = Sybase ASE
DeploymentIpAddr (scrDeploymentIpAddr)   IP address on the management network used for deployment and configuration
DeploymentIpAddr_HDB (scrDeploymentIpAddr_HDB)   IP address of the SAP HANA database on the management network used for deployment and configuration
DepotHost (scrDepotHost) cifs:172.16.0.15 or nfs:172.16.0.15 Protocol and host name of the server hosting the software depot. Protocol can be either cifs (when using Windows shares) or nfs (when using Linux shares). <protocol>:<hostname/IP-address>
DepotName (scrDepotName) SWDEPOT Name of the export / share on the file server
DepotSapDirectory (scrDepotSapDirectory)   Name of the directory where the software is located on the export / share
DryRun
(scrDryRun)
true
false
If true, then a test run is executed without the SAP installation. Default: false
HostFunction (scrHostFunction)
standard
ascs
scs
pas
db
aas

The value of this input parameter controls the type of SAP component to be installed.

standard = 2-tier - ASCS/SCS, DB and PAS on one Host
ascs = 3-tier – Central Services for ABAP (ASCS instance)
scs = 3-tier – Central Services for Java (SCS instance)
pas = 3-tier - Primary Application Server (PAS instance)
db = 3-tier – Database (DB)
aas = Additional Application Server (AAS instance)
HostnameFQDN (scrHostnameFQDN)   Fully qualified domain name (FQDN) of the host on the production network
HostnameFQDN_HDB (scrHostnameFQDN_HDB)   FQDN of the SAP HANA database host on the production network
InstanceNumber (scrInstanceNumber)   Two-digit SAP Instance Number of the SAP system scheduled to be deployed
InstanceNumber_HDB (scrInstanceNumber_HDB)   Two-digit SAP HANA database instance number
IpAddr (scrIpAddr)   Corresponding IP address on the production network
IpAddr_HDB (scrIpAddr_HDB)   Corresponding IP address of the SAP HANA database on the production network
MasterPW_HDB (scrMasterPW_HDB)   Master password of the SAP HANA database
multipleOS (scrMultipleOS)
true
false
Only necessary for heterogeneous installations. Currently, only Linux is supported. Default: false
OperatingSystem Linux Currently, only Linux is supported.
OperatingSystem_HDB Linux Only Linux is supported for a SAP HANA database.
SapApplication (scrSapApplication)   Name of the SAP application to be installed
SapFlavour (scrSapFlavour)
ABAP
JAVA
Either ABAP or JAVA, depending on what kind of application stack will be installed
SapVersion (scrSapVersion)
*BS2013SR1
*BS2013SR2
*S4HANAONPREM1511

SAP version to be installed

BS2013SR1 = SAP Business Suite innovations 2013 SR1
BS2013SR2 = SAP Business Suite innovations 2013 SR2
S4HANAONPREM1511 = SAP S/4HANA on-premise 1511
SID (scrSID)   SAP System Identification (SID). Only three characters are allowed.
SID_HDB (scrSID_HDB)   SAP System Identification of the SAP HANA database host
sshPort 22 ssh port of the host to connect to
sshRootPassword   ssh root password of the host to connect to
sshRootUsername root ssh root user of the host to connect to

For a vCenter component

The values in brackets in the Name column are the corresponding parameters/variables for the local_input.ini file.

Name Description
clusterName Cluster Name that should be used
cpuCount Amount of CPUs to allocate to the virtual machine (VM)
customizationSpec Name of the vCenter Customization Specification to use for the VM
dataStore Data store to use for the deployment
hostSystem ESXi host where the VM should be deployed
memorySize Amount of memory in megabytes to allocate to the VM
password Not necessary
privateKey Not necessary
username Not necessary
vmFolder Name of the Vmware folder the VM should create
vmNamePrefix VM prefix that should be used for the Vmware name
vmResourcePool Resource pool that should be used
vmTemplateReference Name of the VMware template that should be deployed

If you have any comments or suggestions regarding this document, please send them by email to sw-doc@hpe.com.