UC-4 BATCH process external depnendency between clients (test/qa/prod)

We are using UC-4 tool for scheduling batch jobs in our organization and i am wondering if there is a way to create external dependency of uc4 ojbects between UC-4 Test/qa/prod clients. Say i have object A in Test, B in QA, C in prod, i have to create a process in UC4 prod client to execute object A from Test and after successful run execute object B from qa and then object c from prod.(A-->B-->C sequential)

Thanks in advance

Answers

  • Ian GegliaIan Geglia Team Automic Posts: 91 Specialist ✭✭✭✭
    Generally speaking each client in a Automation Engine is a separate entity. Which is to say you can't really execute a job in another client. We do however provide a callAPI. Using this you could execute a script that runs the callAPI when object A completes. That script would use the callAPI to execute object B. Please see the link to the documentation below:
    https://docs.automic.com/documentation/webhelp/english/AWA/11.2/AE/11.2/All Guides/help.htm#ucaadh.htm?

  • Pete WirfsPete Wirfs Software Engineer Salem OregonPosts: 1,167 Innovator ✭✭✭✭✭✭
    In addition to @Ian Geglia's solution, we have also employed a method that allowed us to join dis-similar schedulers.

    You set up a shared folder that both schedulers can update.  When an event in SystemA needs to trigger an event in SystemB, SystemA saves a "trigger file" in the shared folder.  SystemB waits for the existence of the trigger file (via UC4 EVENT object or a workflow task Precondition).  SystemB then deletes the trigger file and runs the successors.
    Pete
    AE 11.2.1/Windows2012R2/SQLServer12.0
  • Alexander TrenkerAlexander Trenker Team Automic Posts: 314 Expert ✭✭✭✭✭
    In addition to the CallAPI(s) you could also use our internal Webservice combined with the RA WebServices agent.
  • Keld MollnitzKeld Mollnitz Automic Infrastructure Operations Expert DenmarkPosts: 187 Specialist ✭✭✭✭
    I would recommend to use a SYNC object to make dependencies between clients. 
    If you create the SYNC object in client 0 then you can refer to it from other clients. 


  • Wolfgang BruecklerWolfgang Brueckler Developer LV3 EXAutomicPosts: 1,664 Innovator ✭✭✭✭✭✭
    If you have no access to Client 0 there is a disadvantage - you are not able to reset or change the SYNC if necessary by error or if its urgent...

    cheers, Wolfgang
    Wolfgang Brückler
    Developer Lv. 3
    AE 11.2/ORA11G/Linux
  • Ian GegliaIan Geglia Team Automic Posts: 91 Specialist ✭✭✭✭
    In addition to @Ian Geglia's solution, we have also employed a method that allowed us to join dis-similar schedulers.

    You set up a shared folder that both schedulers can update.  When an event in SystemA needs to trigger an event in SystemB, SystemA saves a "trigger file" in the shared folder.  SystemB waits for the existence of the trigger file (via UC4 EVENT object or a workflow task Precondition).  SystemB then deletes the trigger file and runs the successors.
    I like this solution. It doesn't require a sync object or callAPI. Just an event that checks for the file.
  • Stephen AlbertsStephen Alberts Data Automation Engineer FloridaPosts: 12 Explorer ✭✭
    If the systems can't share a folder, the trigger file can also be sent from one system to the other.
Sign In or Register to comment.