IBM Service Management and Tivoli Provisioning Manager 7.2 Integration

Tutorial (Software and Patch Deployment, Management and Customization)

1. Product Versions

Compatible software versions required for this integration tutorial are: Maximo Base Services (MBS) 7.1.1.6 Tivoli Service Request Manager (TSRM) 7.2.0.1 Change & Configuration Management Database (CCMDB) 7.2.0.1 Tivoli Provisioning Manager (TPM) 7.2 Tivoli Application Dependency Discovery Manager (TADDM) 7.2 IBM Tivoli Integration Composer (ITIC) 7.2.0.1

2. Prerequisites

Before you run the tutorial, ensure that: • Tivoli Provisioning Manager (TPM) 7.2 is installed and running. • Tivoli Service Request Manager (TSRM) is installed and running. • Tivoli Application Dependency Discovery Manager (TADDM) is installed and

running (typically on a remote node). • IBM Tivoli Integration Composer (ITIC) is installed and configured (can be on

a remote node). • Change and Configuration Management Database (CCMDB) is installed and

running. • Targets have been discovered in TADDM by TADDM sensors. Data in

TADDM has been synchronized back to the TPM data center model (DCM) by running TADDM discovery configuration in TPM.

• Actual configuration items (ACTCI) for targets are created in CCMDB by us-ing TADDM ITIC adaptor for CCMDB.

• ACTCI have been promoted to configuration items (CIs) via CI promotion process, or by using Deployers Workbench (DW).

• Tivoli Process Automation Engine (TPAE), CCMDB and TSRM are config-ured for business use. (Examples of business configurations: organization creation, GL account structure, GL accounts, clearing account for each organi-zation, currency codes, sites setup, definition of the default site/location for us-ers, definition of the user roles).

• Software, patch and file repositories for software and patch deployment and management are configured in the provisioning server and are populated with the necessary binaries.

2. Run Software Deployment via IBM Service Management process

1. Log on to the provisioning server. 2. To create a service ticket :

Go To Service Desk Service Requests or: Go To Self Service Service Requests Create Service Request Note: The Service Desk application is available only to selected service request-ors, as defined in the user role setup.

3. On the Service Requests page, click the New Service Request button to create a new service request.

4. Fill out the Service Request form. Note: You can use the TPSWDEPLOYMENT classification to specify the soft-ware deployment attributes. There are three out of the box classifications for software and patch deployment and management. These are:

• TPSWDEPLOYMENT – software deployment • TPSWMANAGEMENT – software instance start or restart • TPPATCHDEPLOYMENT – patch deployment.

Figure 1: Self-service - Create service request form 5. Specify the classification attributes when creating the service order. In the Self

Service application, use the Attributes section to enter the attribute value for the request. You can also defer this step to the service manager or change manager to specify the classification attributes later. For example, specify the software prod-uct name to deploy on the target.

You can defer this step. The service manager or change manager can specify the classification attributes later, in the Service Request form. If you decide to do so, click on the Specifications tab in the Service Request form.

Figure 2: Self-service - Specify the classification attributes

6. Save (in the Service Desk application) or submit (in the Self Service application)

the form after completing it. 7. You can include more than one CI as the target of the service request by adding

new rows to the Multiple Assets, Locations and CIs section. 8. Generate a Work Order by logging on to the provisioning server as a service re-

quest manager. Route the service ticket to create a new work order based on the service description described below.

9. On the newly created service request page: Click Select Action Workflow Route Workflow

10. Specify TPSRTOWO:Route Service Request Work Order on the pop up window when prompted. Click OK.

11. On the Manual Input pop-up window, select Create Work Order. Click OK to create a new work order.

Figure 3: Create Work Order from the Service Request

12. A new work order is created based on the service ticket.

The Work Order Tracking page displays.

Figure 4: New Work Order

13. All attributes from the service ticket are copied into the new work order. The

work order also includes the defined configuration items or targets (single or mul-tiple targets). A default Job Plan template called TPJPTEMPL is associated with the work or-der. The Job Plan template can be used to define a set of the tasks required to be performed for this work order. Tivoli Provisioning Manager provides a default Job Plan template including an out of the box provisioning task to be performed. The classifications and the assisted workflow for running the provisioning tasks are copied to the tasks in this newly created work order.

