Hi,
Is it possible to define, inside a custom transformer, a published parameter corresponding to a named database connection ?
The idea is to develop a generic custom transformer that manage metadata tables. This custom transformer must be able to work on differents database/schema.
Thanks,
Thibaut.
Thibaut,
Yes, that is possible, and you can do it using embedded connections. For example, I created a custom transformer called the ELocationPopulater, which needs to run a SQL query on an Oracle table. So, within the custom transformer, in the SQLExecutor parameters, I chose to "Embed Connection Parameters" - then, for the Service Name, Username, and Password, I created user parameters (see screenshot below).
When I use the custom transformer in a workspace, I am prompted to enter the correct values for the connection parameters:
Hopefully this helps!
-Courtney
Thibaut,
Yes, that is possible, and you can do it using embedded connections. For example, I created a custom transformer called the ELocationPopulater, which needs to run a SQL query on an Oracle table. So, within the custom transformer, in the SQLExecutor parameters, I chose to "Embed Connection Parameters" - then, for the Service Name, Username, and Password, I created user parameters (see screenshot below).
When I use the custom transformer in a workspace, I am prompted to enter the correct values for the connection parameters:
Hopefully this helps!
-Courtney
@courtney_m Thanks for the answer but I would like to use named connection instead of embedded connection (sorry was unclear on my question, I edited it accordingly).
I don't want to include database connection parameters in the workspace. The main reason is that the workspaces will be publish to multiples FME server, each one with a separate database. The idea is to create the same named connection on each FME server but with different parameters. Like that, according to witch server the workspace is published, the connection will be done on the right database without any modification of the workspace.
@courtney_m Thanks for the answer but I would like to use named connection instead of embedded connection (sorry was unclear on my question, I edited it accordingly).
I don't want to include database connection parameters in the workspace. The main reason is that the workspaces will be publish to multiples FME server, each one with a separate database. The idea is to create the same named connection on each FME server but with different parameters. Like that, according to witch server the workspace is published, the connection will be done on the right database without any modification of the workspace.
@courtney_m Thanks for the answer but I would like to use named connection instead of embedded connection (sorry was unclear on my question, I edited it accordingly).
I don't want to include database connection parameters in the workspace. The main reason is that the workspaces will be publish to multiples FME server, each one with a separate database. The idea is to create the same named connection on each FME server but with different parameters. Like that, according to witch server the workspace is published, the connection will be done on the right database without any modification of the workspace.