Updating module configuration for Continuous Compliance for Server Automation
Prior to using the solution, you must make certain module configuration changes that are specific to the BMC Continuous Compliance for Server Automation solution environment.
Accessing module configuration
To view and update the module configuration:
- Using BMC Atrium Orchestrator Development Studio Project Navigator, open the module and double-click configuration.
- Expand configuration to review the configuration settings for the environment.
- Make the required updates described in the following sections.
Updating Operations Actions management module configurations
- Make the changes described in the following table to the Operations Actions management module configurations. For more information, see the BMC Atrium Orchestrator Operations Actions (OA) Management Modules and Utilities online documentation.
- To configure the run book modules, double-click a configuration item, make the required changes shown in the following table, and click Save.
Description and required changes
AutoPilot OA Change Management
Enables you to control the lifecycle of all changes with minimum disruption to IT services. Specific processes exist for interfacing with BMC Remedy ITSM change management.
AutoPilot OA Configuration Management
Enables you to manage configuration items. Specific processes exist for interfacing with BMC Remedy ITSM change management and BMC Atrium CMDB.
AutoPilot OA Incident Management
Enables you to manage incident requests. Specific processes exist for interfacing with service request management systems and BMC Remedy ITSM.
AutoPilot OA Task Management
Enables you to perform tasks in response to service tickets. Specific processes exist for interfacing with service request management systems and BMC Remedy ITSM. For more information, see Task Management module in the BMC Atrium Orchestrator online documentation.
AutoPilot Common Utilities
Predeveloped processes representing core processes used across all OA modules. No changes are required.
Predeveloped processes containing common application-related commands used in Red Hat Enterprise Linux, Sun Solaris, and Microsoft Windows environments. No changes are required.
Updating run book module configurations
Run book module
Closed Loop Server Audit module
Runbook Default configuration items: Closed_Loop_Server-SA-Audit
Runbook Default configuration items: Closed_Loop_Compliance-SA-Servers
For a list of all options for the module configuration, see Closed Loop Compliance SA Server module.
Default_User configuration items: Closed_Loop_Compliance_ITSM_Integration
Note: If you do not want to create a change and incident ticket, you can disable the Closed_Loop_Compliance_ITSM_Integration workflow.
For a list of all options for the module configuration, see Closed Loop Compliance ITSM Integration module.
BladeLogic ITSM Integration module
Runbook Default configuration items: BladeLogic-SA-ITSM_Integration
Server Incident Enrichment module
Configuration items: Server_Incident-SA-Enrichment
BDSSA: Modify these items if you must customize any of the settings listed in Server Incident Enrichment module for BMC BladeLogic Decision Support for Server Automation. For example, if BMC BladeLogic Decision Support for Server Automation is installed with a non-default port number, update the Server_Name item as <ServerName:portNumber>.
Synchronizing the environment for Continuous Compliance for Server Automation
You must synchronize the computers housing the BMC Atrium Orchestrator CDP, BMC Remedy ITSM, and BMC Atrium Orchestrator Development Studio. Without time synchronization, workflows might not complete as expected.
For example, in environments that are not synchronized, a workflow might create a configuration item. However, you might not be able to retrieve it due to the time in the environment being out of sync.
To avoid problems, ensure that the time in your environment is within 1 minute of the BMC Remedy ITSM instance.