designated resource pool and proceeds with the provisioning of all required 

software packages. After a successful provisioning operation, Tivoli 

Provisioning Manager marks the new server resource as used and moves its 

DCM representation from the resource pool to the Cluster definition.

4. The newly provisioned SAP application server is placed in the SAP logon 

group of the utilized SAP system and can be used by all users of this system. 

Tivoli Provisioning Manager then signals the Utility Business Services 

component that all workflows were executed successfully and the SAP 

application server is ready for use.

5. Utility Business Services now informs the customer that the subscription 

request has been completed and all resources associated to the offering are 

ready to use.

6. The Metrics service starts metering of this resource for later billing purposes.

7. The Optimizer then interacts with Tivoli Provisioning Manager and dictates 

the allocation and deallocation of new application servers based on current 

workload.

Existing IT infrastructure

In order to demonstrate the provisioning operations performed by IBM Dynamic 

Infrastructure for mySAP in this scenario, the following assumptions are made:

1. A functional management environment with IBM Tivoli Provisioning Manager 

V2.1 up and running. 

2. A functional SAP base system infrastructure running on zSeries.

Figure 2 on page 8 shows the IT infrastructure used in this scenario. This is the 

start point for us to create a working IBM Dynamic Infrastructure for mySAP 

environment.

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

7