Request to Fulfill Value Stream with SAP Best Practices |
|
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:
HP Cloud Service Automation (HP CSA)
HP Operation Orchestration (HP OO)
HPE SAP installation content packages
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.
Note: For the hardware and software requirements, see the product documentation.
Product | Version | Instructions |
---|---|---|
HP Cloud Service Automation |
|
For installation instructions, see HP Cloud Service Automation Version 4.50 Installation Guide. |
HP Operation Orchestration |
|
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.
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.
HP Cloud Service Automation. For more information, see HP Cloud Service Automation Version 4.50 Support Matrix.
HP Operation Orchestration. For more information, see System Requirements in HP Operations Orchestration Version 10.20 Installation Guide.
SAP Software. See the SAP Support Portal or the hardware partner to identify supported SAP hardware and software.
Select one of the following options:
Downloading and Importing Content for SAP S/4HANA with VMware vCenter on Linux
Downloading and Importing Content for SAP Standard System with VMware vCenter on Linux
Downloading and Importing Content for SAP Distributed System with VMware vCenter on Linux
Suspending and Resuming SAP System in the CSA Marketplace
Adding Application Server in the CSA Marketplace
Cancelling 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.
Use the following third-party products to prepare the environment content for SAP S/4HANA with VMware vCenter on Linux:
HPE SAP installation content packages
VMware vSphere 5.5u2
VMware vCenter Server
DHCP Server
DNS Server
NTP server
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.
System Sizing
For guidelines and recommendations regarding SAP system sizing, visit Sizing tool for SAP or consult your SAP administrator.
Operating System Requirements
Additional operating system packages, kernel settings, and other configurations are required for the SAP systems.
You must have access to the SAP support web pages to view and download the necessary SAP notes.
To access the SAP support pages where SAP notes are stored, you must have at least SAP S‑User with credentials for support access. If you do not have such an account, contact to your company's SAP super‑administrator or contact SAP and provide your company's contract information number.
SAP HANA Database, if needed
On the SAP HANA Platform web page, check the latest SAP HANA Master Guide and SAP HANA Server Installation Guide for important SAP Notes and additional information about the setup.
Relevant SAP Notes
SAP S/4HANA Installation
Download the SAP latest installation guide from https://help.sap.com
Relevant SAP Notes
171356. SAP software on Linux: General information
VMware Template Creation
Create a new VMware virtual machine for your SAP system.
Note: If you also plan to deploy the SAP HANA database on a virtual machine, you have to create an additional virtual machine for the database server.
For the operating system, select between SUSE Linux Enterprise Server and Red Hat Enterprise Linux. For the network configuration, you could create two network adapters—one for the management and another for the production network.
Create a new customization specification.
In the Computer Name step, select Use the virtual machine name, complete the Domain Name field, and click Next.
In the DNS and Domain Settings dialog box, enter your domain name in the Domain Name field. Provide at least the Primary DNS IP and also the DNS Search Path.
To support repeatable, automated SAP installations, it is crucial to store all necessary installation media at a central location—a software depot.
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)
Create a folder on your Windows server for the software depot, such as C:\SWDEPOT.
To share the software depot folder, right-click SWDEPOT and select Share with > Specific people.
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)
Create a folder on your Linux server for the software depot. # mkdir /SWDEPOT
Install the NFS Server package on your Linux host, if not already done.
Modify the exports file. # vi /etc/exports
Make the following entry for your share. /SWDEPOT *(fsid=0,ro,root_squash,sync)
Run exportfs to make the changes effective. # exportfs –a
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.
SWPM 1.0 SP09 for NW higher than 7.0x
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.
Log on to HP Operations Orchestration (HP OO).
Go to https://"<OO Server>":8443/oo.
Log on as a user with administrative privileges.
The OO Web Client main window opens.
In the left pane of the HP OO window, select Content Management.
In the Content Management pane, select Content Packs.
In the Content Packs pane, click the Deploy New Content icon.
In the Deploy New Content pane, click the Add files for deployment button.
Browse to the location of the content pack and select it.
Click Open and then click Deploy.
Log on to the Cloud Service Automation (CSA) application management console.
Go to https://"<CSA server>":8444/csa/login.
Log on as a user with administrative privileges.
The Cloud Service Automation management console opens.
Click Providers.
On the left side of the Providers pane, select VMware vCenter
On the right side of the Providers pane, the VMware vCenter opens. Click Create.
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:
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. |
Click Create.
On the "<Provider Name>" page, select the Properties tab and click DATACENTERNAME.
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.
Log on to the Cloud Service Automation application management console.
Go to https://"<CSA server>":8444/csa/login.
Log on as a user with administrative privileges.
The Cloud Service Automation management console opens.
Navigate to Designs > Topology > Designer.
The Topology Designs window opens.
In the left pane, select All Designs.
On the bottom of the right pane, click Import.
In the Import Design dialog box:
For the Archive File, click the Open button.
From the Open dialog box, select the R2F_SAP_S/4HANA_vCenter.zip zip file that was downloaded in the package.
Confirm that the Option field is set to Import.
Click Import.
In the Import Summary confirmation box, click OK.
The Import Design dialog box closes.
After the importing is complete, click the version number of the SAP S/4HANA System design.
The SAP S/4HANA System window opens.
Click the Designer tab. The topology design opens.
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.
After selecting each component, click Save in the Properties pane.
Note: For information on how to handle errors, see CSA Troubleshooting Guide.
Log on to the Cloud Service Automation application management console.
Go to https://"<CSA server>":8444/csa/login.
Log on as a user with administrative privileges.
The Cloud Service Automation management console opens.
Navigate to Designs > Topology > Designer.
The Topology Designs window opens.
In the Search field in the right pane, enter SAP S/4HANA System.
In the left pane, select the SAP S/4HANA System topology design.
In the Topology Design Overview page, click Publish.
In the Confirmation Required dialog box, click Yes.
On the Topology Design Overview page, the green Published icon is visible—confirming publication.
Click the Return button four times to return to the CSA management console home page and click Offerings.
On the Offerings page, click Create.
On the bottom of the right pane, click Import.
In the Import Offering dialog box:
For the Archive File, click the Open button.
From the Open dialog box, select the SAP S/4HANA Offering zip file that was downloaded in the package.
Confirm that the Option field is set to Import.
Click Import.
In the Import Summary confirmation box, click OK.
The Import Offering dialog box closes.
In the Search field in the right pane, enter SAP S/4HANA Offering.
In the Search results, select the SAP S/4HANA Offering offering.
In the Offerings pane, select the Publishing tab and click Publish.
The Publish Service Offering dialog box opens.
Complete the following and click Publish.
To Catalog. Select Global Shared Catalog.
In Category. Select Application Services.
Log on to the Cloud Service Automation Marketplace Portal.
Go to https://localhost:8444/mpp.
Log on as a user with Administrative privileges.
The Cloud Service Automation Marketplace Portal opens.
In the Sidebar Menu, select Browse Catalog.
The Browse Catalog pane opens.
In the Search field, search for SAP S/4HANA Offering. When you see the SAP S/4HANA Offering offering, the validation is complete.
Log on to the Cloud Service Automation Marketplace Portal.
Go to https://localhost:8444/mpp.
Log on as a user with Administrative privileges.
The Cloud Service Automation Marketplace Portal opens.
In the Sidebar Menu, select Browse Catalog.
The Browse Catalog pane opens.
In the Search field, search for SAP S/4HANA Offering.
Select the SAP S/4HANA Offering and complete all of the properties according to the table in Appendix A: CSA Properties.
Click Checkout.
The Service Checkout window opens.
In the Service Checkout window, complete the required information and click Submit Request. A confirmation message is displayed saying the request has been placed.
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 |
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.
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.
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.
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.
Use the following third-party products to prepare the environment content for SAP Standard System with VMware vCenter on Linux:
HPE SAP installation content packages
VMware vSphere 5.5u2
VMware vCenter Server
DHCP Server
DNS Server
NTP server
The following prerequisites must be configured in the VMware vCenter before deploying the SAP Standard System with VMware vCenter on Linux.
System Sizing
For guidelines and recommendations regarding SAP system sizing, visit Sizing tool for SAP or consult your SAP administrator.
Operating System Requirements
Additional operating system packages, kernel settings, and other configurations are required for the SAP systems.
You must have access to the SAP support web pages to view and download the necessary SAP notes.
To access the SAP support pages where SAP notes are stored, you must have at least SAP S‑User with credentials for support access. If you do not have such an account, contact to your company's SAP super‑administrator or contact SAP and provide your company's contract information number.
SAP HANA Database, if needed
On the SAP HANA Platform web page, check the latest SAP HANA Master Guide and SAP HANA Server Installation Guide for important SAP Notes and additional information about the setup.
Relevant SAP Notes
SAP S/4HANA Installation
Download the SAP latest installation guide from https://help.sap.com
Relevant SAP Notes
171356. SAP software on Linux: General information
VMware Template Creation
Create a new VMware virtual machine for your SAP system.
Note: If you also plan to deploy the SAP HANA database on a virtual machine, you have to create an additional virtual machine for the database server.
For the operating system, select between SUSE Linux Enterprise Server and Red Hat Enterprise Linux. For the network configuration, you could create two network adapters—one for the management and another for the production network.
Create a new customization specification.
In the Computer Name step, select Use the virtual machine name, complete the Domain Name field, and click Next.
In the DNS and Domain Settings dialog box, enter your domain name in the Domain Name field. Provide at least the Primary DNS IP and also the DNS Search Path.
To support repeatable, automated SAP installations, it is crucial to store all necessary installation media at a central location—a software depot.
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)
Create a folder on your Windows server for the software depot, such as C:\SWDEPOT.
To share the software depot folder, right-click SWDEPOT and select Share with > Specific people.
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)
Create a folder on your Linux server for the software depot. # mkdir /SWDEPOT
Install the NFS Server package on your Linux host, if not already done.
Modify the exports file. # vi /etc/exports
Make the following entry for your share. /SWDEPOT *(fsid=0,ro,root_squash,sync)
Run exportfs to make the changes effective. # exportfs –a
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.
SWPM 1.0 SP09 for NW higher than 7.0x
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.
Log on to HP Operations Orchestration (HP OO).
Go to https://"<OO Server>":8443/oo.
Log on as a user with administrative privileges.
The OO Web Client main window opens.
In the left pane of the HP OO window, select Content Management.
In the Content Management pane, select Content Packs.
In the Content Packs pane, click the Deploy New Content icon.
In the Deploy New Content pane, click the Add files for deployment button.
Browse to the location of the content pack and select it.
Click Open and then click Deploy.
Log on to the Cloud Service Automation (CSA) application management console.
Go to https://"<CSA server>":8444/csa/login.
Log on as a user with administrative privileges.
The Cloud Service Automation management console opens.
Click Providers.
On the left side of the Providers pane, select VMware vCenter.
On the right side of the Providers pane, the VMware vCenter opens. Click Create.
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:
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. |
Click Create.
On the "<Provider Name>" page, select the Properties tab and click DATACENTERNAME.
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.
Log on to the Cloud Service Automation application management console.
Go to https://"<CSA server>":8444/csa/login.
Log on as a user with administrative privileges.
The Cloud Service Automation management console opens.
Navigate to Designs > Topology > Designer.
The Topology Designs window opens.
In the left pane, select All Designs.
On the bottom of the right pane, click Import.
In the Import Design dialog box:
For the Archive File, click the Open button.
From the Open dialog box, select the R2F_SAP_Standard_vCenter.zip zip file that was downloaded in the package.
Confirm that the Option field is set to Import.
Click Import.
In the Import Summary confirmation box, click OK.
The Import Design dialog box closes.
After the importing is complete, click the version number of the SAP Standard System design.
The SAP Standard System window opens.
Click the Designer tab. The topology design opens.
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.
After selecting each component, click Save in the Properties pane.
Note: For information on how to handle errors, see CSA Troubleshooting Guide.
Log on to the Cloud Service Automation application management console.
Go to https://"<CSA server>":8444/csa/login.
Log on as a user with administrative privileges.
The Cloud Service Automation management console opens.
Navigate to Designs > Topology > Designer.
The Topology Designs window opens.
In the Search field in the right pane, enter SAP Standard System.
In the left pane, select the SAP Standard System topology design.
In the Topology Design Overview page, click Publish.
In the Confirmation Required dialog box, click Yes.
On the Topology Design Overview page, the green Published icon is visible—confirming publication.
Click the Return button four times to return to the CSA management console home page and click Offerings.
On the Offerings page, click Create.
On the bottom of the right pane, click Import.
In the Import Offering dialog box:
For the Archive File, click the Open button.
From the Open dialog box, select the SAP Standard System Offering zip file that was downloaded in the package.
Confirm that the Option field is set to Import.
Click Import.
In the Import Summary confirmation box, click OK.
The Import Offering dialog box closes.
In the Search field in the right pane, enter SAP Standard System Offering.
In the Search results, select the SAP Standard System Offering offering.
In the Offerings pane, select the Publishing tab and click Publish.
The Publish Service Offering dialog box opens.
Complete the following and click Publish.
To Catalog. Select Global Shared Catalog.
In Category. Select Application Services.
Log on to the Cloud Service Automation Marketplace Portal.
Go to https://localhost:8444/mpp.
Log on as a user with Administrative privileges.
The Cloud Service Automation Marketplace Portal opens.
In the Sidebar Menu, select Browse Catalog.
The Browse Catalog pane opens.
In the Search field, search for SAP Standard System Offering. When you see the SAP Standard System Offering offering, the validation is complete.
Log on to the Cloud Service Automation Marketplace Portal.
Go to https://localhost:8444/mpp.
Log on as a user with Administrative privileges.
The Cloud Service Automation Marketplace Portal opens.
In the Sidebar Menu, select Browse Catalog.
The Browse Catalog pane opens.
In the Search field, search for SAP Standard System Offering.
Select the SAP Standard System Offering and complete all of the properties according to the table in Appendix A: CSA Properties.
Click Checkout.
The Service Checkout window opens.
In the Service Checkout window, complete the required information and click Submit Request. A confirmation message is displayed saying the request has been placed.
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 |
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.
Use the following third-party products to prepare the environment content for SAP Distributed System with VMware vCenter on Linux:
HPE SAP installation content packages
VMware vSphere 5.5u2
VMware vCenter Server
DHCP Server
DNS Server
NTP server
The following prerequisites must be configured in the VMware vCenter before deploying the SAP Distributed System with VMware vCenter on Linux.
System Sizing
For guidelines and recommendations regarding SAP system sizing, visit Sizing tool for SAP or consult your SAP administrator.
Operating System Requirements
Additional operating system packages, kernel settings, and other configurations are required for the SAP systems.
You must have access to the SAP support web pages to view and download the necessary SAP notes.
To access the SAP support pages where SAP notes are stored, you must have at least SAP S‑User with credentials for support access. If you do not have such an account, contact to your company's SAP super‑administrator or contact SAP and provide your company's contract information number.
SAP HANA Database, if needed
On the SAP HANA Platform web page, check the latest SAP HANA Master Guide and SAP HANA Server Installation Guide for important SAP Notes and additional information about the setup.
Relevant SAP Notes
SAP S/4HANA Installation
Download the SAP latest installation guide from https://help.sap.com
Relevant SAP Notes
171356. SAP software on Linux: General information
VMware Template Creation
Create a new VMware virtual machine for your SAP system.
Note: If you also plan to deploy the SAP HANA database on a virtual machine, you have to create an additional virtual machine for the database server.
For the operating system, select between SUSE Linux Enterprise Server and Red Hat Enterprise Linux. For the network configuration, you could create two network adapters—one for the management and another for the production network.
Create a new customization specification.
In the Computer Name step, select Use the virtual machine name, complete the Domain Name field, and click Next.
In the DNS and Domain Settings dialog box, enter your domain name in the Domain Name field. Provide at least the Primary DNS IP and also the DNS Search Path.
To support repeatable, automated SAP installations, it is crucial to store all necessary installation media at a central location—a software depot.
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)
Create a folder on your Windows server for the software depot, such as C:\SWDEPOT.
To share the software depot folder, right-click SWDEPOT and select Share with > Specific people.
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)
Create a folder on your Linux server for the software depot. # mkdir /SWDEPOT
Install the NFS Server package on your Linux host, if not already done.
Modify the exports file. # vi /etc/exports
Make the following entry for your share. /SWDEPOT *(fsid=0,ro,root_squash,sync)
Run exportfs to make the changes effective. # exportfs –a
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.
SWPM 1.0 SP09 for NW higher than 7.0x
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.
Log on to HP Operations Orchestration (HP OO).
Go to https://"<OO Server>":8443/oo.
Log on as a user with administrative privileges.
The OO Web Client main window opens.
In the left pane of the HP OO window, select Content Management.
In the Content Management pane, select Content Packs.
In the Content Packs pane, click the Deploy New Content icon.
In the Deploy New Content pane, click the Add files for deployment button.
Browse to the location of the content pack and select it.
Click Open and then click Deploy.
Log on to the Cloud Service Automation (CSA) application management console.
Go to https://"<CSA server>":8444/csa/login.
Log on as a user with administrative privileges.
The Cloud Service Automation management console opens.
Click Providers.
On the left side of the Providers pane, select VMware vCenter.
On the right side of the Providers pane, the VMware vCenter opens. Click Create.
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:
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. |
Click Create.
On the "<Provider Name>" page, select the Properties tab and click DATACENTERNAME.
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.
Log on to the Cloud Service Automation application management console.
Go to https://"<CSA server>":8444/csa/login.
Log on as a user with administrative privileges.
The Cloud Service Automation management console opens.
Navigate to Designs > Topology > Designer.
The Topology Designs window opens.
In the left pane, select All Designs.
On the bottom of the right pane, click Import.
In the Import Design dialog box:
For the Archive File, click the Open button.
From the Open dialog box, select the R2F_SAP_Distributed_vCenter.zip zip file that was downloaded in the package.
Confirm that the Option field is set to Import.
Click Import.
In the Import Summary confirmation box, click OK.
The Import Design dialog box closes.
After the importing is complete, click the version number of the SAP Distributed System design.
The SAP Distributed System window opens.
Click the Designer tab. The topology design opens.
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.
After selecting each component, click Save in the Properties pane.
Note: For information on how to handle errors, see CSA Troubleshooting Guide.
Log on to the Cloud Service Automation application management console.
Go to https://"<CSA server>":8444/csa/login.
Log on as a user with administrative privileges.
The Cloud Service Automation management console opens.
Navigate to Designs > Topology > Designer.
The Topology Designs window opens.
In the Search field in the right pane, enter SAP Distributed System.
In the left pane, select the SAP Distributed System topology design.
In the Topology Design Overview page, click Publish.
In the Confirmation Required dialog box, click Yes.
On the Topology Design Overview page, the green Published icon is visible—confirming publication.
Click the Return button four times to return to the CSA management console home page and click Offerings.
On the Offerings page, click Create.
On the bottom of the right pane, click Import.
In the Import Offering dialog box:
For the Archive File, click the Open button.
From the Open dialog box, select the SAP Distributed System Offering zip file that was downloaded in the package.
Confirm that the Option field is set to Import.
Click Import.
In the Import Summary confirmation box, click OK.
The Import Offering dialog box closes.
In the Search field in the right pane, enter SAP Distributed System Offering.
In the Search results, select the SAP Distributed System Offering offering.
In the Offerings pane, select the Publishing tab and click Publish.
The Publish Service Offering dialog box opens.
Complete the following and click Publish.
To Catalog. Select Global Shared Catalog.
In Category. Select Application Services.
Log on to the Cloud Service Automation Marketplace Portal.
Go to https://localhost:8444/mpp.
Log on as a user with Administrative privileges.
The Cloud Service Automation Marketplace Portal opens.
In the Sidebar Menu, select Browse Catalog.
The Browse Catalog pane opens.
In the Search field, search for SAP Distributed System Offering. When you see the SAP Distributed System Offering offering, the validation is complete.
Log on to the Cloud Service Automation Marketplace Portal.
Go to https://localhost:8444/mpp.
Log on as a user with Administrative privileges.
The Cloud Service Automation Marketplace Portal opens.
In the Sidebar Menu, select Browse Catalog.
The Browse Catalog pane opens.
In the Search field, search for SAP Distributed System Offering.
Select the SAP Distributed System Offering and complete all of the properties according to the table in Appendix A: CSA Properties.
Click Checkout.
The Service Checkout window opens.
In the Service Checkout window, complete the required information and click Submit Request. A confirmation message is displayed saying the request has been placed.
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 |
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.