accommodate all of our base SAP processing. As a backup, we can make use of 

the SAPDI server for additional base resources if the need arises. Your 

configuration may vary from this setup and may require additional resources. 

Our SAPCI system NFS exports several SAP file systems except for 

/sapmnt/M5D/exe, as well as some of the SAP CDs that are needed to install 

new systems. We NFS mounted then exported the following file systems:

/usr/sap/M5D

/usr/sap/trans

/sapmnt

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 28 shows the actual coding of the text.

Example 28   SAPCI snmpd.conf entry

rocommunity public default

As this SAP system was installed prior to the IBM Dynamic Infrastructure setup, 

we originally defined a static real network address for this system's network 

connection. If we had to do this over, the team would have looked into setting up 

a vswitch or Hipersockets for this connection.

Disk drive layout for SAPCI

The SAP Central Instance was installed as a normal SAP installation. The VM 

user direct entry depicted in Example 29 on page 46 shows that we defined one 

VM minidisk for the guest 191 A disk, and 12 disk drives to hold the Linux file 

system, the SAP file system, and the assorted CD ROMs that must be mounted 

for SAP install work to proceed.

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

Disk 0202 is assigned to /boot. Disks 0203 and 0204 are assigned to /root. This 

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

Disks 0205 through 0208, which are assigned to /sapcds, hold the various SAP 

installation CD ROMs. Disk 0209 is assigned to /install and will be the primary 

SAP installation directory for status and logs. Disk 0210 is assigned to the 

/usr/sap/trans file system, disk 0211 is assigned to /usr/sapM5D, and disk 0212 

is assigned to /sapmnt: these are the SAP file systems that are accessed by all 

SAP systems in the landscape. 

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

45