Updating module configuration for Continuous Compliance for Server Automation

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.

BMC_AR_System:Adapter — Change this value to the name of the AR System actor adapter on your CDP.

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.

BMC_AR_System:Adapter — Change this value to the name of the AR System actor adapter on your CDP.

AutoPilot OA Incident Management

Enables you to manage incident requests. Specific processes exist for interfacing with service request management systems and BMC Remedy ITSM.

BMC_AR_System:Adapter — Change this value to the name of the AR System actor adapter on your CDP.

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.

• BMC_AR_System:Adapter — Change this value to the name of the AR System Actor Adapter on your CDP.
• BMC_AR_System:Soap_User_Name — Change this parameter, if required, to the name of the BMC Remedy user that can associate Tasks with CIs.
• BMC_AR_System:Soap_Password — Change this parameter, if required, to the password assigned to Soap_User_Name.

AutoPilot Common Utilities

Predeveloped processes representing core processes used across all OA modules. No changes are required.

AutoPilot ADUtilities

Predeveloped processes containing common application-related commands used in Red Hat Enterprise Linux, Sun Solaris, and Microsoft Windows environments. No changes are required.

Closed Loop Server Audit
module

Runbook_Defaults configuration items: Closed_Loop_Server-SA-Audit

• Export_Path: Change this value to a string value that holds the directory name that must exist on the BMC Server Automation adapter peer where the comma seperated values (CSV) file of Audit Job results is to be stored. This path does not contain the file name. For example, *C:\temp*.
• File_Connection_Details: Ensure that the host name element matches the host name of the peer running the BMC Server Automation adapter.
• Package_Group_Name: Enter a string value that holds the BMC Server Automation Depot folder structure which contains the BLPackages used to remediate Audit discrepancies. For example, /Closed Loop Remediation/Audit.
• Remediation_Job_Group: Enter a string value that holds the BMC Server Automation Job folder structure which contains the newly created remediation job to remediate Audit discrepancies. For example, /Remediation/Audit.
• Destination_Verify_Job_Group: Enter a string value that holds the BMC Server Automation Job folder structure which contains the copy of the verification job that ensures that the Audit discrepancies have been remediated. For example, /Remediation/Verify/Audit.
• SNMP_Target: Enter the IP address of the computer of the BMC Atrium Orchestrator peer running an SNMP Monitor adapter on the grid. Jobs executed on BMC Server Automation that require SNMP Trap notification back to BMC Atrium Orchestrator use this value for the Job Run Notification SNMP properties. 

• Jobs: Enter the details for each job that you want to execute. Specify elements such as job-group,group, job-name, and name for each of the jobs that you want to execute.
  

  Example

  <jobs>
    <job>
      <job-group>/Closed Loop Folder/CLSA</job-group>
      <job-name>audit job</job-name>
      <templates>
        <template>
          <group>/CLSA</group>
          <name>CLSA Template</name>
        </template>
      </templates>
    </job>
  </jobs>

Default_User configuration items

• Adapter: Change this entry to the name of the BMC Remedy Actor adapter configured on the grid. For example, ARSAdapter.
• Username: This value must match the name of the BMC Remedy ITSM logon ID created for BMC Continuous Compliance for Server Automation solution (for example, orchestrationuser or ccsuser). Change the default value so that it matches the BMC Remedy ITSM logon ID.
• Default_First_Name: Enter the first name as seen in BMC Remedy ITSM instance for the given user name. For example, BladeLogic.
• Default_Last_Name: Enter the last name as seen in BMC Remedy ITSM instance for the given user name. For example, OrchestrationUser.
• Default_Company: Enter the company name as seen in BMC Remedy ITSM instance for the given user name. For example, Calbro Financial Services.

• Default_Company_Location: Enter the company location as seen in BMC Remedy ITSM instance for the given user name. For example, Calbro Financial Services. 

  
  For a complete list of options see Closed Loop Server Audit module.

Runbook Default configuration items: Closed_Loop_Compliance-SA-Servers

