I have got an environment with a set of Named Connections however I would like to test them without pushing up a workbench. Is this possible?
Best Answer
FME Server Database Connections
Best answer by ciarab
@johnbyrnejb
you can test your database connections through the workbench under Tools>FME Options and then select your database connections. Your named connections are already defined here and if you select them there is a test button available which could use
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.
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.
+18- Supporter
Hi @johnbyrnejb,
Interesting, why? eventually you will need to use a workspace....
I suggest you create a simple workspace set to read one feature per connection, to test your connections.
Hope this helps.
Hi @johnbyrnejb,
Interesting, why? eventually you will need to use a workspace....
I suggest you create a simple workspace set to read one feature per connection, to test your connections.
Hope this helps.
But yes I feel like a workspace to test connections is the only way :(
Hi @johnbyrnejb,
Interesting, why? eventually you will need to use a workspace....
I suggest you create a simple workspace set to read one feature per connection, to test your connections.
Hope this helps.
+9- Contributor
- Best Answer
@johnbyrnejb
you can test your database connections through the workbench under Tools>FME Options and then select your database connections. Your named connections are already defined here and if you select them there is a test button available which could use
@johnbyrnejb
you can test your database connections through the workbench under Tools>FME Options and then select your database connections. Your named connections are already defined here and if you select them there is a test button available which could use
I don't see a test button in the Database Connections tab of my FME Options of my FME Desktop. I've looked in Desktop 2016 and Desktop 2017. There is only a "Public" column. Where is the test button?
Right-click on the Connection and select 'Test',
Hi @johnbyrnejb,
Interesting, why? eventually you will need to use a workspace....
I suggest you create a simple workspace set to read one feature per connection, to test your connections.
Hope this helps.
+6- Contributor
Hi @johnbyrnejb,
Interesting, why? eventually you will need to use a workspace....
I suggest you create a simple workspace set to read one feature per connection, to test your connections.
Hope this helps.
Itay (I realise this is a bit old but see exactly where @johnbyrnejb is going.
We have developed a system using fme workbench and publishing the workbenches to server. For a "release" we create a project in Server and secure that (In TFS) and at some time later we will get to production where we want to import the project thereby releasing a known tested set of workbenches/automations/schedules.
We then need to create/update the data connections to point to the production database and for db connections this has to be done manually in FME Server. Ideally we then need to test this database connection, but using a workbench is not appropriate as we do not allow/want publication of workbenches to production. Also, we don't have a model which we can run adhoc without impacting the system.
Interestingly where we use arcgis arcsde connections we can achieve the above as the connection file is mastered in arcCatalog and can therefore be tested and is then loaded as a shared resource in server.
Is there any way yet of testing a db connection in Server?