DTP Connectivity

BZ 253523- Define Database Vendor and Version profile property mapping in an Extension Point

Since DTP provides very little as far as built-in out-of-box database recognizers, adopters can now add their own databaseRecognition extension for the databases that they use. Instead of implementing an IDatabaseRecognizer that covers the specific product name and version metadata returned by their JDBC drivers, a developer can simply define the mapping in plugin.xml between a JDBC database product name and version values to those of a DTP enablement driver template.

This is the first step in beefing up DTP APIs to allow easier access to some of the more obscure DTP functionality without going through the UI.

BZ 253606 - Support handling of Transient Connection Profile instance

In previous releases, DTP did not have the concept of temporary or "transient" connection profiles. You could create a profile, but it would show up in the Data Source Explorer, which may not be what you need. Now you have the option of creating a transient profile instance via API from a set of profile properties, which you can use to connect to and access the profile data source. When the workbench is closed, these transient profiles are then disconnected and disposed of properly.

BZ 264520 - Need to filter Driver Templates

Developers now have a method of removing specific driver templates from the list via their own driverTemplateOverride extensions. This allows much more granular removal of templates if they are replacing driver templates with their own versions, or if they're not supporting particular drivers at all but don't want to remove entire sets of enablement plug-ins. Further work will be done, but the initial implementation is in and working.