Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 175634 - Integrate Connection Profile framework with ODA runtime
Summary: Integrate Connection Profile framework with ODA runtime
Status: CLOSED FIXED
Alias: None
Product: Data Tools
Classification: Tools
Component: Open Data Access (show other bugs)
Version: 1.5   Edit
Hardware: PC Windows 2000
: P3 enhancement (vote)
Target Milestone: 1.5M6   Edit
Assignee: Linda Chan CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 149945
  Show dependency tree
 
Reported: 2007-02-26 21:34 EST by Linda Chan CLA
Modified: 2007-06-26 21:27 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Linda Chan CLA 2007-02-26 21:34:35 EST 
In DTP 1.0, the ODA framework only supports the "import" use of a connection profile's properties into an ODA data source design definition.

This enhancement includes: 
1) provide ODA runtime support of using externalized properties defined in a linked connection profile instance persisted in a connection profile store file.  It includes automatically adding related public data source properties on a linked connection profile for all ODA runtime data providers.

2) provide UI pages in the ODA design UI framework for an user to create/edit the selection of an external connection profile instance.
Comment 1 Linda Chan CLA 2007-02-26 22:12:07 EST 
The first part of this feature (ODA runtime support) is delivered in DTP 1.5 M5 release.  

The ODA runtime framework now provides a connection profile property provider service to look up and use an external connection profile instance.
To use this service, an ODA consumer application must specify the service name in the application context Map passed in its call to an oda.IConnection.setAppContext method.  The map entry in the connection's context must specify the following key-value pair:
        connAppContext.put( IPropertyProvider.ODA_CONSUMER_ID, 
                            Constants.CONN_PROFILE_APPL_ID );
where IPropertyProvider is in org.eclipse.datatools.connectivity.oda.consumer.services package,
and Constants is in org.eclipse.datatools.connectivity.oda.profile package, which contains the service name of the default connection profile property provider.

The oda.util.manifest package is enhanced to automatically include 2 additional public properties in all ODA drivers' data source definition for linking a connection profile.  The names of these 2 properties defined by the ODA framework are specifed as constants in the package:
ConnectionProfileProperty.PROFILE_NAME_PROP_KEY
and ConnectionProfileProperty.PROFILE_STORE_FILE_PATH_PROP_KEY .

An ODA consumer application UI will simply need to host the oda.design.ui's profile selection UI pages (part 2 of this feature scheduled in M6), which will in turn incorporate these 2 properties as part of an ODA data source design definition.
Comment 2 Linda Chan CLA 2007-03-01 03:04:01 EST 
Delivered the second part of this feature - provide UI pages in the ODA design UI framework for an user to create/edit the selection of an external connection profile instance.  Available in DTP 1.5 M6.
Comment 3 Linda Chan CLA 2007-06-26 21:27:16 EDT 
Verified and closed.