Viewing tasks at runtime for integration with BMC BladeLogic Client Automation
This example explains how you can launch tasks at runtime from a parent object, which is the BMC Helix ITSM: Change Management application. This section focuses exclusively on tasks used in the BMC BladeLogic Client Automation integration.
Before you begin
To make the following procedure work as expected, you must properly configure the integration between Change Management and BMC BladeLogic Client Automation. For more information, see Integrating-with-BMC-BladeLogic-Client-Automation.
To view and launch tasks at runtime
- Open the parent application object, for example, Change Management, and then create a record.
Although you can add tasks or task groups to a change during any state, for example, Initiate, they can only be worked on during the Implement state. - Use the process flow accelerators to step through the states of your change request until you reach the Implement state.
- From the Request Type list on the Tasks tab, select Task Group Template, and then click Relate.
On the Select Template dialog box, select a task group, for example, Create and Modify Policy with Closed Loop Verification, and then click Relate.
(Optional) Click View Flow to see a read-only view of the tasks in the task group.
The Task Flow Viewer uses color codes to illustrate the different stages of the tasks. For example, a blue stage indicates that its status is Closed, but a yellow stage shows its status is Staged. The Viewer also shows you the flow between tasks. You can perform the following functions in the Task Flow Viewer:
- Zoom in to focus the view.
- Zoom out to expand the view.
- Use the scroll bar to move the flow around.
- Use the Show All option to view the complete task flow within the viewer.
- In the Children of Selected Task Group table, select the task to work on and then click View.
- On the task form, click the Relationships tab.
- Select the Software Library Item from the search list and search for the storage locations.
This displays the Software Library Item Search dialog box. The storage location contains the location of the software being deployed. The storage location can be either a physical repository (for example, Fred's top drawer) or an electronic repository (a folder on your network). In the search results, select the appropriate storage location, and then click Relate.
The Relationship Attributes dialog box appears.
On the Relationship Attributes dialog box, you can only set the following values with storage locations and CIs; otherwise, the relationships created do not work as expected.Relationship item
Relationship attribute
Action attribute
Configuration Item
TARGET
Not applicable
LDAP
TARGET
Not applicable
Software Library Item
SOURCE
INSTALL
Software Library Item
SOURCE
UNINSTALL
- Define the relationship attribute, for example, SOURCE.
- Define the action attribute, for example, INSTALL.
- Click Apply.
The storage location is added to the change request. - Perform a search for a Configuration item.
- In the search results on the CI Relationships Search dialog box, select the appropriate CI, and then click Relate.
The Relationship Attributes dialog box appears. - On the Relationship Attributes dialog box, define the relationship attribute, for example, TARGET.
Define the action attribute, for example, INSTALL, and then click Apply.
The CI is added to the Relationships table in the Task form.- On the Task form, click the General tab.
Click Launch to display the BMC BladeLogic Client Automation Policy Manager.
- After you have performed the policy changes, click Save.
- Close the Policy Manager window to return to the Task form.
- (Optional) Review the work information about the task.
The work information about the task is updated with the changes performed by the task.- Click the Work Info tab.
- In the Work Info History area, select the Policy Manager entry, and then click View.
- Close the Work Info dialog box dialog box when you are finished viewing the information.
- Click Report to view an ASCII-format report of the task changes.
The report lists the software installed, whether the policy was successful, and so on.
- In the Status field, set the task status to Closed.
The status reason is set to Success automatically. You can select a different status reason, for example, Failed or Canceled. - After you make all your modifications and enter all required information, save and close the task.
- On the Change form, refresh the children of the task group table.
The status of the first task is marked as Closed and the status of the second task is now Waiting. - Open the second task:
- Select the Check Compliance task and then click View.
- On the Task form, click Details to view the target and package compliance.
- Verify the compliance in Policy Manager.
- Close the Viewer window when you are finished to return to the Task form.
- In the Status field, set the task status to Closed.
You can view the work information for the task as needed. The task record is updated with the changes performed by the task. - After you make all your modifications, save and close the task.
- On the Change form, refresh the children of the task group and the task and task groups tables.
All tasks and the task group are marked as Closed. - Click Save.