14. In a change manager role, you can modify the job plan template by modifying the tasks on the Job Plan page. To disable the job plan associated with TPJPTEMPL, or to remove the associa-tion when routing the service ticket to the workflow, follow these steps:

a. Go To System Configuration Platform Configuration Actions b. Search for “TPASSOCJOBPLAN”

c. On the details page, remove the value “TPJPTEMPL” from the Parame-ter/Attribute field or replace it with a different parameter. Note: This value is a Job Plan name. A user in a change manager role can customize this value to automatically associate it with the work order when routing the service ticket to the work order.

Figure 5: Job Plan Template

15. The new work order can be assigned to a change manager for approval. The

change manager marks the work order status to be in progress. To assign the new owner, from the work order tracking page, select Action Select Owner.

16. Log on to the provisioning server. Ensure that you have a change manager role. Find the new work order. Review the content, define additional work order activi-ties from the work order plan, approve it and then mark the order in progress. From the work order tracking page, select Action Change Status

17. When the work order status is in progress, log on to the provisioning server. En-

sure that your user role is deployment specialist to be able to find the work order. Go To Work Orders Work Order Tracking On the Plans tab expand the provision computer with custom application task. Click the link beside the Reference WO field to go to this specific work order ac-tivity task for provisioning.

Figure 6: Work Order Tasks

The assisted workflow is set according to the use case (software deployment, soft-ware patch deployment or software management):

Figure 7: Start Assisted Workflow

18. In a Deployment Specialist user role, click the Start Assisted Workflow button to

initiate a provisioning task. If deploying software, this action retrieves the soft-ware product classification attributes and the targets information from the work order or the work order activity task. This input is then used by the provisioning workflows. In a Deployment Specialist role, you can schedule a provisioning workflow task from the work order Activities and Tasks page by specifying the scheduled time in the Scheduled Start input filed.

19. Click Start Assisted Workflow. On the Provisioning Task Tracking page you can monitor the provisioning task status.

Figure 8: Provisioning Task Tracking Page

20. In a Deployment Specialist role, click the link beside the Base Services Task field

on the Provisioning Task Tracking page to go back to the work order Activities and Tasks page.

21. If the provisioning task runs successfully, the task activity status is automatically marked COMP on the work order Activities and Tasks page. If all the activity tasks in a work order are marked COMP, the work order and the service ticket that is associated with it will automatically be marked resolved.

3. Run Software Management via IBM Services Manager process

1. After a software product is deployed, the change manager can create a new work

order or a new activity task under the same work order and run the software man-agement assisted workflow (for example, to restart WebSphere Administration Server and a DB2 instance).

2. To create a new activity task, go to the Work Orders Work Orders Tracking. On the Plans tab associate the software management classification TPSWMAN-AGEMENT to the activity task (Restart Tomcat server instance in the following example).

Figure 9: Software Management Tasks

3. Click the link beside the References field to launch this activity task.

4. Select an assisted workflow TPSOFTMGMT from the Assisted Workflow list.

5. Select the software instance in the Attributes section on the work order Activities

and Tasks page.

If this activity task is not yet approved and the status is not yet in progress, change this activity task status to in progress.

Figure 10: Software Management Assisted Workflow and Classification Attributes

6. In a Deployment Specialist role, you can manage the server instance by using a

provisioning workflow: Click the Start Assisted Workflow button to invoke the provisioning task.

4. Run Patch Deployment via IBM Services Manager process

The process of running patch deployment via IBM Services Manager (ISM) is the same as running software deployment. The classification used when creating a service request or a work order is called „TPPATCHDEPLOYMENT‟. When this classification is se-lected, you can specify a software patch name and other installation options as the classi-fication attributes. These attributes are used by the provisioning task to deploy patches. Patch deployment supports both deployment engine and scalable distribution infrastruc-ture depending on the service access point types defined for the target. Multiple targets can be selected for both software and patch deployment and management. To define the multiple targets, use the Multiple Assets, Locations and Configuration Items section on the service ticket or the work order detail page.

5. Assisted Workflow and Action Customization

