Orchestrating change through Workflow Jobs
The integration of Workflow Jobs in BMC BladeLogic Server Automation with BMC Atrium Orchestrator gives administrators many capabilities for connecting data center tasks. All of these possible tasks depend on a basic use case — creating and running a Workflow Job. That basic capability gives administrators the possibility to perform many other types of tasks, described in #Additional use cases.
Basic use case
Task | Product involved | Description and references |
---|---|---|
Create and execute BMC Atrium Orchestrator workflows using a BMC BladeLogic Server Automation Workflow Job. | BMC BladeLogic Server Automation | Set up a Workflow Job. The job can incorporate Atrium Orchestrator workflows, which in turn can run other types of BMC BladeLogic Server Automation jobs. |
Additional use cases
Task | Products involved | Description and references |
---|---|---|
Pause a job until pre-conditions are met (for example, approval is obtained). | BMC BladeLogic Server Automation | When defining a Workflow Job, specify that it requires Remedy approval. Jobs set up in this way communicate with BMC Atrium Orchestrator to reference an existing Remedy ticket or to generate a new ticket. The job can obtain approval automatically so the Workflow Job can proceed without any human intervention. Or, the job can require manual approval. In that case, the job pauses until an administrator reviews and approves the job. Once approved, BMC Atrium Orchestrator restarts the paused job. |
Monitor workflow status. | BMC BladeLogic Server Automation | Monitor Workflow Jobs like any other BMC BladeLogic Server Automation job by watching jobs in progress, viewing job results, and reading job logs. The Workflow Job log can include messages generated by BMC Atrium Orchestrator. |
Run conditional logic (for example, if workflow 1 fails, then abort and do not do step 2). | BMC Atrium Orchestrator | Use the functionality of BMC Atrium Orchestrator to set up a workflow that includes conditional logic. Once a workflow is designed in this way a Workflow Job can execute different child jobs depending on the results of previous jobs. |
Get user input within a job run | BMC BladeLogic Server Automation | Specify data that Atrium Orchestrator may require by entering parameters for the Workflow Job. By defining information in this way, it can be provided automatically to the Workflow Job. |
See the Workflow Job results and status, and from them see the results of any child jobs. | BMC BladeLogic Server Automation | In BMC BladeLogic Server Automation, use the Jobs folder to see the results of all runs of a Workflow Job. If you set up the executeWorkflowChildJob and executeWorkflowChildJobId BLCLI commands, you can also see the results of any child jobs that the Workflow Job initiated. |