BMC Remedy IT Service Management Suite

BMC Release Process Management 5.0 enables you to integrate with BMC Remedy IT Service Management Suite (BMC Remedy ITSM Suite). You can use the BMC Release Process Management interface to perform various functions in the BMC Remedy ITSM Suite interface while carrying out your deployment process interface to perform various functions in the BMC Remedy ITSM Suite interface while carrying out your deployment process.

Integration workflow

This integration enables the following workflows:

  • Workflow 1: (Recommended) Use BMC Remedy ITSM Suite for release planning and use BMC Release Process Management for executing the release plan. 
  • Workflow 2: Use BMC Release Process Management for release planning and BMC Remedy ITSM Suite for change tracking.

The following figure illustrates workflow 1. The numbers represent steps in the workflow.

Integration workflow 1

workflow1.png


  1. The Release Manager or the application team creates a release request in BMC Remedy ITSM Suite.
  2. The authorized user approves the release request in BMC Remedy ITSM Suite at the approval phase and moves the release to the Planning stage.
  3. BMC Remedy ITSM Suite automatically creates a release in BMC Release Process Management on the Plans tab. BMC Remedy ITSM Suite also associates the relevant change requests for that release as external tickets (in BMC Release Process Management) under the plan created.
  4. The application team uses BMC Release Process Management to manage deployments and tactical release processes by creating requests with associated steps necessary to carry out deployment tasks. While creating steps, you can use the automation scripts provided with the product to perform functions in BMC Remedy ITSM Suite.
  5. The release request is advanced through the phase gates according to the iterative release process in BMC Remedy ITSM Suite. At the same time, deployments are completed in BMC Release Process Management.
  6. The authorized user approves the deployment to move to the Production environment in BMC Remedy ITSM Suite.
  7. BMC Release Process Management executes the final deployment to the Production environment (using automation scripts).
  8. BMC Release Process Management logs the results of the final deployment into BMC Remedy ITSM Suite (using automation scripts).
  9. End of process.

Sample use cases for workflows

The following use cases describe the preceding workflows.

Use case for workflow 1

You can use BMC Remedy ITSM Suite for release planning and use BMC Release Process Management for executing the release plan.

  1. User logs into BMC Remedy ITSM Suite and creates a release RLM000000000001 named "Feb 2013 Maintenance upgrade" to carry out the maintenance upgrade scheduled for February 2013.
  2. User creates the following change requests under the release RLM000000000001 in BMC Remedy ITSM Suite:
    • CRQ000000000001: Update database schema of Oracle application 5.2

    • CRQ000000000002: Update .war file of xyz.com
      When he creates this release and moves it to the Planning stage, the same release is added as a plan in BMC Release Process Management along with the associated change requests (that are added as tickets).

      Note

      The change requests are added into BMC Release Process Management only when the following conditions are fulfilled:

      1. The Relationship Type of the change request with the release is set to Member of on the BMC Release Management Console.
      2. The Request Type of the change request is set to Infrastructure Change on the BMC Release Management Console.
  3. User logs into BMC Release Process Management and creates a Request 1001 named "Update database schema of Oracle application 5.2" under the plan, "RLM000000000001:Feb 2013 Maintenance upgrade."
  4. User adds the following steps under Request 1001:
    • Step 1: Update actual start of the change request CRQ000000000001 by using the Remedy update change request automation script.
    • Step 2: Perform the actual deployment task.
    • Step 3: Mark the deployment tasks as "closed" in BMC Remedy ITSM Suite by using the Remedy update change request tasks automation script.
    • Step 4: Update the Completed Date and Status as shown in BMC Remedy ITSM Suite into BMC Release Process Management by using the Remedy update change request automation script.
  5. User creates another Request 1002 named "Update .war file of xyz.com."
  6. User adds the following steps under Request 1002.
    • Step 1: Update actual start of the change request CRQ000000000002 by using the Remedy update change request automation script.
    • Step 2: Perform the actual deployment task.
    • Step 3: Mark the deployment tasks as "closed" in BMC Remedy ITSM Suite by using the Remedy update change request tasks automation script.
    • Step 4: Update the Completed Date and Status as shown in BMC Remedy ITSM Suite into BMC Release Process Management by using the Remedy update change request automation script.
      This step completes the release planning and execution for the February 2013 maintenance upgrade.
Use case for workflow 2

You can use BMC Release Process Management for release planning and BMC Remedy ITSM Suite for change tracking.

  1. User logs into BMC Remedy ITSM Suite and creates the following change requests:
    • CRQ000000000001: Update database schema of Oracle application 5.2
    • CRQ000000000002: Update .war file of xyz.com
  2. User logs into BMC Release Process Management and creates a plan named "Feb 2013 Maintenance upgrade" to carry out the maintenance upgrade scheduled for February 2013.
  3. User creates a plan under the Plans tab, and then he navigates to the Tickets tab and uses the External Ticket Filters link to associate the BMC Remedy ITSM Suite change requests (CRQ000000000001 and CRQ000000000002) as tickets in BMC Release Process Management.
  4. User creates a Request 1001 named "Update database schema of Oracle application 5.2" under the plan created.
  5. User adds the following steps under Request 1001:
    • Step 1: Update actual start of the change request CRQ000000000001 by using the Remedy update change request automation script.
    • Step 2: Perform the actual deployment task.
    • Step 3: Mark the deployment tasks as "closed" in BMC Remedy ITSM Suite by using the Remedy update change request tasks automation script.
    • Step 4: Update the Completed Date and Status as shown in BMC Remedy ITSM Suite into BMC Release Process Management by using the Remedy update change request automation script.
  6. User creates a Request 1002 named "Update .war file of xyz.com."
  7. User adds the following steps under Request 1002.
    • Step 1: Update actual start of the change request CRQ000000000002 by using the Remedy update change request automation script.
    • Step 2: Perform the actual deployment task.
    • Step 3: Mark the deployment tasks as "closed" in BMC Remedy ITSM Suite by using the Remedy update change request tasks automation script.
    • Step 4: Update the Completed Date and Status as shown in BMC Remedy ITSM Suite into BMC Release Process Management by using the Remedy update change request automation script.
      This step completes the release planning and change tracking for the February 2013 maintenance upgrade.


Related topics

Automation-scripts-for-BMC-Remedy-IT-Service-Management-Suite

Configuring-for-integrating-with-BMC-Remedy-IT-Service-Management-Suite

Entity-mapping-for-BMC-Remedy-IT-Service-Management-Suite

Known-and-corrected-issues

Managing-automation

Mapping-properties

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*