Create Datastores and Columns

Working with Common Format Designer 6-5

6.3 Generating DDL scripts

When data structure changes have been performed in a data server, you usually perform an incremental reverse-engineering in Oracle Data Integrator to retrieve the new metadata from the data server. When a diagram or data model is designed or modified in Oracle Data Integrator, it is necessary to implement the data model or the changes in the data server containing the model implementation. This operation is performed with DDL scripts. The DDL scripts are generated in the form of Oracle Data Integrator procedures containing DDL commands create table, alter table, etc. This procedure may be executed on the data server to apply the changes. To generate the DDL scripts:

1. In the Models tree of Designer Navigator, select the data model for which you

want to generate the DDL scripts.

2. Right-click, then select Generate DDL. The Generate DDL for Oracle Data

Integrator Model dialog is displayed.

3. Click Yes if you want to process tables that are not in the Oracle Data Integrator

model, otherwise click No. Oracle Data Integrator retrieves current state of the data structure from the data server, and compares it to the model definition. The progression is displayed in the status bar. The Generate DDL Editor appears, with the differences detected.

4. Select the Action Group to use for the DDL script generation.

5. Click the ... button to select the Generation Folder into which the procedure will be created.

6. Select the folder and click OK.

7. Filter the type of changes you want to display using the Filters check boxes.

8. Select the changes to apply by checking the Synchronization option. The

following icons indicate the type of changes: ■ - : Element existing in the data model but not in the data server. ■ + : Element existing in the data server but not in the data model. ■ = : Element existing in both the data model and the data server, but with differences in its properties example: a column resized or attached elements example: a table including new columns.

9. Click OK to generate the DDL script.

Oracle Data Integrator generates the DDL scripts in a procedure and opens the Procedure Editor for this procedure. Note: The templates for the DDL scripts are defined as Action Groups. Check in the Topology Navigator that you have the appropriate action group for the technology of the model before starting DDL scripts generation. For more information on action groups, please refer to the Knowledge Module Developers Guide for Oracle Data Integrator. 6-6 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator

6.4 Generating Interface INOUT

For a given model or datastore assembled using Common Format Designer, Oracle Data Integrator is able to generate: ■ Interfaces IN : These integration interfaces are used to load the models datastores assembled from other datastorescolumns. They are the integration process merging data from the original datastores into the composite datastores. ■ Interfaces OUT : These integration interfaces are used to extract data from the models datastores. They are generated using the interfaces including the interfaces IN already loading the models datastore. They reverse the integration process to propagate the data from the composite datastore to the original datastores. For example, an Active Integration Hub AIH assembles information coming from several other applications. It is made up of composite datastores built from several data models, assembled in a diagram. The AIH is loaded using the Interfaces IN, and is able to send the data it contains to the original systems using the Interfaces OUT. To generate the Interfaces IN:

1. In the Models tree of Designer Navigator, select the data model or datastore for

which you want to generate the interfaces.

2. Right-click, then select Generate Interfaces IN. Oracle Data Integrator looks for

the original datastores and columns used to build the current model or datastore. The Generate Interfaces IN Editor appears with a list of datastores for which Interfaces IN may be generated.

3. Select an Optimization Context for your interfaces. This context will define how

the flow for the generated interfaces will look like, and will condition the automated selection of KMs. 4. Click the ... button to select the Generation Folder into which the interfaces will be generated.

5. In the Candidate Datastores table, check the Generate Interface option for the

datastores to load.

6. Edit the content of the Interface Name column to rename the integration

interfaces.

7. Click OK. Interface generation starts.

The generated interfaces appear in the specified folder. To generate the Interface OUT: Note: Interfaces automatically generated are built using predefined rules based on repository metadata. These interfaces can not be executed immediately. They must be carefully reviewed and modified before execution Note: If no candidate datastore is found when generating the interfaces IN, then it is likely that the datastores you are trying to load are not built from other datastores or columns. Automatic interface generation does not work to load datastores and columns that are not created from other models datastores and columns.