You can create your own assisted workflows and define your own actions to call the pro-visioning tasks. To create the action you can use a Java Class or a Jython script. Tivoli Provisioning Manager 7.2 enables the Automation Scripts application from the TPAE UI, and also provides examples on how to create and configure Jython scripts or Java code for the action running from the assisted workflow. The examples are available at: $TIO_HOME/samples/ismint/. You can use Jython scripting to create actions and then define an assisted workflow to call the provisioning tasks. Examples of the basic Tivoli Provisioning Manager device ping operation and software product uninstall operation using Jython are available at: $TIO_HOME/samples/ismint/ismint_jython_actions.zip). You can use the example Jython scripts to learn how to build your own assisted workflow and customized actions. (Note: The sample code contained is provided to you as is.) Follow these steps to install the Jython examples:

1. Go to %TIO_HOME%samples/ismint/ and copy ismint_jython_actions.zip to the administration workstation. For example: c:\temp\samples\ (Create the folder if it is not yet created.)

2. Extract ismint_jython_actions.zip on the administration workstation For example: c:\temp\samples\

Note: Make sure that following four XML files are extracted under c:\temp\samples\: TPDevicePingAutoScript.xml TPDevPingProcess.xml TPSWProductUninstallAutoScript.xml TPSWProductUninstallProcess.xml

3. Go to the SMP directory and import the examples to the provisioning server by performing the following:

- cd c:\ibm\SMP\maximo\tools\maximo\internal\ - ImportObject -directory=c:\temp\samples\

Verify the import: I. Verify that the two sample assisted workflows are imported:

Go To System Configuration Platform Configuration Workflow De-signer and search for the following processes:

a) TPDEVPING – assisted workflow for Tivoli Provisioning Manager device ping operations

b) TPUNINSTSW – assisted workflow for Tivoli Provisioning Manager software product uninstall

II. Verify the Jython script and its action:

Go To Script Management Automation Scripts Search for the following scripts: a) TPDEVPING - script to call Tivoli Provisioning Manager by device ping b) TPSWUNINST - script to uninstall a software product

Running the device ping use case:

1. To ensure the server is still running, the change manager creates a new activity task to run device ping from an existing work order.

2. Click the Reference WO link to go to the Activities and Tasks page. 3. On the Activities and Tasks page, select TPTASK as the classification and

TPDEVPING for the assisted workflow. Save the change and click the Assisted Workflow button to initiate the device ping operation.

Running the software product uninstall use case:

1. From an existing work order, the change manager creates a new activity task to run a software product uninstall.

2. Click the Reference WO link to go to this activity task page. 3. On the Activities and Tasks page, select TPSWDEPLOYMENT as the classifica-

tion and TPUNINSTSW as the assisted workflow. 4. At the bottom of the attributes section, specify a software product to uninstall.

Save the changes.

5. Click the Assisted Workflow button to initiate the software uninstall operation.

6. Examples

The example code is available under $TIO_HOME/samples/ismint/

Two zip files, ismint_software_java_action_classes.zip and ismint_jython_actions.zip, contain the following examples: 1. ismint_software_java_action_classes.zip - includes the java implementation of the actions for software deployment, software management and patch deployment

- SoftwareDeploymentAction.java – action class for running software de-ployment

- SoftwareManagementAction.java –action class for running software man-agement such as start and restart software instance

- SoftwarePatchDeploymentAction.java – action class for running patch deployment

- AttachJobPlanToOrder.java – action class for automatically associating a specified job plan to a newly created order and configuring the order to set the specified assisted workflow

- Constants.java – list of the constant variables used by the action classes - Utilities.java – a set of utility methods used by the action classes (for ex-

ample, finding specification attributes from the different level, finding the list of the targets, getting the scheduled time)

2. ismint_jython_actions.zip - includes the Jython implementation of the actions for software uninstall and device ping operations. The example includes the assisted workflows which are used to call the Jython actions and scripts.

- TPDevicePingAutoScript.xml – xml definition for the device ping action including the Jython script for device ping operation

- TPDevPingProcess.xml –xml definition for the device ping assisted work-flow

- TPSWProductUninstallAutoScript – xml definition for the software uninstall action including the Jython script for running software product uninstallation

- TPSWProductUninstallProcess – The xml definition for the software product uninstall assisted workflow