Hello, Workday has an API endpoint used in Boomi processes for fetching application data via API. Need an HTTP check on this endpoint url WHO: API endpoint: https://services1.myworkday.com/ Application : Workday v25.1 HOW: Perform and HTTP check and get status from the check if the endpoint responds OK, Boomi process is kicked off else re-try. Would be nice to have a script called from Boomi processes itself (python/shell) and spit the output as Yes/No so the process can take the decision to start. Please let me know for any other information needed
Do we have access to the boomi box to be able to run the shell from there ?
:shradda we need more information and a lot more detail to implement anything here. Where/what are these Boomi processes? What host do they run on? HTTP check of... what? The URL you gave there is currently responding with "not available".
HI Peter, Boomi processes are run on the Boomi atom hosted on amazon cloud - ip-10-81-7-103.us-west-2.compute.internal (22.214.171.124).I have given MOC login access to this host. Let me know if i need to provide access to the UI for this host so that you can see the process The process connects to Workday instance (https://services1.myworkday.com/) to fetch a report. This instance sometimes returns 500 internal error which fails the process. I would like to have a check(script) inside the process to verify instance availability before the process kicks off. I am not sure if an HTTP or PING can verify the instance availability but seeking the help. Happy to answer more questions. Thanks !
Tossing back into the queue since I'll be on PTO all next week - Will retake if no-one has wrangled it.
Status: ASSIGNED → NEW
Back to data team component until bug 1334236 has resolution.
Component: MOC: Service Requests → Other
Product: Infrastructure & Operations → Data & BI Services Team
QA Contact: lypulong → mpressman
Version: unspecified → other
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.