Community
Participate
Working Groups
In the current DTP connection profile framework, a JDBC connection profile instance is expected to get created based on user input and selection of a specific driver definition. The proposed enhancement is to add the capability to take the basic JDBC connection properties (that may be used with JDBC API to open a connection) and use DTP Connectivity API to create a corresponding, transient connection profile instance that can be used to connect and access the DTP enablement features. To support the above feature, 3 areas of enhancements are identified. In order to systematically map generic JDBC connection properties to a DTP Database connection profile properties, it will need to navigate and identify the corresponding values for these 2 sets of connection profile properties: * Database vendor and version (specifics in bug #253523) * Connection profile provider id (specifics in bug #253584) In addition, a connection profile instance is normally persisted in a repository. Additional support to create a transient connection profile instance would make it easier for adopters use (specifics in bug #253606).
Linda, can we consider this closed for Galileo?
Yes, indeed.