1. Cloud Control Host Lifecycle Management Guide
  2. Monitoring and Managing Hosts
  3. Additional Setup for Real-time Monitoring
  4. Setting Up Change Request Management Integration
  5. BMC Remedy Action Request System 7.1 Integration
  6. Installing and Customizing Remedy ARS
  7. Adding the Connector to Cloud Control
  8. Creating Change Requests for Upcoming Changes

Creating Change Requests for Upcoming Changes

Now that integration is set up and Real-time monitoring rules have been created, Change Requests can be created by Remedy users in the Remedy interface. These Change Requests will be compared to observations that occur to automatically determine if these observations are from actions that were authorized by change requests or not.

To make this correlation, some new fields that have been added to the Change Request form must be filled out by the change request filer. Not all fields are required; correlation only occurs on the fields that are present in the Change Request.

For instance, the following fields have been added to the Change Request form under the Oracle Enterprise Manager Integration tab:

  • Connector: Choose the Cloud Control connector this Change Request will use to integrate with Cloud Control.

  • Hostname: the hostname(s) this change request is for. These are the hosts that this change request is specifying someone needs to make changes to. An empty value in this field indicates that all hosts will be correlated to this change request.

  • Target User List: the user name(s) this change request is for based on target users. These are the target users you expect to log in to the target to make a change. An empty value in this field means that all users on the target will be correlated to this change request.

  • Target Type: the target type this change request is against. An empty value in this field means that any target type will be correlated to this change request.

  • Target: The target this change request is specifically for. An empty value in this field indicates that any target will be correlated to this change request.

  • Facet: The facet this change request is specifically for. An empty value in this field indicates that all facets on the above target type and target will be correlated for this change request.

When creating a change request that you want to use to authorize changes detected by Real-time monitoring rules, follow these steps in addition to whatever requirements your organization implements for creation of Change Requests:

  1. Under the Dates tab of the Change Request form, fill out the Scheduled Start date and Scheduled End Date. These are the date ranges the request is valid for reconciliation. If an action occurs outside this time, it is marked as unauthorized by the Real-time Monitoring feature.
  2. Select the Oracle Enterprise Manager Integration tab.
  3. Select the Cloud Control connector from the drop-down list.
  4. Optionally select values for the five reconciliation criteria as described above: Hostname, Target User List, Target type, Target and Facet. The last three -- Target Type, Target, and Facet -- will be Choice lists based on content in Real-time Monitoring Rules that have been created in Cloud Control that belong to Compliance Standards which are associated to targets. You can add multiple values separated by commas.

    Note:

    This form can be customized in Remedy to look differently. The example form elements from the customizations loaded earlier are only examples.

  5. Change the auditable status to True. This configures Remedy to allow Cloud Control to use this change request for reconciliation of Real-time Observations that are detected.
  6. Save the change request.
  7. A popup displays, notifying you that active links will send the content to Cloud Control. You will see a DOS command window open and then close.