10 Importing Design Definitions from Oracle Designer

Using Oracle Designer Sources

You can create a source module that connects to an Oracle Designer repository. When the definitions for an application are stored and managed in an Oracle Designer repository, the time required to connect to the application is reduced.

Designer repositories use workareas to control versions of an object. By selecting a workarea, you can specify a version of a repository object. With Oracle Designer, you can also group objects into container elements within workareas. Container Elements contain definitions for namespace and ownership of objects, and enable you to view objects even if they are owned by a different user. Because Designer container elements are controlled by workareas, they are version controlled. See the Oracle Designer documentation for more information about workareas and container elements.

All visible objects of a workarea or a container element in Designer are available for use as data sources. To select Designer objects as a source, you must:

• Specify a workarea, and

• Specify the container element in the workarea

The list of repository objects available for import is determined by the following criteria:

• The object type must be supported by Oracle Warehouse Builder (Table, View, Sequence, and Synonyms).

• The object must be accessible in the specified workarea. This determines the version of objects accessed.

• The object must be visible in the specified container element. The list displays objects owned by the specified container element and other objects shared by the specified container element, but not owned by it.

To import definitions from a Designer source, you must create an Oracle database module.