Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Extending the integration with BMC Change Management

Optionally, you can extend the integration with BMC Change Management by making additional actions available to the service offering, or by customizing the change templates.

This topic contains the following sections:

Enabling additional actions

To configure the integration for an action with BMC Change Management, map the values in the CMF:ChangeIntegrationEnablement form as follows.

  1. Log on to enterprise BMC Remedy AR System server (AR System server).
  2. Open the SYS:Menu Items form and locate the Menu Type field.
  3. Select Change Policy from the Menu Typelist. The following Change Policies are returned:
    • Change Approval Required
    • Audit Only Change
    • Pre-Authorized Change
    • No Change Required
  4. Select the change policy to which you want to add the custom actions from the search list (for example, Change Approval Required).
  5. Copy the contents of the Menu Value 1 field on the SYS:Menu Items form.
  6. Open the CMF:ChangeIntegrationEnablement form.
  7. To verify that the change for operations has not been implemented, paste the value of Menu Value 1 in the field Change Template ID.
  8. If the search does not return a change template, click New Request.
  9. Set up the desired operator action by completing the fields on the form.

    Use the table in Mapping reference to determine the values to enter in the fields.
  10. Click Save in the upper right corner of the form.

Mapping reference, by change policy

Set up as many of the operator actions as required for each change policy, using the values in the table below to populate the fields on the CMF:ChangeIntegrationEnablement form.

Change policy

Value for ClassName

Available values for Operation

Value for ChangeTemplateID

Change Approval Required

ComputeContainer

  • start
  • stop
  • shutdown

Use the value copied from the Menu Value1 field on the SYS: Menu Items form for the Change Approval Required change policy.

Change Approval Required

ServiceOfferingInstance

  • startCompute
  • stopCompute
  • decommission
  • extend
  • shutdownCompute

Use the value copied from the Menu Value1 field on the SYS: Menu Items form for the Change Approval Required change policy.

Audit Only Change

ComputeContainer

  • start
  • stop
  • shutdown

Use the value copied from the Menu Value1 field on the SYS: Menu Items form for the Audit Only Change change policy.

Audit Only Change

ServiceOfferingInstance

  • startCompute
  • stopCompute
  • decommission
  • extend
  • shutdownCompute

Use the value copied from the Menu Value1 field on the SYS: Menu Items form for the Audit Only Change change policy.

Pre-Authorized Change

ComputeContainer

  • start
  • stop
  • shutdown

Use the value copied from the Menu Value1 field on the SYS: Menu Items form for the Pre-Authorized Change change policy.

Pre-Authorized Change

ServiceOfferingInstance

  • startCompute
  • stopCompute
  • decommission
  • extend
  • shutdownCompute

Use the value copied from the Menu Value1 field on the SYS: Menu Items form for the Pre-Authorized Change change policy.

Notes

  • Only the Submit Request action is configured out-of-the-box.
  • You can add more change templates to the change policy menu by using the SYS:MenuItems form, as described in the following section.
  • For Auto-Decommissioning, if you configure the SOI Decommission to have change integration, Auto Decommissioning is also route through change management.

Guidelines for customizing BMC Cloud Lifecycle Management templates

You can add a new change template, map it to corresponding policies, and make the association with a specific service offering definition.

When creating the new change template, add the Change Template Instance ID to the SYS:Menu Items form, with Change Policy specified as the Menu Type.

The newly created change policy is added as an entry to the Change Policy drop-down list of the requestable offering definitions.

On the existing Change Template forms, you can modify attributes such as Summary, Risk Level, and Urgency.

On Task Templates, you can add customized tasks in addition to the Standard Cloud Task.

Note

Do not remove the Standard Cloud Task.

Related topics

The following link provides supplemental information available from a blog entry in BMC Cloud Lifecycle Management Communities:

Configuring BMC Cloud Lifecycle Management to use multitenant Change Management

Was this page helpful? Yes No Submitting... Thank you

Comments