Integrating with BMC Helix Change Management
The integration of BMC Change Management with TrueSight Infrastructure Management enables you to create an automated blackout policy and schedule downtime for a Configuration Item (CI) in TrueSight Infrastructure Management. When TrueSight Infrastructure Management receives a change or a task request for scheduled maintenance, the associated CI goes into the blackout state. This prevents the generation of false alerts, alarms, and data for the CI.
Integration with BMC Helix CMDB is required for integration with BMC Helix Change Management.
Integrating BMC Change Management with TrueSight Infrastructure Management has the following benefits:
- Enables TrueSight Infrastructure Management to receive notifications of change requests configured on specific CIs from BMC Change Management.
- Enables the TrueSight console to display the attributes of the change requests that are configured in BMC Change Management.
- Creates an automated blackout policy in the TrueSight console for the CI that you configure for maintenance in BMC Change Management. The Blackout policy ensures that no false alarms are generated for the CI that is scheduled for maintenance.
For detailed information about installing, configuring, and using this solution, see the BMC Helix Change Management documentation . The following diagram depicts the architecture of this integration:
Internal processes involved in the TrueSight Operations Management environment
The following components are involved:
- Rest Webservice EventProvider—Receives event notifications from the ITSM change management in the JSON format over the rest webservice. The component converts this event notification into an NGP event and sends it to jserver, which is the event processor component, through the jserver facade.
- Event Processor—Receives the NGP event from the webservices Eventprovider component. The component does any pre-processing required on the event then sends the event to the cell.
- Event Selector—Receives the event from the gatewayEvent handler. If the event is a change event or some other event of concern, the Event Selector sends the event to the RuleConfigurator asynchronously.
- Rule Configurator—Has two major components: RuleConfiguratorConsumer, and RuleConfiguratorWorker.
The RuleConfiguratorConsumer is controlled by the RuleConfiguratorConsumerManager, which gets started when the JSERVER is initialized. The RuleConfiguratorManager starts the different RuleConfiguratorConsumer threads, which feeds the data to RuleConfigurator. The RuleConfigurator includes the PolicyConfigurator and ScheduleConfigurator. The PolicyConfigurator uses BlackOutPolicyCrud to create a blackout policy. The ScheduleConfigurator uses ScheduleConfiguratorCrud APIs to schedule down time.
Configuring the integration
Complete the following tasks to integrate with BMC Helix Change Management:
For troubleshooting information, see Troubleshooting the BMC Helix Change Management integration.
Comments
Log in or register to comment.