Named database connections on FME Server - limitations? | Community

Hi,

My 2015 FME workspace was ready to be published to FME Server 2015 but named connections aren't supported. I see they are supported in 2017 so we will need to upgrade.

My question: are there any other known limitations with the named connections on FME Server 2017 that I should be aware of.

I'm using the named connections in the following way:

I have 3 Oracle spatial connections in the Navigator using named connections linked to 3 published parameters. I also have 70 Joiner transformers, using Oracle Non-spatial, that reference the named connection as a published parameter.

Are the above supported if I publish to FME Server 2017.1?

I'd like to test but I don't have enough time allocated in this sprint to do so.

Thanks,

Annette

Page 1 / 1

I'll just address this phrase:

I'd like to test but I don't have enough time allocated in this sprint to do so.

This sounds like a recipe for disaster.

I'll just address this phrase:

I'd like to test but I don't have enough time allocated in this sprint to do so.

This sounds like a recipe for disaster.

We will just continue to use the desktop until we upgrade our FME server as planned next year. The export is only run a few times per year but I want to make it self serve.

Yes, this is only our third sprint so we are learning. So far so good.

I'll just address this phrase:

I'd like to test but I don't have enough time allocated in this sprint to do so.

This sounds like a recipe for disaster.

In fact, it makes me a bit reluctant to answer...

What are your exact version of Desktop and Server?

Currently 2015.0 for both Desktop and Server. We will upgrade to 2017.1.

I'll just address this phrase:

I'd like to test but I don't have enough time allocated in this sprint to do so.

This sounds like a recipe for disaster.

:( a case where less detail is more. Mainly I am wondering should I continue to use named connections, even with FME 2017, if I am going to encounter more problems.

We are using 2017 a lot with named database connection without any issues for readers, transformers and writers.

Since we have multiple environments, the named connections are helping a lot but in our case, they have to exist on FME Server before publishing (we are not creating them at publication time).

We are using 2017 a lot with named database connection without any issues for readers, transformers and writers.

Since we have multiple environments, the named connections are helping a lot but in our case, they have to exist on FME Server before publishing (we are not creating them at publication time).

I can add that I'm also (slowly) starting to use named connections and I've yet to have any issues, they've worked really well for me so far.

Only annoyance is that ArcSDE Geodatabase connections insist on using those pesky .sde connection files rather than the FME named connections, but I can't blame Safe for that one.

I have used Named connections in FME desktop and Server 2017 for both Oracle and SQL Server and have had no issues.

I have used the method to create them in the FME Server Web UI or upload them from FME Desktop.

You do need the Oracle client installed (but you knew that) and have the same entries in the TNSNames.ora file as on desktop to be able to make the connections.

I have used Named connections in FME desktop and Server 2017 for both Oracle and SQL Server and have had no issues.

I have used the method to create them in the FME Server Web UI or upload them from FME Desktop.

You do need the Oracle client installed (but you knew that) and have the same entries in the TNSNames.ora file as on desktop to be able to make the connections.

Thanks Erik Jan.

We are using 2017 a lot with named database connection without any issues for readers, transformers and writers.

Since we have multiple environments, the named connections are helping a lot but in our case, they have to exist on FME Server before publishing (we are not creating them at publication time).

Thanks Larry and David.

David, Yes, I agree the .sde connections are a pain. Do you upload the sde connections to the server or reference them from a shared folder?

Thanks Larry and David.

David, Yes, I agree the .sde connections are a pain. Do you upload the sde connections to the server or reference them from a shared folder?

I usually upload the necessary .sde files to a separate folder in the FME Server shared resources structure. That way I can reference them in the workspaces like e.g. like this:

$(FME_SHAREDRESOURCE_DATA)/SDEFiles/myconnection.sde

An observation from experience,.. make sure port 7069 is open in your firewall rules - this is the port that connection communicates on.

Reply