The suse sapinit.rpm installs several SAP related scripts/parms to assist with the 

proper running of SAP. After installation of the RPM, you must modify 

/etc/sysconfig/sapr3 for the number of systems to auto start as well as their 

corresponding SAPSIDs.

Implement the new changes by entering the following command as root:

insserv  f /etc/init.d/sapr3

The saplocales RPM provides the SAP specific configuration changes required 

to run SAP on Linux for zSeries. No manual configuration work is required after 

successful installation of the RPM.

We then installed the Java SDK 1.3.1.8.0 on our Linux systems per the SAP 

documentation.

`

IBM Dynamic Infrastructure for mySAP customizations for SAP

We created an SAP logon group to hold the dynamically provisioned servers 

created by the IDI workflows. Our SAP logon group for these servers is called 

idigrp

 and contains the planned servers for dynamic provisioning.

We also created separate logon groups for the day to day running of the SAP 

system, and these contained the SAP central instance and base dialog instance.

Table 1   Logon groups

Group

System

admin

sapci_M5D_00

admin

sapdi_M5D_00

idigrp

idadm001_M5D_00

idigrp

idadm002_M5D_00

idigrp

IDADM002_M5D 00

admin

sapci_M5D_00

The SAP Central Instance (SAPCI)

The SAPCI system was installed using standard SAP installation tools. Refer to 

SAP R/3 Enterprise on UNIX: IBM DB2 Universal Database for z/OS and 

OS/390

, Version 1, November 2003

The SAP Central Instance is set up to run all of the SAP processes (Dialog, 

Update, Enqueue, Batch, Message, Gateway, and Spool). It is large enough to 

44 

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