Skip to main content
  • EN

Hi, 

I have a workbench that references a ESRI GIS Connection File on my local shared network (\\gis\FME\admin@sde@sde_spatial.sde), the workbench runs fine with this as my Connection File parameter.

 

I now want to publish this new workbench project to my FME Server, and I know I already have uploaded the SDE Connection File to the resources section, and I have found the link to be - $(FME_SHAREDRESOURCE_SYSTEM)/Connection Files/admin@sde@sde_spatial.sde

Each time I try to publish, the software wants me to upload a copy of my SDE file, but I would love to tell FME to use the one already published. 

 

I have tried to simply plug in the server reference in my FME Desktop Workbench but when I test it on my local machine it keeps wigging out with:

2021-11-14 23:36:16|   4.1|  0.1|ERROR |An error occurred while attempting to retrieve the connection parameters from the connection file '/Connection Files/admin@sde@sde_spatial.sde'
2021-11-14 23:36:16|   4.1|  0.0|ERROR |A fatal error has occurred. Check the logfile above for details

I am new to FME Server so I haven't quite got my head around how to use the resources, so I have been pulling my hair out trying to work out how to use this already published file, rather than upload a new copy every time I publish another workbench to the server.

Hi benvk,

 

We also use an SDE connection on our FME server, however we have our connection on a network drive which is accessible to FME Server. This way we don't get the request to upload the file and we don't have to attempt to find the file in the FME Connection Files folder as well as not having to manage multiple copies of what is supposed to be the same connection(but probably won't be if something changes in the future). Another nice thing is that the file path will be the same for both the desktop version of FME and the server version of FME.

 

I know that this is more of a workaround for your problem but maybe the information is useful to you.

Hi benvk,

 

We also use an SDE connection on our FME server, however we have our connection on a network drive which is accessible to FME Server. This way we don't get the request to upload the file and we don't have to attempt to find the file in the FME Connection Files folder as well as not having to manage multiple copies of what is supposed to be the same connection(but probably won't be if something changes in the future). Another nice thing is that the file path will be the same for both the desktop version of FME and the server version of FME.

 

I know that this is more of a workaround for your problem but maybe the information is useful to you.

@birgit​ thats great info, thank you.

How did you make a network drive accessible to your server?

Did you add the directory per Example 4?

@birgit​ thats great info, thank you.

How did you make a network drive accessible to your server?

Did you add the directory per Example 4?

@benvk​ , I am not sure how it is done because our FME Server environment is managed by another company which does the server setup, maintenance and settings but I suspect that example 4 is correct. The path we use in FME Server looks like //aMachineName/Data/SDEConnections which sort of looks like the path used in the example.

 

@birgit​ thats great info, thank you.

How did you make a network drive accessible to your server?

Did you add the directory per Example 4?

On top of this, we use a switch and a script, so we can choose which connection (test or prod) we use when running the workspace in workbench while we are developing.

When the workspace is running on server, it is selecting the test or prod connection based on fme server engine name.

So no mistakes when publishing to prod and running test data etc, and full flexibility when developing a workspace.

Reply


Community Stats

30,168
Posts
114,527
Replies
37,826
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.