Figure 1   Subscription process workflow

1. The customer accesses the IBM Dynamic Infrastructure for mySAP user 

interface to subscribe to an offering. In doing this, the customer chooses an 

offering and sets several service level agreements to its subscription. 

2. The Utility Business Service component of IBM Dynamic Infrastructure for 

mySAP gathers and stores all property data connected with this subscription 

and generates a request to Tivoli Provisioning Manager to start the operations 

that set up and configure all resources needed by this subscription.

3. Tivoli Provisioning Manager then executes workflows and scripts that are 

provided by the IBM Dynamic Infrastructure for mySAP automation package, 

as well resources from other automation packages, depending on the target 

platform the SAP systems run on. In our case, the workflows create one or 

more new Linux on zSeries servers on our z/VM system, and install and 

configure an SAP application server on it.

For the subscription operation, the workflows create the necessary Data 

Center Model (DCM) infrastructure required for the subscription. The DCM 

entries are: Customer, Application, and Cluster definitions. The workflows 

proceed by provisioning servers to the defined cluster according to the details 

of the subscription. Tivoli Provisioning Manager allocates a server from the 

6 

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