and more in a single search tool across platforms. Read the announcement here. |
03/19/2024 08:42 AM
Hello!
I am trying to run the /v5/runJobTrigger endpoint with the following body:
{
"jobgroup": "DATA",
"triggername": "ActiveDirectory_Accounts_Import_Full",
"jobname": "ApplicationDataImportJob",
"createJobIfNotExists": "false"
}
I found the values for these in the ecmimportjob table in Saviynt:
Full screenshot from Postman:
What could be the issue?
03/19/2024 08:49 AM
Can you try {{path}} - Use api/v5
03/20/2024 12:30 AM
Thanks for your reply, The full url path is set up correctly.
{{base_url}} in my case is a variable, and it contains everything i.e., https://mycompany.saviyntcloud.com/ECM/api
So that is not the issue I think.
03/19/2024 10:07 AM
it should be like below auth and url
03/20/2024 12:29 AM
Yes, I have authorization set up correctly, and the path is also correct.
{{base_url}} in my case is a variable, and it contains everything i.e., https://mycompany.saviyntcloud.com/ECM/api
03/19/2024 07:52 PM
ECM keyword missing in url
{{URL}}/ECM/{{path}}/runJobTrigger
03/20/2024 12:29 AM
{{base_url}} in my case is a variable, and it contains everything i.e., https://mycompany.saviyntcloud.com/ECM/api
So that is not the issue I think.
03/20/2024 03:01 AM
There should be v5 also
Please share curl command [Refer https://codingnconcepts.com/postman/how-to-generate-curl-command-from-postman/ ]
03/20/2024 03:08 AM - edited 03/20/2024 03:19 AM
Yes the v5 is there as shown in the screenshot.
Here's the curl command:
curl --location 'https://****.saviyntcloud.com/ECM/api/v5/runJobTrigger' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer *****; token_type=Bearer; user_name=***' \
--data '{
"jobgroup": "DATA",
"triggername": "ActiveDirectory_Accounts_Import_Full",
"jobname": "ApplicationDataImportJob",
"createJobIfNotExists": "false"
}'
03/20/2024 03:11 AM
{ "jobgroup": "DATA", "triggername": "ActiveDirectory_Accounts_Import_Full", "jobname": "SapImportJob" }
job name is wrong please fix
03/20/2024 03:19 AM
Tried changing jobname to "SapImportJob" and I'm getting the following response:
03/20/2024 10:32 PM
Job Name is not correct/exists in system / Are you connecting to correct instance ?
03/21/2024 01:13 AM
I think so... according to other forum posts it seems like I have the correct values. Even tried creating a Account Import (Single Threaded) as I saw that Multi Threaded was not supported for the API.
Will raise a ticket, thanks for all your help!
03/21/2024 08:31 PM
Check logs
03/20/2024 12:32 AM
I can add that running this POST request to the same endpoint works:
So I think I might have wrong jobgroup or triggername or jobname.
03/20/2024 12:45 AM
think so you added v5 right, and mismatch group.
anyway you got the solution, Great thank you..!
03/20/2024 12:53 AM
My original problem statement still stands, but maybe I should rephrase myself. How do I find the correct attributes:
jobname, jobgroup, triggername
03/20/2024 01:00 AM
above your 1 statement query is right , am using same and used result in payload nd getting status '200'.
try below query check analytic report any diff above field name
select qt.trigger_name,qt.job_name,qt.job_group from qrtz_cron_triggers qcr inner join qrtz_triggers qt on qt.trigger_name=qcr.trigger_name
03/20/2024 01:14 AM
Running your command I get:
Which is the same as running it in the data analyzer on table ecmimportjob:
So I am still stuck with the values:
03/20/2024 02:20 AM
Hi @oscar-am ,
{
"jobgroup": "DATA",
"triggername": "ActiveDirectory_Accounts_Import_Full",
"jobname": "SapImportJob"
}
If this reply answers your question, please consider selecting Accept As Solution and hit kudos.
03/20/2024 03:11 AM
Don't see how that's relevant since we have a different jobname. Maybe I'm failing to understand what's needed.
03/20/2024 03:12 AM
Jobname is internal category of jobs
03/20/2024 02:41 AM
yes as per schema name it should work, my system it working. re-import api dump and check it.
03/20/2024 03:18 AM
What do you mean with "re-import api dump and check it", thanks
03/20/2024 10:30 PM
Saviynt Api re-configured or just dump saviynt api document to your postman set again env nd check it
03/20/2024 10:38 PM