×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')
BMC Atrium Orchestrator Content 20.16.02 ... Run books BMC Continuous Compliance for Servers for ServiceNow Configuration roadmap for Continuous Compliance for Servers for ServiceNow

Updating module configuration for Continuous Compliance for Server Automation for ServiceNow

Prior to using the solution, you must make the following 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:

  1. Using BMC Atrium Orchestrator Development Studio Project Navigator, open the module and double-click configuration.
  2. Expand configuration to review the configuration settings for the environment.
  3. Make the required updates described in the following sections.

Updating Operations Actions management module configurations

  1. Make the changes described in the following table to the Operations Actions management module configurations.
    For more information, see Operations Actions Management modules. 
  2. To configure the run book modules, double-click a configuration item, make the required changes shown in the following table, and click Save.

Module name

Description and required changes

AutoPilot OA Change Management

Enables you to control the lifecycle of all changes with minimum disruption to IT services.

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

AutoPilot OA Configuration Management

Enables you to manage configuration items.

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

AutoPilot OA Incident Management

Enables you to manage incident requests.

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

AutoPilot OA Task Management

Enables you to perform tasks in response to service tickets.

For more information, see Task Management module in the BMC Atrium Orchestrator online documentation.

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

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.

Updating run book module configurations

Run book module

Required changes

Closed_Loop_
Compliance-SA-
Servers

Runbook Default configuration items: Closed_Loop_Compliance-SA-Servers

  • FileAdapter: Specify the name of the file adapter.
  • SMTPAdapter: Specify the name of the SMTP adapter.
  • Change_Management: For the Enable element,
    specify true if you want to create a change in ServiceNow.
    Default value is false.
  • Incident_Management: For the Enable element, 
    specify true if you want to create an incident in ServiceNow.
    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 is Bladelogic adapter.
  • BL_Connection_Details_Instance_2: Specify the adapter name for the second instance.
  • BL_Version: Specify the version of the BMC Server Automation Console.
    Default version is 8.1

  • BladeLogic_Trap_Mappings: 

    <bladelogic-trap-mappings>
  <enterprise>.1.3.6.1.4.1.12788</enterprise>
  <generic-trap-type>6</generic-trap-type>
  <specific-trap-type>1001</specific-trap-type>
  <jc-job-name>.1.3.6.1.4.1.12788.1.1.1</jc-job-name>
  <jc-start-time>.1.3.6.1.4.1.12788.1.1.2</jc-start-time>
  <jc-end-time>.1.3.6.1.4.1.12788.1.1.3</jc-end-time>
  <jc-overall-status>.1.3.6.1.4.1.12788.1.1.4</jc-overall-status>
  <jc-exit-code>.1.3.6.1.4.1.12788.1.1.5</jc-exit-code>
  <jc-group-id>.1.3.6.1.4.1.12788.1.1.6</jc-group-id>
  <jc-run-id>.1.3.6.1.4.1.12788.1.1.7</jc-run-id>
  <jc-type-id>.1.3.6.1.4.1.12788.1.1.8</jc-type-id>
  <ar-cons-type>.1.3.6.1.4.1.12788.1.2.1</ar-cons-type>
  <ar-obj-type>.1.3.6.1.4.1.12788.1.2.2</ar-obj-type>
  <ar-os-type>.1.3.6.1.4.1.12788.1.2.3</ar-os-type>
  <cr-cons-type>.1.3.6.1.4.1.12788.1.5.1</cr-cons-type>
  <cr-template-name>.1.3.6.1.4.1.12788.1.5.2</cr-template-name>
  <cr-rule-name>.1.3.6.1.4.1.12788.1.5.3</cr-rule-name>
  <at-user-name>.1.3.6.1.4.1.12788.1.3.1</at-user-name>
  <at-host-name>.1.3.6.1.4.1.12788.1.3.2</at-host-name>
  <at-command-string>.1.3.6.1.4.1.12788.1.3.3</at-command-string>
  <at-time-occurred>.1.3.6.1.4.1.12788.1.3.4</at-time-occurred>
  <rat-date>.1.3.6.1.4.1.12788.1.4.1</rat-date>
  <rat-role-name>.1.3.6.1.4.1.12788.1.4.2</rat-role-name>
  <rat-user-name>.1.3.6.1.4.1.12788.1.4.3</rat-user-name>
  <rat-object-type>.1.3.6.1.4.1.12788.1.4.4</rat-object-type>
  <rat-object-name>.1.3.6.1.4.1.12788.1.4.5</rat-object-name>
  <rat-authorization-action>.1.3.6.1.4.1.12788.1.4.6</rat-authorization-action>
  <rat-action-status>.1.3.6.1.4.1.12788.1.4.7</rat-action-status>
  <rat-message>.1.3.6.1.4.1.12788.1.4.8</rat-message>
</bladelogic-trap-mappings>


  • Create_Remediation_Schedule_With_BSA_Approval: Specify true if you want to use ORCA Web Service to
    call the BMC Atrium Orchestrator workflows, from the BladeLogic-SA-ITSM_Integration module.
    If you specify true, you must activate the BladeLogic-SA-ITSM_Integration module also on the grid.
    By default, the value is false. If false, the Closed_Loop_Compliance_ITSM_Integration
    module is used for calling the workflows.
  • 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: If specified as true, the remediation jobs are scheduled automatically with pre-approved change.
    If false, remediation jobs are not scheduled automatically and the change remains in the draft state.
    A change coordinator needs to approve the change manually to schedule the job
    as per the next maintenance window.  
    Specify the value if you are using ITSM integration.
  • 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.
  • 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    .

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

Closed_Loop_
Compliance_
ITSM_Integration

Runbook Default 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, ServiceNowActor.
  • Authentication_Query_Mappings:
  • Default_Company: Enter the company name as seen in ServiceNow instance for the given user name.
    For example, Calbro Financial Services.
  • Default_Company_Location: Enter the company location as seen in ServiceNow instance for the given user name.
    For example, Calbro Financial Services.  
  • Default_First_Name: Enter the first name as seen in ServiceNow instance for the given user name.
    For example, BladeLogic.
  • Default_Last_Name: Enter the last name as seen in ServiceNow instance for the given user name.
    For example, orchestrationuser.
  • Username: This value must match the name of the ServiceNow logon ID created for BMC Continuous
    Compliance for Server Automation solution.
    Change the default value to orchestrationuser so that it matches the ServiceNow 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 Default 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: The Username value must match the name of the logon ID created for
    BMC Continuous Compliance for Server Automation solution in ServiceNow.
    (for example, orchestrationuser or ccsuser).
  • RCP Console configuration group: The BL_Version value must specify the version
    and location of the BMC Server Automation Console that launches
    from the Task ticket in ServiceNow for the operator-initiated change use case.
    For a complete list of options see BladeLogic ITSM Integration module.

Synchronizing the environment for Continuous Compliance for Server Automation

You must synchronize the computers housing the BMC Atrium Orchestrator CDP, ServiceNow, 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 ServiceNow instance.


Was this page helpful? Yes No Submitting... Thank you
Last modified by Shweta Hardikar on May 05, 2016
configuring continuous_compliance_servers

Comments

Log in or register to comment.

Configuring adapters for the Continuous Compliance for Server Automation for ServiceNow solution
Executing Continuous Compliance for Servers for ServiceNow use cases
© Copyright 2024 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.