This section contains information about enhancements in version 2.0 of BMC Change Automation.
The following enhancements are available in this release of BMC Change Automation.
The BMC Change Automation installer simplifies the process of integration with base components and enables the solution features.
BMC Change Automation installer performs the following:
If BMC Atrium Orchestrator version 7.9 is not installed on the computer, running the BMC Change Automation installer installs BMC Atrium Orchestrator 7.9 on that computer.
A connection with following components is enabled by configuring the connection details:
The installer configures Derby database to store data coming from the automation system and the change management system. The following database tables are created:
The following modules are activated:
The installer configures following adapters:
Uploads the latest ROAR file to the repository that has patches for BMC Change Automaton.
The following web services are added in BMC Remedy Change Management to support integration with an external automation system.
|Web service name||Purpose|
To create or update a Request For Change for an automation job.
To pull data from the change management system.
To support the history of certain transactions such as worklog updates.
To create a task template for an automation job.
The following job enhancements support the Operator-Initiated Change and Change-Initiated Job use cases in BMC Change Automation 2.0.
|A checkbox for Execute on Approval on Schedules panel.||Ensures that the job is run after approval from change management.|
|A checkbox for Create incident on job failure on Default Notifications panel.||Ensures creation of an incident upon failure of a job.|
|A checkbox for Change Task Template Enabled on General panel.||Enables creation of a task template in change management having all job details. This task template is utilized by the change manager during creation of a change.|
In this release of BMC Change Automation, templates are dynamically applied to a change record. This ensures that change records are quickly created and relevant attributes are applied to enrich the change record.
To ensure that correct templates are searched, optionally, you can define template selection rules using the new Template Selection Configuration interface. Using this UI, you can create, edit, delete, and search template selection rules. A template selection rule consists of criteria to search and apply a relevant template when a change record is created.
Navigate to Administrator Console > Application Administration Console > Custom Configuration > Foundation > Advanced Options > Template Selection Configuration to access this interface. For more information, see Managing change template selection rules.
The following screenshot shows the new UI.
Starting with this release, a new process flow is provided out of the box that is applied to a Request for Change from an automation system. This process flow is called Standard Process-Automation System.
In this process flow, the state of the change record by default transitions directly from Draft to Planning in Progress stage. To avoid the possibility of applying existing auto-approval processes to these new types of automated change records, this stage transition ensures that the auto approval process is bypassed even if the auto approvals are configured in the system.
The following screenshot depicts the state transition of the Standard Process-Automation System process flow.
This capability ensures that the change manager has the opportunity to:
For more information, see Overview of Standard Process-Automation System process flow.
A set of new change rules are provided that are applicable to requests from automation systems.
The following tables lists the rules and their default values:
|Rule Name||Default Value|
Create Service Request on Submit
|Default Automation Change Process Flow|
Standard Process-Automation System
|Default Change Duration|
|Outbound Communication Approval Status|
Scheduled For Approval
For more information, see Configuring change rules for requests from automation system.
A single-click, end-to-end integration validation utility is provided to help you verify whether the integration between the automation system, BMC Atrium Orchestrator and BMC Remedy Change Management is working fine. The one-click utility runs automatically after you set the connection details in the BSA console. The utility displays the results of the test and integration errors, if any. After you fix the errors, you can manually run the utility again to validate whether the integrations are working correctly.
For more information, see Validating integrations.
To facilitate guaranteed delivery of data and ensure reliability, this release of BMC Change Automation supports a store-and-forward mechanism in BMC Atrium Orchestrator. When BMC Atrium Orchestrator receives data from an automation system or retrieves information from the BMC Remedy Change Management system, the data is stored in the event when either of the endpoint is unavailable. In this event, periodically, BMC Atrium Orchestrator retries sending this data to the other end point. The default duration to resend the stored data is three days, which can be configured as per your requirement. For more information, see Configuring data persistence interval.
The major benefit of this feature is that BMC Atrium Orchestrator reliably tries resending data to the end point and communicates failure or success of the process.
In this release of BMC Change Automation 2.0, workflows and adapters are provided in BMC Atrium Orchestrator for successful implementation of Operator-Initiated Change and Change-Initiated job. These workflows and adapters ensure efficient transmission of data between automation system and change management.
For more information, see BMC Atrium Orchestrator workflows and adapters.
To extend your system and to maintain the flow of information from the automation system and change management, three new wrapper workflows are introduced in BMC Atrium Orchestrator. These wrapper workflows operate as customization windows and represent empty implementation of the workflow. These customization windows provide an opportunity to search and add functionality without changing the default behavior.
Ensure that you perform modifications only in the given customization windows. This best practice ensures that your modifications do not alter the default settings of the workflow.
For more information about the customization windows, see