for custom statistics purpose I would like to setup a SQL connection
to one or more databases setup under “Setting->JDBC Pools”.
The goal is to use this like a “JDBC Adapter Connection”.
I know that I can define this as “SQL Adapter Connection” but
this data is very Server-Specific and such a Package is difficult
to “Deploy” to an other server (every server need an other setup)
One other Question would be:
“How do I deploy a package with a JDBC connection if the connection
details are target-specific?”
but this is not the main goal of the question.
The main goal is to get the connection-details from the
“JDBC Pools” section or reuse the already available pools.
The Pool-Connection-Details required are:
* Archiving
* ISCoreAudit
* ProcessAudit
“How do I deploy a package with a JDBC connection if the connection
details are target-specific?”
Here is common practice to consider:
Define connections in their own package, never within the same package as the integration services
Never deploy connections. Always use IS Administrator to define them in each environment. Deploying a connection pointing to dev/test data, even momentarily enabled, can be disastrous.
I believe Deployer can deal with changing connection parameters on the fly but I’ve never done that. Perhaps someone else can chime in.