Hi,
Please can you add the 'OutputLocation' parameter to the 'Job' 'Response Class' returned by the REST service?
This would allow you to calculate the download link from Asynchronous Data Download requests.
Many thanks,
Paul Wittle
Archived
Provide OutputLocation in Job response class via REST
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+22- Safer
With FME Server 2016.0 there is a new 'resultDatasetDownloadUrl' parameter returned when you use the following call in version 3 of the REST API:
GET /transformations/jobs/id/< jobid >/resultThis parameter is only applicable when a job is run using the Data Download service
Screenshot:
https://www.dropbox.com/s/79rh411kn10bp27/Screensh...
Doc:
https://bluesky-safe-software.fmecloud.com/fmerest...
Does this address your requirement @paul_wittle?
Hi,
Sorry @aaronkoning for the slow reply; apparently I was not following my own idea...
I currently changed tack; I now get FME Server to issue a HTTP POST notification on completion to a web application which listens for the messages and use that to get the URL.
I believe the parameter you describe is what I am looking for though as the current method fails if the POST fails for any reason.
It is better that the application can make the request to the API as this allows it to try again if the first request is unsuccessful.
We have not yet upgraded to the 2016 Server but I will certainly try it out when we do.
Thanks