+1I have created a number of workspaces that end up in a FME Server project that will finally run on a different machine.
My question is: How can I specify FME Server connections for example for FMEJobSubmitter or FMEServerLogRetriever that can run in the new server environment without knowledge of accounts and passwords on the target machine?
For database connections this is easily possible, but I have found no way to do this with the connections in the aforementioned transformers.
+19Hi @dollargis, what version of FME are you using? With FME Workbench 2017+, Web Connections (including FME Server Connections) used in a workspace can be uploaded to a FME Server simultaneously when you publish the workspace.
+1@takashi: We are on FME Desktop/Server 2018.
The problem arises with our security restrictions: As the workspaces' author, I have no knowledge about the target machine's accounts and passwords, and in the status quo my credentials of the developer environment won't work.
What would help here is an abstraction level like we have with database connections which can be predefined on the server and, given the same name, be used without knowledge of the underlying credentials.
As I see the situation there is now alternative but let the FMEServer administrator click through all workspaces that use FMEJobSubmitters or FMEServerLogRetrievers and set the correct web connections (minor problem is that they have no FME knowledge).
+1@takashi : Coming back to my original question:
I just talked to our security, and they insist on having a separate account on the server machine whose password is not known to the author of the workspaces. Therefore I cannot use these user credentials in FME desktop and upload them together with the workspaces.
What solution could be envisaged here?
+19@takashi : Coming back to my original question:
I just talked to our security, and they insist on having a separate account on the server machine whose password is not known to the author of the workspaces. Therefore I cannot use these user credentials in FME desktop and upload them together with the workspaces.
What solution could be envisaged here?
+2Hi @dollargis,
I think the approach is the same for database connections:
1/ You (or the person who knows the username/password) creates the connection on each of the FME Servers (web interface). They should all have the same name.
2/ You create a connection with the same name on your own machine (via FME Workbench). This connection can point to an FME Server that you have access to.
3/ When you publish your workspace to an FME Server, do not publish the web connection (it is already there). Your published workspace will now use the connection on the server with the same name.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
