Endevor

 View Only
  • 1.  Endevor and Remedy Integration (or any other Change Management tool)

    Posted Aug 12, 2022 04:06 PM
    We are trying to find a better way to integrate our Endevor to Remedy.  Is there anyone that uses Remedy that could share how their integration is setup?  We are trying to accomplish the following:
    a. Check for promotion package = Y
    b. Package Window start date >=  CR start date
    c. Package ID must be 12 characters
    d. Element CCID must match package ID
    e. Prevent 'BYPASS ELEMENT DELETE', 'SYNC', 'OVERRIDE SIGNOUT'

    Our current setup is stage D, T, Q, P (Fix X, O).  Package required from D>T, T>Q, Q>P (monitoring occurs from T to P)

    We receive a file from Remedy with all CR (change request) and it's status (start/end dates, etc...). Their is so much jcl written to just match the CR with the PACKAGE info and APPROVE/RESET/RECAST, it's just making the process much more complicated to add additional checks.
    Just wanted to see how other shops are working.



  • 2.  RE: Endevor and Remedy Integration (or any other Change Management tool)

    Broadcom Employee
    Posted Aug 15, 2022 02:22 PM
    Hi Sherma. I've never used Remedy so won't be much help there but... I can't help thinking maybe integration with Remedy isn't necessary. That is, Endevor's exit7 could perform all the checks you have listed. Then, if exit7 fails a package for one of these checks, exit7 can also send a notification email to whoever needs to make the corrections.


  • 3.  RE: Endevor and Remedy Integration (or any other Change Management tool)

    Posted Aug 15, 2022 04:24 PM
    Can you send me an example of how these conditions will be checked in EXIT7.

    Thanks

    Sherma J. Burch

    Sr Infrastructure Engineer
    (864)498-9934 c
    Sherma.Burch@lowes.com

    ________________________________
    NOTICE: All information in and attached to the e-mails below may be proprietary, confidential, privileged and otherwise protected from improper or erroneous disclosure. If you are not the sender's intended recipient, you are not authorized to intercept, read, print, retain, copy, forward, or disseminate this message. If you have erroneously received this communication, please notify the sender immediately by phone (704-758-1000) or by e-mail and destroy all copies of this message electronic, paper, or otherwise. By transmitting documents via this email: Users, Customers, Suppliers and Vendors collectively acknowledge and agree the transmittal of information via email is voluntary, is offered as a convenience, and is not a secured method of communication; Not to transmit any payment information E.G. credit card, debit card, checking account, wire transfer information, passwords, or sensitive and personal information E.G. Driver's license, DOB, social security, or any other information the user wishes to remain confidential; To transmit only non-confidential information such as plans, pictures and drawings and to assume all risk and liability for and indemnify Lowe's from any claims, losses or damages that may arise from the transmittal of documents or including non-confidential information in the body of an email transmittal. Thank you.




  • 4.  RE: Endevor and Remedy Integration (or any other Change Management tool)

    Broadcom Employee
    Posted Aug 16, 2022 04:59 AM
    Hi Shrema,

    As Dave has told you, most of the verifications can be done through Exit 7. Those that need direct and synchronous connectivity with Remedy (Package Window start date >= CR start date) could be done through a direct call to the Remedy API (if any) from Exit 7.

    BR,

    JB

    ------------------------------
    José B. González L.
    Client Services Consultant SPAIN
    Mainframe Software Division - Broadcom
    ------------------------------



  • 5.  RE: Endevor and Remedy Integration (or any other Change Management tool)

    Broadcom Employee
    Posted Aug 26, 2022 05:02 PM
    I used to be a Remedy consultant.  Not sure if I am understanding your problem completely, but I'll make a stab.

    1.  If you are getting a file from the Remedy CR and you are trying to match that to Endevor, it might be easier to write a zowe command to do it.
    2.  If you are trying to cause actions from Remedy, you could use the Endevor Web Services API or a Zowe script to cause the actions.
    3.  If you are looking to update Remedy, we could use a Webhook and trigger an action to notify Remedy.

    We can do a lot of this on the mainframe using exits and calling some scripts from USS, for example.

    If I get a CSV file, I can process it using Javascript or Python and trigger events or validate information in Endevor.

    If you would like to discuss this, please let me know.  I have some time next week.

    Thomas
    thomas.mcquitty@broadcom.com