BDA - How does the workflow in the BDA integration with Remedy function?

Version 2
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    BMC BladeLogic Database Automation


    APPLIES TO:

    BMC BladeLogic Database Automation



    QUESTION:

    How does the workflow in the BDA integration with Remedy function?

    LP: BMC BladeLogic Database Automation 8.6.00
    DR: BMC BladeLogic Database Automation 8.6.00


    ANSWER:

     

    Legacy ID:KA423424

      

    The workflow is like this:

    1. User creates a job in BDA, specifies a Change and Task number. From the user's perspective, they're waiting for BDA to check with Remedy.

    2. BDA sends a message to Remedy/ITSM (ITSM) via Atrium Orchestrator (AO), telling ITSM that there's a job awaiting approval. BDA then puts the job into "AO Request" state and goes off to do other things. BDA does not wait for a response.

    3. ITSM examines the specified Change/Task, and, in response to the message it got from BDA, sends a message back through AO to inform BDA of the current status of the Change/Task. This status can be "Approved", "Rejected", or "Approval Pending". ITSM then goes off to do other things. It does not wait for BDA to respond.

    4. BDA receives the message sent via AO from ITSM. It calls up the job and updates it according to the message received from ITSM: if the status of the Change/Task was "Approved", it sets the job's status to "Running" and the job starts running. If the status of the Change/Task was "Rejected", the job's status is set to "Approval Rejected" and the job is marked as "Done", which means the job will never run. If the status of the Change/Task was "Approval Pending", the job's status is set to "Approval Pending" and then BDA goes off to do other things.

    5. Several seconds/minutes/hours/days/weeks/years go by.

    6. An ITSM user then approves the Change/Task associated with the job to run. This triggers ITSM to send a message to BDA via AO, informing it that the status of the Change/Task has changed. ITSM then goes off to do other things.

    7. BDA receives the message sent via AO from ITSM. It calls up the job and updates it according to the message received from ITSM: if the status of the Change/Task was "Approved", it sets the job's status to "Running" and the job starts running. If the status of the Change/Task was "Rejected", the job's status is set to "Approval Rejected" and the job is marked as "Done", which means the job will never run. 

      
    Related Products:  
       
    1. BMC BladeLogic Database Automation

     


    Article Number:

    000027593


    Article Type:

    FAQ/Procedural



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles