Documentation update

   

To provide a better user experience, we have now created a separate documentation space for BMC Helix Automation Console (previously called BMC Helix Vulnerability Management).
Users of BMC Helix Automation Console can find the latest documentation at BMC Helix Automation Console. .

Enabling change automation

This topic describes the steps to enable change automation for remediation operations in 
TrueSight Automation Console.To understand the concept of change automation, see Change automation

Creating change requests for an operation

  1. Review the system requirements.

  2. Install the TrueSight Orchestration ITSM Automation runbook. 

    For installation instructions, see Installing the ITSM Automation runbook .

  3. Configure the ITSM Automation runbook as described in Configuring the ITSM Automation runbook. . 

    Depending on the ITSM system that you use (BMC Remedy ITSM or ServiceNow), ensure that the ITSM Automation runbook is configured accordingly. 

  4. Ensure that a connection is established between Automation Console and TrueSight Orchestration.
    For more information, see Configuring the TrueSight Orchestration connector
  5. Ensure that permissions are appropriately configured in TrueSight Server Automation.
    See User roles and permissions

    Do I create a new user account to enable change automation?

    No. The service account created for using Automation Console can be used for change automation too.

  6. (Optional) If you have developed custom workflows as part of the runbook to match your requirements, do these steps: 

    1. Obtain the workflow names created in the ITSM Automation runbook for the following scenarios: 

      ScenarioCurrent out-of-the-box workflow name
      Get ITSM configuration detailsGet ITSM configuration
      Create a change requestCreate Change Ticket
      Get the change request statusGet Change Status

      Update change request

      Update Change Ticket

    2. On the host where the TrueSight Orchestration connector is running, go to the <InstallationDirectory>/truesight/application/common/tso-connector/config/application.properties file. 
    3. In the application.properties file, locate the following and update the current names of the custom workflows for each of the scenario: 

      #Configuration for Tsac
      ao.workflow.itsmConfiguration=:BMC-SA-ITSM_Automation:Change_Management:<CustomWorkflowName>
      ao.workflow.changeTicket=:BMC-SA-ITSM_Automation:Change_Management:<CustomWorkflowName>
      ao.workflow.changeStatus=:BMC-SA-ITSM_Automation:Change_Management:<CustomWorkflowName>
      ao.workflow.updateStatus=:BMC-SA-ITSM_Automation:Change_Management:<CustomWorkflowName>

      Here, <CustomWorkflowName> is the name of the custom workflow created in your TrueSight Orchestration environment. By default, the workflows are created in the Change_Management folder. If you have created workflows in a different folder, replace Change_Management with the accurate folder name.

    4. Restart the TrueSight Orchestration connector. 
      See Configuring the TrueSight Orchestration connector

Where to go from here

When you create an operation, you can now create a change request and configure approvals for a vulnerability remediation operation. See Working with operations

Was this page helpful? Yes No Submitting... Thank you

Comments