Solved

Setup API using FME Cloud and AWS API

  • 15 January 2018
  • 1 reply
  • 2 views

Badge +10

Hi,

I have tried to use the blog post

https://knowledge.safe.com/articles/24147/tutorial-creating-web-services-using-fme-server.html

but come across some differences in the instructions to what I see in FME Cloud and AWS.

Namely:

Give the role the following permissions:

  • Applications > FME Server Web User Interface

This doesnt show as an option in FME cloud.

and:

We need to get the URL to run the workspace via the Data Streaming service:

  1. Go to Run.
  2. Select the parksapi repository, and then select the workspace you published. The only option should be for Data Streaming.
  3. Click the wrench icon to get the developer information.
  4. Save the URL given. For example, https://my-fme-server-example.fmecloud.com/fmedatastreaming/parksapi/getParksGeoJSON.fmw.

I don't know which URL to use, the one I do use I tried to put into the AWS API Gateway and it wouldn't accept my http address - it said that it wasn't valid.

 

If there are more recent guides that anyone could point me to that would be super.

Many Thanks

Oliver

icon

Best answer by gerhardatsafe 15 January 2018, 20:21

View original

1 reply

Badge

Hi @olivermorris,

Thanks for reaching out!

I reviewed the article you were following and there have indeed been a few minor changes to FME Server which need to be addressed in this article:

FME Server Security:

For FME Server 2017 the security model changed significantly. Permissions for single services and for the FME User Web Interface are not part of the selectable permissions anymore. For the purpose of the instruction, you are following your new user 'parksapi' will need the following permissions

  • Repositories > parksapi > Read, Run
  • Run Workspace > Access

Direct URL:

The URL to be used can be found Advanced > Direct URL on the Run Workspace page. AWS API Gateway expects an endpoint URL without any query parameters. By default, the direct URL displayed for an FME Server workspace includes the query parameters for all published parameters. If you just use the base and the path of the direct URL before the query parameters without '?' (e.g https://<you-server>.fmecloud.com/fmedatastreaming/parksapi/getParksGeoJSON.fmw) the URL should be accepted.

I will update the article accordingly.

Kind regards,

Gerhard

Reply