SAP base system overview

Each customer has an SAP base system that consists of the database and core 

SAP processes instances required to run the SAP system. Each base system 

may be planned and deployed differently. The provisioning and deprovisioning of 

the SAP base system is outside of the scope of IBM Dynamic Infrastructure for 

mySAP. 

The SAP base system must be up and running before any automated 

provisioning operation can occur. However, there are special considerations for 

the SAP Central Instance, SAP Dialog Instance, and SAP Configuration Master 

systems when considering IBM Dynamic Infrastructure for mySAP. Refer to 

IBM 

Dynamic Infrastructure Enterprise Edition for mySAP Business Suite Planning,

BOEE EUIPL 00 for details. 

For the purpose of this scenario, SAP System 4.7 Enterprise Kit with kernel 

version 6.20 patch level 1211 is used. Also the SAP support pack 47 must be 

installed as required by IBM Dynamic Infrastructure for mySAP. The level of 

maintenance for your system will vary depending on the version of SAP.

The manuals recommend that the SAP Configuration Master hosts the SAP 

runtime that will be accessed via NFS by the provisioned SAP application 

servers. The SAP runtime must be accessible at all times any provisioned SAP 

application server is running. In our scenario, the SAP Configuration Master 

contains the SAP runtime locally, and as all the provisioned SAP application 

servers will be created as clones of the SAP Configuration Master server, the 

SAP runtime will be available to the SAP application servers locally as well.

Note:

 If your environment is not set up similarly or has multiple sets of cloned 

disks you may find it necessary or convenient to mount the file system 

containing the SAP runtime on each dynamically provisioned clone from the 

SAP Configuration Master.

The IBM Dynamic Infrastructure for mySAP solution has requirements around 

how the VM minidisks are defined for the SAP Configuration Master server. If the 

workflow defaults are used, the z/VM minidisks that are to be cloned must have 

DASD device addresses in the form of 1CXX to be recognized and copied during 

the provisioning operation. All z/VM minidisk DASD device addresses of the form 

0CXX are the basis when creating the SAP Configuration Master server.

When the SAP Configuration Master server setup is complete, the content of the 

0CXX minidisks must be copied to the 1CXX minidisks for cloning. All other 

DASD device addresses from 2XXX through FXXX are unused by the default 

provisioning operation. For details about how the SAP Configuration Master has 

been defined in our scenario, refer to  SAP master systems setup  on page 43.

Dynamic Provisioning of SAP Environments using IBM DI for mySAP and Tivoli Provisioning Manager

9