• Change_Management: For the Enable element, specify true if you want to create a change in ITSM. Default value is false.
• Incident_Management:For the Enable element, specify true if you want to create an incident in ITSM. Default value is false.
• Configuration_Management: For the Enable element, specify true if you want to integrate with Configuration Management. Default value is false.
• BL_Connection_Details: Specify the adapter name for the run book. Default value: Bladelogic adapter.
• BL_Connection_Details_Instance_2: If you want to use one more BladeLogic adapter, specify the name of the second instance of the adapter.
• BL_Version: Specify the version of the BMC Server Automation Console. Default version is 8.1
• BladeLogic_Trap_Mappings: Specify the XML structure that holds the BMC Server Automation trap mappings
• Default_TimeZone: Specify the time zone. Default value is GMT-6:00 
• Destination_Verify_Job: Enter a string value that holds the BMC Server Automation folder structure which contains the copy of the verification job that ensures that the Compliance violations have been remediated. For example, /Closed Loop Folder/CLSC/Verify Job Folder.
• Export_Path: Change this value to a string value for the directory on the BMC Server Automation adapter peer where the CSV file of Compliance Job results is to be stored. This path does not contain the file name. For example, C:\temp.
• File_Connection_Details: Ensure that the host name element matches the host name of the peer running the BMC Server Automation adapter.
• Jobs: Specify an XML structure that contains a list of Compliance Jobs that BMC Atrium Orchestrator manages. Multiple job elements are allowed, and a job might contain multiple template elements.
• Log_File_Path: Specify the location where the log files are located. For example: C:\clc.log
• Logging_Enabled: If true, the File adapter must be enabled on the grid and
• Remediation_Depot_Name: Enter a string value for the BMC Server Automation Depot folder structure which contains the BLPackages used to remediate Compliance violations. For example, /CLSC/Remediation Package Folder.
• Remediation_Job_Delimiter: Default delimiter is -AO-.
• Remediation_Job_Group:  Enter a string value for the BMC Server Automation Job folder structure which contains the newly created remediation job to remediate Compliance violations. For example, /Closed Loop Folder/CLSC/Remediation Job Folder.
• SNMP_Target: Enter the IP address of the BMC Atrium Orchestrator peer running an SNMP Monitor adapter on the grid. Jobs executed on BMC Server Automation that require SNMP Trap notification back to BMC Atrium Orchestrator use this value for the Job Run Notification SNMP properties.
• Send_Approval_Email: Specify true if you want to send approval emails automatically. You must have configured the SMNP target and the email 
• To_Email_Address_List: Specify the email addresses of the users to whom you want to send the approval emails automatically. The IMAP adapter must be enabled with the email addresses. The subject of the email is retrieved from the clc.log file, which is created at the path specified for the Log file path under the LOG_File_Path property.
• blcli_tunneling: Specify true if you want to enable the BMC Server Automation adapter with the BLCLI tunneling mode on. Default value is false.

For a list of all options for the module configuration, see Closed Loop Compliance SA Server module.

Closed_Loop_Compliance
_ITSM_Integration

Default_User configuration items: Closed_Loop_Compliance_ITSM_Integration

• Adapter:  Change this entry to the name of the BMC Remedy Actor adapter configured on the grid. For example, ARSAdapter.
• Default_Company: Enter the company name as seen in BMC Remedy ITSM instance for the given user name. For example, Calbro Financial Services.
• Default_Company_Location:  Enter the company location as seen in BMC Remedy ITSM instance for the given user name. For example, Calbro Financial Services.  
• Default_First_Name:  Enter the first name as seen in BMC Remedy ITSM instance for the given user name. For example, BladeLogic.
• Default_Last_Name: Enter the last name as seen in BMC Remedy ITSM instance for the given user name. For example, OrchestrationUser.
• Username: This value must match the name of the BMC Remedy ITSM logon ID created for BMC Continuous Compliance for Server Automation solution. Change the default value to orchestrationuser so that it matches the BMC Remedy ITSM logon ID.

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 _Defaults configuration items: BladeLogic-SA-ITSM_Integration

• Email_Notification: Modify these items if you are implementing eMail notification in BMC Server Automation.

Default User configuration items: BladeLogic-SA-ITSM_Integration

• Username: The Username value must match the name of the logon ID created for BMC Continuous Compliance for Server Automation solution in BMC Remedy ITSM (for example, orchestrationuser or ccsuser).

RCP Console > BL_Version configuration items: BladeLogic-SA-ITSM_Integration:

• version: Specify the version and location of the BMC Server Automation Console that launches from the Task ticket in BMC Remedy ITSM for the operator-initiated change use case. For a complete list of options see BladeLogic ITSM Integration module.

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>. 

BladeLogic: If you are using BMC BladeLogic Decision Support for Server Automation version 8.5, you must change this value of Version in the BladeLogic configuration group to v8.5. to generate new URLs.