Skip to main content
Solved

result url and async rest call of download service

  • May 28, 2013
  • 2 replies
  • 21 views

Wher can I find the result url if I run a download service by rest call in async mode?

 

 

The async call url is build like this:

 

http://<serverName >:<serverPort>/fmedatadownload/<repositoryName>/<workspaceName>?opt_servicemode=async&opt_responseformat=xml&token=<token>

 

 

The result query is build like this:

 

http://serverName>:<serverPort>/fmerest/jobs/<jobId>/result.xml?token=<token>

 

 

The xml response of result query does not contain the result url. If I run download service in sync mode, I can find the result url in xml response of sync call.

 

 

What I have to do to get the result url when I call a download service in async mode?

 

Best answer by david_r

Hi,

 

 

according to the examples here, it seems like the async call only supports sending the download url by mail, and not including it in the result xml like for synchronous calls.

 

 

You might consider contacting Safe support about this if it isn't what you'd expect.

 

 

David
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.

2 replies

david_r
Celebrity
  • Best Answer
  • May 28, 2013
Hi,

 

 

according to the examples here, it seems like the async call only supports sending the download url by mail, and not including it in the result xml like for synchronous calls.

 

 

You might consider contacting Safe support about this if it isn't what you'd expect.

 

 

David

Forum|alt.badge.img
  • November 2, 2017

The above URL not work(404). I found I can make an asyn call with empty parameters {} successful; but once I pass any parameters, it result 404 bad request: because json is not correct(space error) or if json is correct, then it returns

"Expected a list of published parameter objects". Still struggling very hard.