Files
What are Database Connections?
Many readers, writers, and transformers require you to connect and authenticate to database services in order to use them. Database connections provide a convenient and secure way to store and reuse these connection parameters. For example, to use the Oracle Spatial Object reader, you need to provide a host, port, service name, username, and password.
A database connection makes it easy to connect to a database in a workspace. All you need to do is select the stored connection, instead of re-entering the connection parameters each time. If connection parameters change (e.g. a password), updating the database connection will also update every workflow using that connection.
FAQ Overview
- Where can I find out more about Database Connections on FME Flow?
- Is there a way to synchronize my FME Flow and FME Form connections?
- How do I manage Database Connections as an FME Flow Administrator?
- What account is used if a database connection is using Windows Authentication on FME Flow?
- What about database client software on FME Flow?
FAQ
Where can I find out more about Database Connections on FME Flow?
The FME Flow Administration Guide has all the information you need for uploading, removing, and updating database connections.
Is there a way to synchronize my FME Flow and FME Form connections?
Once the connection is stored in FME Flow, they need to be managed from the web UI and there is no correlation between the connection stored on Form and Flow. You can always choose to make edits to database connections in FME Form, and then republish the connection with an existing workspace.
How do I manage Database Connections as an FME Flow Administrator?
There are two common scenarios: 1) users can create database connections, and 2) users do not have access to create their own database connections.
Since there is no way to synchronize connections between FME Form and FME Flow, it is important to keep the names of the database connections unified between the two. This makes database connections easier to manage.
1. Users have permission to create connections
NOTE: If a user has permission to create connections, that user can also overwrite shared connections. Any workflows on FME Flow (belonging to any user) that contain that connection will be affected.
- Users can create their own database connections.
- Each user will be responsible for managing their own connections; this may lead to many connections for a single database.
- Users can choose to share their connections with others in FME Flow.
- Users must be careful when publishing workspaces that include a database connection with the same name as a previously shared connection. This may affect other workspaces using that database connection.
Image of the database connection page in FME Flow.
2. Users do not have permission to create connections (preferred)
As an FME Flow Administrator...
- You would have to create each connection in FME Flow (or upload them from FME Form).
- Access can be granted to any role or specific user account in FME Flow. Users will not have access unless they have been granted permissions to that connection through their account or role.
- You may choose to give users access to the Connections page. This will grant users access to the Connections page, where they can view all database connections they have access to.
Image of the user management page in FME Flow
- Ensure that all users that have workspaces with database connections create a published parameter with the connection. Then, the user can select the database connection as a published parameter in the run workspace page.
What account is used if a database connection is using Windows Authentication on FME Flow?
Some database connections can use Windows Authentication as the authentication method.
Image of the Database Connection dialog in FME Form
If you upload a database connection to FME Flow that uses Windows Authentication, the account used to authenticate the connection will be the Windows Account running the FME Flow Engine service - you may have to switch this account for this to work properly. This is a common misunderstanding for users of SQL Server databases. If the Engine Service user doesn't have access or permissions to the database, errors will be presented in the job log. Speak to your database administrator to ensure this service user has access to the database in question.
What about database client software on FME Flow?
Whether a database client needs to be installed or not depends on the database used. FME Flow will follow the same rules as an FME Form installation. For example, PostGIS should not need any additional set up, however, Oracle on FME Flow will.
You’ll have to work with the FME Flow administrator or your system administrator to ensure the required client software is installed before publishing a workspace containing a database format. It is common for database client software to be missing on new computer systems. Always review the FME Flow job log for clues when a job fails.
Additional Resources
FME Flow Troubleshooting: Database Connections
SDE Connection Management