Skip to main content
Question

Create a WMS Service using FME Server 2019.0.1

  • October 8, 2019
  • 1 reply
  • 60 views

Hi all,

I am trying to create a WMS service with the use of FME Server 2019.0.1. I have followed two tutorials:

- https://knowledge.safe.com/articles/19640/how-to-create-a-wms-service-using-fme-server.html

- https://knowledge.safe.com/articles/1342/inspire-wms-demo.html

After following the tutorials, I am able to open the WMS service in the data inspector and in QGIS. In QGIS, I have to do an FME Server authentication. Otherwise I am not able to see the data provided by the WMS service. In ArcGIS Portal and ArcGIS Pro, I also try to add the WMS service. However, an error occurs. These software packages are not able to open my WMS service created with FME Server.

I think the errors occur, because of the token in the URL in the WMS service, for example: https://fmeserver.xxx.com/fmedatastreaming/Playground/GetCapabilities.fmw?&token=91dfc73aed4c80932296ba2116d4aabdcfd4b3ce. In the tutorial there is no information on these tokens and how to you use them in the xml of the webservice.

Is there anyone who has experience in creating a WMS service with FME Server 2019 and is able to communicate with the WMS in ArcGIS Portal of ArcGIS Pro?

Kind regards,

Niels

1 reply

todd_davis
Influencer
Forum|alt.badge.img+22
  • Influencer
  • October 9, 2019

"token" is not a valid part of a WMS querystring so lots of things will not except it. If you create a WMS behind an Esri security that uses a token, most system won't be able to read that either, so this isn't an FME thing.

Here is some more info from the Esri point of view:

https://enterprise.arcgis.com/en/server/latest/publish-services/windows/wms-services.htm

ArcGIS Online and Portal, do not have the ability to deal with the "token" in the querystring.

https://doc.arcgis.com/en/arcgis-online/reference/ogc.htm

So get rid of your token and use http basic! Going directly to your workbench at https://fmeserver.xxx.com/fmedatastreaming/Playground/GetCapabilities.fmw will pop a window for authentication which is http basic.

So when you add your link to a wms client, you just need to put the relevant username/password into the authentication into your client to access.

Cheers,

Todd


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