Skip to main content
Released

Simpler access to FME Server REST API via Workbench

Related products:Transformers
  • October 30, 2018
  • 1 reply
  • 6 views
danilo_fme
jmjanzen
mark2atsafe
  • danilo_fme
    danilo_fme
  • jmjanzen
    jmjanzen
  • mark2atsafe
    mark2atsafe

nic_ran
Contributor

Currently, the only way to access the majority of the FME Server REST API functionality via Workbench is to use the HTTPCaller.

The problem with this approach is that you need to hard-code the server URL into the HTTPCaller (or use a published parameter) but this is not dynamic between environments. If I want to publish a workspace from DEV to PROD, I need to go in and update the server URL.

It would be nice if a named FME Server Web Connection (which already includes the FME Server URL) could be used for both authentication and base URL configuration.

A simple wrapper around the existing HTTPCaller would probably be all that is required, so that the base request URL is automatically supplied from the web connection.

If the above is too difficult, please create a transformer to allow for the web connection URL to be queried in the workspace, so that this can be passed in to the HTTPCaller.

The ultimate solution would be to have a full FMEServer_API_Caller transformer that would allow REST API queries to be dynamically built within the transformer... but that's probably asking too much. :)

This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, 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.

1 reply

revesz
Contributor
Forum|alt.badge.img+15
  • Contributor
  • November 1, 2018

Another useful solution would be something like custom server parameters. Eg. it would work as private parameter in FME Desktop but it would get the value from the custom server parameter in FME Server it exists.

It would be useful with other server dependent parameters, too.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings