Automic Workload Automation

 View Only

Expand all | Collapse all

What are the impacts if running parallel Agents with same job in different environments

  • 1.  What are the impacts if running parallel Agents with same job in different environments

    Posted Aug 29, 2023 01:54 AM

    Hi Community,

    We have following setup in existing data center and we want to migrate our AE system to another data canter with latest version

    1. AE 12.3 and Agent 12.3 on target machine
    2. Migrated and upgraded to AE 21.0.5 and Agent 21.0.5 on same target machine

    Both AE systems have same jobs, schedules and event so if we want to start the Agents in new automic system will there be any impact on job level and events if yes what is mitigation strategy to overcome the problem and also please suggest how can we stop all scheduled jobs before starting agents in new Automic system? 



    ------------------------------
    Regards,

    Eshwar
    ------------------------------


  • 2.  RE: What are the impacts if running parallel Agents with same job in different environments

    Posted Sep 01, 2023 08:56 AM

    Hi Eshwar,

    because i've not the same setting, i only can reflect from our knowledge and the knowledge from automic system itself.

    1. Are there impacts to be expected on the job level?
      Yes and No, it depends on the job. 

      Yes if both jobs access to same data at same time. It could be possible that you overwrite data, or write it double to a file, or you transfer files twice, i don't know anything about the task you're doing, so the answer only vague.

      No
      from automation engine itself there is no problem. Both AE trigger on same event and run the task you expect. The JCL send to every agent ideally in separete folder's, depends on your agent configuration. The jcl Filename is generated dynamically, so at this point there is no impact.
       
    2. Migration Strategy:
      To solve the problem you can stop the Workflow on AE Env 1 (12.3) and start it on AE Env 2 (21.0.5). If you have no direct access, or you need to switch on specific date and time, you can use calendar conditions. So Job run up to an specific date and time on Env1 and after calender condition (date/time)  Env 2 execute it. 
      This is theoretical idea i've not tested it. 
      Another idea is to split the workflow execution process in 2 process paths and execute the different pathes on different date/time conditions.

    Hope that helps.

    Best regards

    Andrzej Golaszewski