Micro Focus Operations Orchestration Workflows

To automatically launch flows from alerts or situations, ensure that the “Launch Micro Focus OO Flow” workflows are enabled.

To trigger the outbound request from an alert or situation, add a workflow to the “Alert Workflows” or “Situation Workflows” WFE that includes the sendRequestToAutomation function.

For example, the following added to the “Alert Workflows” WFE triggers the a flow to perform a ping test for alerts matching:

Workflow Name: Send Request to MFOO automation

Entry filter: 'manager' = 'MICROFOCUS'

First Match Only: Checked

Where the instanceName argument matches the Instance Name configured in the AlertOps integration tile and the templateName matches a template configured in that instance.

If successful, the the alert updates custom_info.automation.MicfoFocusOO.MicroFocusOO1 to:

{ 
  "status":"pending"
}

If the request is unsuccessful, the “status” and any returned error message will be added to the “summary”:

{ 
  "status":"failed",
  "summary": "Status code: 404, status_msg: Not Found, msg:  ......"
}

A client tool “Launch Micro Focus OO Flow” is available which allows the manual launching of flows from alerts and situations.

To use the tool, ensure that the “Launch Micro Focus OO Flow” workflows are enabled and update the tool prompts to include any instances and flow templates configured in the integration tile.

To update alerts and situations with the results of a flow executed in Micro Focus OO, ensure the “Process Micro Focus OO Response” is enabled and that the flows are updated to include the following callback:

curl -X POST -k -u ${grazeuser}:${grazepw} \
     ${aiopshost}/graze/v1/sendToWorkflow?rejectUnauthorized=false \
     -H "Content-Type: application/json" \
     -d \ 
     '{ "workflow_name":"Process Micro Focus OO Response",
        "engine_name":"Situation Inform Engine",
        "context":{
          "ceventType":"${ceventtype}",
          "ceventId":"${ceventid}",
          "instanceName":"${instance}",
          "status":"${status}",
          "summary":"${formattedResults}",
          "resultsLink":"${resultsLink}"
        }
      }'

The ${ceventtype}, ${ceventid} and ${instance} variables are taken from the triggering request. The ${status}, ${formattedResults} and ${resultsLink} variables update with the flow results.

The returned results are used to update custom_info.automation.MicfoFocusOO.${instance} of the originating alert or situation.

For an alert that belongs to no active situations, custom_info.automation.MicfoFocusOO.${instance} updates with:

{ 
  "status":"${status}",
  "summary": "${formattedResults}",
  "resultsURL": "${resultsLink}"
}

It the alert belongs to active situations, the summary is omitted from custom_info and instead adds a collaboration thread entry to the situations, if that option is enabled in the integration. In this case, custom_info.automation.MicfoFocusOO.${instance}.alert-${ceventid} in the situations also updates with:

{ 
  "status":"${status}"
}

For situations, custom_info.automation.MicfoFocusOO.${instance} will be updates with:

{ 
  "status":"${status}",
  "resultsURL": "${resultsLink}"
}

And a collaboration thread entry is added to the summary , if that option is enabled in the integration.