Integration scenario overview

IBM Dynamic Infrastructure for mySAP relies on several components that must 

be installed and configured before any dynamic provisioning of application 

servers takes place. 

The IBM Dynamic Infrastructure for mySAP solution has the following main 

components:

An SAP base system consisting of:

  An SAP Central Instance server

This scenario uses an SAP Central Instance server running on SUSE 

SLES8 Linux  running on zSeries .

  A database server

This scenario uses a DB2  database server running on z/OS .

  Various static application servers. The number of application servers 

depends on workload and agreed service level objectives.

Infrastructure servers

  SAP Dialog Instance Master server

A server on which a reference installation for all Dialog Instances is 

performed and tested. This scenario uses an SAP Dialog Instance Master 

server running on SUSE SLES8 Linux running on zSeries.

  SAP Configuration Master server

A server on which the cloning configuration is maintained. This 

configuration is used during dynamic provision operations. This scenario 

uses an SAP Configuration Master server running on SUSE SLES8 Linux 

running on zSeries.

  Managed through server

This server receives and executes tasks that assist in the provisioning 

operations. The managed through server will be configured as a boot 

server in Tivoli Provisioning Manager. This scenario uses z/VM  to 

support the provisioning of Linux for zSeries servers.

Management environment

The management environment represents the environment that will manage 

the dynamic provisioning of SAP application servers. It consists of Tivoli 

Provisioning Manager and IBM Dynamic Infrastructure for mySAP software. 

The recommended topology used for the management environment is a 

two server architecture as follows:

  Server 1 running IBM DB2 Server and Tivoli Directory Server

4 

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