Skip to main content
  • EN

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?

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.macroValuesr'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.

Reply


Community Stats

30,176
Posts
114,543
Replies
37,835
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.