TPM toolkit for SmartCloud Orchestrator, part 1
by C. J. Meidlinger
While teaching a SmartCloud Orchestrator (SCO) workshop recently, a student asked about calling Tivoli Provisioning Manager (TPM) from SCO. Although SCO certainly provides tools for building such integrations, it is easier and faster to use integrations built by others. If SCO does not provide a ready-to-use integration for TPM out of the box, the first place one should look is the ISM Cloud Marketplace. A quick check there showed us the IBM SmartCloud Orchestrator Content Pack for Tivoli Provisioning Manager.
The documentation describes the elements of the content pack and how to use them. In a nutshell, the content pack provides new business objects, coach views, and integration services for TPM. The business objects are used for describing TPM servers in your environment, describing DCM interaction requests, and describing provisioning workflow requests. The coach views provide the HTML-based interfaces that will be exposed in the SCO interface when accessing the TPM integration services. The integration services are the human services and business process definitions that SCO uses to call the correct coach view and then process the request using information provided by the user.
To install the TPM content pack, go to the Toolkts tab in the SCO Business Process Center UI and click the Import Toolkit link on the right side of the page. Select the SCOrchestrator_TPM_Integration_Toolkit.twx file that you downloaded from the ISM Cloud Marketplace and you're ready to start using the toolkit.
The TPM toolkit for SCO has a handful of pre-built custom operations that allow you to interact with a TPM server without any BPM programming required. Simply register the corresponding human services and business process definitions with SCO as self-service offerings. There are operations for adding, modifying, and deleting TPM servers within SCO; creating, retrieving, updating, and deleting DCM objects; and running provisioning workflows.
I loaded the toolkit into a SCO 2.2 fixpack 1 environment and registered a version 7.2.0 TPM server. The supported level of TPM is 7.2.1 ifix 4, but I already had the 7.2.0 image in my development environment and figured it would be close enough for my purposes.
After registering the TPM server, I ran the following DCM query to test: /server/@name
The host names returned should look familiar to anyone who has attended the TPM 7.2 Fundamentals class. The following is a small excerpt from the SystemOut.log file for BPM on kersrv-3. This shows the DCMQuery and the result.
 00024727 DcmManager I Created a proxy session to TPM 10.10.2.202:8777
 00024727 DcmManager I DCM select query /server/@name
 00024727 wle_javascrip I Result tpm.tivoli.edu, linclient.tivoli.edu, winclient.tivoli.edu, osd_targ.tivoli.edu
I also ran the No_operation workflow with the following result in SystemOut.log:
 0002479e WorkflowManag I Getting logs of request 7002
 0002479e wle_javascrip I Workflow execution log
 0002479e wle_javascrip I Request ID: 7002
Start workflow: 'No_operation'
End workflow: 'No_operation'
As you can see, installing and setting up the TPM toolkit for SCO is easy and gives us the building blocks needed for creating TPM automation with SCO. In part two, I will show how to use these building blocks to create a simple solution that a Cloud customer might use. If you have suggestions for a sample TPM integration that you'd like to see, please post them in the comments section and I will consider them.
C. J. Meidlinger is a technical enablement specialist with IBM Cloud and Smarter Infrastructure. He can sometimes be critical of computing technologies but he is a big fan of both SmartCloud Orchestrator and Tivoli Provisioning Manager.