+6When we create a Web or FME Server connection in a workbench it automatically gets prefixed with my
name.
And then when published to Flow we get the same….
is it possible to create these connections with a more generic name, I’m not connecting as “robert.mcpherson” and it doesn’t seem to matter but this is an enterprise system and I will be for ever named in the system. I guess it doesn’t matter but it doesn’t seem a very “enterprise” thing
+6I think I’ve found the way round this, careful overwriting of the default names at each point (web service, web connection etc) gets rid of the prefix - one missed step and it’s there! Just something to live with I guess
+17I think I’ve found the way round this, careful overwriting of the default names at each point (web service, web connection etc) gets rid of the prefix - one missed step and it’s there! Just something to live with I guess
Interested to know if you (or anyone else) have established a standard naming convention for Web Connections and Services.
I am testing out some ideas for standard naming, such as the following:
FME Web Service/Connection Naming Scheme
1. Platform Name (Compulsory):
FME Flow / ArcGIS Online / Azure Active Directory/...
- This should conform to the name in the FME Web Services or Web Connections Dialog Box
2. URL (Optional)
fme.xxxx.com/xxxx.maps.arcgis.com
- if this is specified in the connection and/or the connection should only be used for this specific site
User Name (Compulsory):
Admin/Publisher/SSO...
- Only include a user name if it is baked in to the connection, or there is a reason why only that user should be used for this connection
- Use SSO to represent a connection that could be many users
Authentication Type (Compulsory):
Basic/OAuth/Token/Open/Client ID...
- Open means no Auth required
- OAuth would likely be paired with SSO in the User Name
Service or Connection (Compulsory):
Svc / WebCon / DBCon
Example:
FME Flow-fme.xxxx.com-admin-Basic-WebCon
