Thanks Scott for the details. Appreciate it.
Couple of questions
1) You said below.
You can set this up on a post condition of your job submission task. It depends on the exact use case and where you want reports etc.
Here you mean capture the parameter with the script and end the job based on the specific value?
2) You said below:
Most rest based api submissions operate on this very premise. Trigger them, get an id, come check the id periodically until satisfied. Even automic itself does the same when you activate it by rest, it gives the runid immediately and you are left to poll that id for end status.
If i give connection time out as 0 then it will check the response until it matches otherwise it will keep waiting. What is the default polling interval? I did not find much documentation about this topic anywhere. Can we change the polling interval? If so how?
Thanks,
Prakash S
Original Message:
Sent: 02-20-2020 01:31 PM
From: Scott Hughes
Subject: Trigger job in AWS cloud by using REST API Oauth option
Hi Prakash,
Some web services I have worked with give the user a token which have a varying lifespan. The work being done by the cloud service should give a session or job id. Determine the best guess of the runtime of that job and start checking at that time, then every minute thereafter until done.
You can set up a subworkflow that accepts the necessary parameters and does the above until the job ends.
You can set this up on a post condition of your job submission task. It depends on the exact use case and where you want reports etc.
Most rest based api submissions operate on this very premise. Trigger them, get an id, come check the id periodically until satisfied. Even automic itself does the same when you activate it by rest, it gives the runid immediately and you are left to poll that id for end status.
If your webservice gives you an expiring token you may have to renew that in some manner, that is a different topic.
--
Scott Hughes
IT Network Services
O 949 286 7668
M 505 373 7872
7000 Central Blvd SW
Albuqurque
Albuqurque, New Mexico 87121
Original Message------
Hi Team,
We are planning to use REST API Oauth option to trigger job in AWS cloud. After starting the job in cloud server by using oauth option, how can we get the response back into automic without read or connection timeout? Because app team don't want to wait for the response until job completes. Instead check the response after periodic interval. How can make this happen in Automic Web Interface?
Note: Currently Automic resides in on-premises.
Thanks,
Prakash S