Integrate > HPE Operations Orchestration (OO) > Example: launching automated implementation for change and request tasks

Example: launching automated implementation for change tasks

This example describes how to launch automated change task implementation when Service Manager is integrated with Operations Orchestration (OO). In this example, automated implementation is launched for tasks related to the Restart Tomcat Service item.

Note The Restart Tomcat Service item used in this example is only provided in Service Manager 9.51 and later versions. An OO flow is configured for this item in the out-of-box Service Manager..

Precondition

Before you start, make sure that necessary content packs are deployed in your Operations Orchestration client. If not, follow these steps to deploy the content packs.

  1. Log on to Operations Orchestration as an Administrator.
  2. Click Content Management on the left-hand panel.
  3. Click the Content Pack tab.
  4. Click the Add icon to add the contents.

  5. Go to <OO Installation folder>/content, select the following content files of which the extensions end with .jar:

    • oo10-base-cp-1.8.0.jar
    • oo10-sm-cp-1.0.3.jar
    • oo-microsoft-office-365-cp-1.0.1.jar
    • oo-saw-cp-2.0.0.jar
    • oo-servicenow-cp-1.0.0.jar
    • oo10-request-fulfillment-cp-2.0.3.jar
  6. Click OK.
  7. Click Save.

Add an Operations Orchestration instance in Service Manager

To add an Operations Orchestration instance in Service Manager, see Add an Operations Orchestration integration.

Enable OO flow automation for change tasks

To enable OO flow automation for change tasks, see Enable OO flow automation for change tasks.

Start the AutomationTaskUpdate backend schedule

  1. From the System Navigator, click Miscellaneous > System Status > Start Scheduler.
  2. Select AutomationTaskUpdate to start the schedule.

When this schedule is started, the status of the change task can be automatically updated after the OO flow execution.

Launch automated task implementation

ClosedLaunch automated implementation for change tasks related to the Restart Tomcat Service item

To launch automated implementation for change tasks related to Restart Tomcat Service, follow these steps:

  1. Open the change task for which you want to launch automated implementation.

    If there are no change tasks related to Restart Tomcat Service, order the Restart Tomcat Service item from Service Catalog to create a change record first, then generate a change task from the change record:

    1. From the Service Manager System Navigator, click Service Catalog > Order from Catalog.

    2. The Service Catalog Entries page opens.

    3. Search for and then open the Restart Tomcat Service item.

    4. Specify the fields on the form.

    5. Click Add to Cart.
    6. Click View Cart/Checkout, and then open the Restart Tomcat Service item.
    7. Specify the fields and then click Submit. Remember the ID of the request for later use, for example, SD10219.
    8. Log on to Service Manager as SDApprover using another session. From the System Navigator, click Service Catalog > Search Request to search for the request created, for example, SD10219.
    9. The request should be in the Pending Approval status. Approve the request.
    10. Switch back to the session where you submitted the order and wait for a few seconds. Then, there should be a change record in the Related Records tab. Click the related record ID, for example, C10061.
    11. In the change record form, move the change to Execution Phase. Then, click the Task tab. A task should be found there.
  2. Click the task ID to open the task details page. The phase should be in Execution.
  3. Wait for a few minutes for the OO task to complete. The task should go to the Completion phase if service is restarted successfully or the Review phase if not.

Send Help Center feedback