HP Matrix Operating Environment 7.2 Update 1 Infrastructure Orchestration User Guide

Service action workflows must receive the following parameters:
• Request XML – The XML that represents the infrastructure; for example:
• User Token – The security token to be used in calls back to infrastructure orchestration.
• Date – Date and time at which the flow was triggered by infrastructure orchestration.
NOTE: These parameters are required in the workflow definition even if the parameters are not
used within the workflow.
Matrix infrastructure orchestration and Operations Orchestration
communication
Matrix infrastructure orchestration uses HTTPS communication with the Operations Orchestration
Server to invoke Operations Orchestration workflows and pass any data needed by the workflow.
The Operations Orchestration Server may be located on the same CMS as infrastructure
orchestration, or may be on a separate server. HP recommends that infrastructure orchestration
and Operations Orchestration be on the same trusted corporate network.
The Operations Orchestration workflow runs with Windows Local System privilege and can be
customized to run arbitrary actions such as file system reads, open network connections or send
email.
For some Operations Orchestration flows, infrastructure orchestration waits for a user response
before moving to the next step of an infrastructure’s lifecycle. Matrix infrastructure orchestration
passes a unique, one time use User Token to these Operations Orchestration flows to
Administrator-defined email recipients. This token is used to authenticate the user response. Matrix
infrastructure orchestrationwaits until the User Token is passed back to the infrastructure orchestration
Service with the correct request ID before moving to the next step of the infrastructure service’s
lifecycle.
By default, these flows send email containing the URL of a response page to the infrastructure
orchestration administrator. This URL contains the User Token and the ID of the request. The
administrator opens the URL in a web browser, and is given a form that allows them to Continue
or Reject the request. Clicking either Continue or Reject opens a HTTPS connection to the
infrastructure orchestration service and passes the user token, request ID and requested action. If
infrastructure orchestration confirms that the user token for the request ID is correct, then infrastructure
orchestration Continues or Cancels the request as appropriate.
If the User Token was intercepted, it is possible for an unauthorized user to approve, reject, continue
or cancel a step of a request on an infrastructure service. However, an administrator will notice
that the infrastructure service continued without his direct action and could then take steps to correct
the problem.
Administrative actions
Administrative Actions are Operations Orchestration Workflow processes invoked during lifecycle
of an infrastructure service.
• Manual OS Deployment—infrastructure orchestration waits for Continued or Canceled response
from user
• Manual Storage Provisioning—infrastructure orchestration waits for Continued or Canceled
response from user
• Manual Storage Removal—infrastructure orchestration waits for Continued or Canceled
response from user
• Manual Disk Scrubbing—infrastructure orchestration waits for Continued or Canceled response
from user
• Request Approval—infrastructure orchestration waits for Approved or Rejected response from
user
• Service Begin Action
• Service End Action
Matrix infrastructure orchestration and Operations Orchestration communication 227