Skip to main content
  • EN

Does anyone know what the 'rules' are for best practice sharing of named database connections? I'm seeing some very odd behavior that I can't explain.

It seems that for example there was a name change for the named connections database between FME 2016 and 2017 from namedConnections.data to fme_connections.data, meaning that an old connection database presumably must be exported as XML and reimported to a newer FME before the connections can be used. So, its not possible to share connections between different versions of FME in an organisation where there are different FME versions installed.

Also, I'm seeing connections that are created on one machine, that work fine when 'tested', when they are tried to be used on another machine in the same organisation and they are 'tested' a whole raft of errors come back and authentication fails. Interestingly the authentication errors mention FME Server and web APIs... Its super odd. At the moment I don't have access to the full errors, but will post when I get them.

Anyway, in a specific organisation I'm working with we've had to resort to embedded connection credentials because the named connection approach is proving unreliable.

Incidentally most testing has been done with 64bit FME Desktop 2017.0.1.1 b17291 sharing connections between two Windows 2012 R2 Virtual Machines on separate networks, that have permissions to a shared resource folder containing the shared connections database.

Anyone got any tips or similar experiences?

Much appreciated, Dave

Hi Dave

I can confirm the name change of the namedConnections.data to fme_connections.data.

I simply nominate the old as master, do the changes here and overwrite the new one when I make any change.

The sqlite versions are the same (3.8.8.3) so a symbolic link may also help.

About the web APIs, my HTTPCallers to the SharePoint web services authentication failed without any 'visible cause' claiming SSL related errors. I simply changed 'Verify SSL Certificates' to No in the HTTPCaller and no problem since then. We use NTLM authentication but it may work with the others, too. I know it is not a nice solution but they were temporary workspaces and we used them on local network.

Cheers, András

Reply


Community Stats

30,387
Posts
115,451
Replies
38,103
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.