Skip to main content
Question

Securing ArcSDE connection files on FME Server

  • March 6, 2020
  • 1 reply
  • 99 views

tim_wood
Contributor
Forum|alt.badge.img+8

See https://knowledge.safe.com/questions/38060/sde-connection-files-and-fme-server.html

I might be OK with read only ArcSDE connection files being in a shared area, but ones with write access need to be restricted. So new system share may be the answer.

If I have a Workspace with a read only ArcSDE connection and a write ArcSDE connection, I can't seem to choose separate locations on server for each one - they both have to go in the same place (that's using FME 2018). So it looks like I will have to create a Workspace with the read only connection file and publish that to upload it to the shared area, then use that in Workspace with the write connection file stored locally.

Is there no way to load ArcSDE connection files into the shared area outside of Workspace publishing? Can you just copy the files to the appropriate folder on the FME Server server?

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, 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

david_r
Celebrity
  • March 6, 2020

I use Python scripted parameters to determine the location of the SDE connection files, then link those to the appropriate reader/writer. Example:

import fme
if fme.macroValues['FME_SHAREDRESOURCE_DATA']:
    # We're running on FME Server
    return fme.macroValues['FME_SHAREDRESOURCE_DATA'] + 'connectionFiles/myConnection.sde'
else:
    # We're running on FME Desktop
    return 'C:/dev/sde/myConnection.sde'

Very trivial example, but you get the idea, I hope. This lets me pool all the connection files in a shared directory structure on the FME Server, and not having to upload the connection files every time I republish a workspace.