To minimize the amount of disk utilized for this project, the SAP specific file 

systems for this dialog instance are also contained within these four disk drives 

that hold the standard Linux operating system.

The IBM Dynamic Infrastructure for mySAP documentation states that SNMP 

must be enabled on all SAP systems. We configured the SNMP control file 

(snmpd.conf) to allow read only access to Public and ensured that the SNMP 

daemon was automatically started at system boot. Example 33 shows actual 

coding of the text.

Example 33   SAPDI snmpd.conf entry

rocommunity public default

The IBM DI SAP Configuration Master Instance (SAPCM)

The SAPCM system was build by running VM scripts to clone the disk drives 

from SAPDI. These scripts can be referenced in 

IBM Dynamic Infrastructure for 

MySAP Business Suite on IBM zSeries,

 SG24 6473.

The SAP Configuration Master Instance is the clone source for building the 

dynamically provisioned servers. It is meant to be a static system that matches 

the SAP Dialog Instance Master System at all times. See  SAP base system 

overview  on page 9 for how we set up this system. Your configuration may vary 

from this setup and may require additional resources.

Since the Dialog Instance Master Server was configured for SNMP, this system 

will also be configured as such. 

We configured a static virtual network address for our network adapter on this 

system as evidenced by the NICDEF statement in Example 34 on page 50. 

Disk drive layout for SAPCM

The SAP Configuration Master Dialog Instance was created by cloning the 

SAPDI system and customized during boot by running the /etc/init.d/boot.local 

script at system load time. 

The VM user direct entry depicted in Example 34 on page 50 shows that we 

defined one VM minidisk for the guest 191 A disk and four disk drives to hold the 

Linux file system and the SAP file system. Additional data was accessed by 

mounting required disk drives from the SAPCI instance via NFS. 

The first Linux on zSeries disk is 0C01, and it is assigned as the swap partition. 

Disk 0C02 is assigned to /boot. Disks 0C03 and 0C04 are assigned to /root. This 

makes up the base Linux file systems needed to start Linux.

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

49