Skip to main content
Question

Httpcaller vs job submitter

  • January 24, 2018
  • 2 replies
  • 28 views

arthy
Contributor
Forum|alt.badge.img+8

Hi all,

I would like to know the pro and cons of using a jobsubmitter instead of a httpcaller in terms of efficiency, parrallelism, ... and vice-versa.

Thanks

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
  • January 24, 2018

If you mean in the context of possibly using the HTTPCaller to submit a job using the REST API, it's exactly the same. As far as I know the FMEServerJobSubmitter uses the exact same API.


Forum|alt.badge.img+2

If you mean in the context of possibly using the HTTPCaller to submit a job using the REST API, it's exactly the same. As far as I know the FMEServerJobSubmitter uses the exact same API.

I believe so. If you want to call the data streaming or download services you can use the HTTPCaller and DirectURL.

 

 

Some info on the FMEServerJobSubmitter behaviour is available here: https://knowledge.safe.com/articles/55369/fme-server-troublshooting-fmeserverjobsubmitter.html

 

Calling jobs (job submitter) through REST API is available here: https://docs.safe.com/fme/html/FME_REST/apidoc/v3/index.html#!/transformations