Generate Scenario Editor

Generate Scenario Editor


Use to generate new scenarios.

A scenario is designed to put a source component (interface, Package, procedure, variable) into production. A scenario results from the generation of code (SQL, shell, and so forth) for this component.

Notes:

Once generated, the scenario is stored inside the work repository. The scenario can be exported then imported to another repository (remote or not) and used in different contexts.

The scenario code (the language generated) is frozen, and all subsequent modifications of the components that contributed to creating it will not change it in any way.

The Name and Version fields of the Scenario are preset with the following values:

Name: The same name as the latest scenario generated for the component

Version: The version number is automatically incremented, if the latest version number ends with an integer. If the latest version does not end with an integer, the latest version number will be displayed in the Version field. Please change the version number according to your needs. Notet that you cannot use the same version number and version name for a scenario.

Generate Interfaces OUT Editor

Generate Interfaces OUT Editor
 

Use to automatically generate interfaces to extract data from datastores of a given data model, based on the existing interfaces used to load data into these datastore. These interfaces invert the existing data flows targeting this model.

Interfaces OUT are generated using the interfaces (including the interfaces IN) already loading the model's datastores. They invert the integration process to propagate the data from the composite datastore to the original datastores.

For a given model or datastore assembled using Common Format Designer, Oracle Data Integrator is able to generate interfaces OUT.

Specify the following parameters in the Generate Interfaces OUT Editor:

Generation

Optimization Context: The context used for creating the interfaces. This context is used to automatically generate the flow of the interfaces.

Generation Folder: Oracle Data Integrator project folder into which the interfaces will be generated.

You can click Search, to search for the project folder or click Clear Folder Selection if you want to remove the folder specified in this field.

Candidate Datastores

This list displays the datastores from the current model as the Target Tables. For each of these datastores, if Oracle Data Integrator is able to find a datastore for which the data flow can be inverted, it presents it as a Candidate Datastore.

Select the Generation/Generate Interface checkbox to generate interfaces for all or some of the candidate datastores attached to a given Target Table. Click Select all the suggested interfaces if you want to select all interfaces.

Edit the Interface Name column to rename the generated interfaces.

Generate Interfaces IN Editor

Generate Interfaces IN Editor
 

Use to generate interfaces to load a data model created using Common Format Designer.

Interfaces IN are integration interfaces that are used to load the model's datastores assembled from other datastores/columns in a model diagram. They are the integration processes merging data from the original datastores into the composite datastores.

Specify the following parameters in the Generate Interfaces IN Editor:

Generation

Optimization Context: The context used for creating the interfaces. This context is used to automatically generate the flow of the interfaces.

Generation Folder: Oracle Data Integrator project folder into which the interfaces will be generated.

You can click Search, to search for the project folder or click Clear Folder Selection if you want to remove the folder specified in this field.

Candidate Datastores

Select the Generate Interface checkbox for the datastores that you want to load. Click Select all the suggested interfaces if you want to select all interfaces.

Edit the Interface Name column to rename the generated interfaces.

Generate DDL Editor

Generate DDL Editor


Use to generate DDL scripts for your data models.

When a diagram or data model is designed or modified in Oracle Data Integrator, it may be necessary to implement the data model or the changes in the data server that contains the model implementation. This operation can be performed using DDL scripts generated by Oracle Data Integrator. The DDL scripts are generated in the form of procedures that contain DDL commands (create table, alter table, and so forth). This procedure may be executed on the data server to impact the changes.

Note that DDL scripts are generated based on the Action Group templates. Check that your have the appropriate action group for the technology of the model before starting DDL scripts generation. The action groups appear in the Topology.

Specify the following parameters in the Generate DDL Editor:

Action Group

The action group to use to generate the DDL script.

Procedure Name

The name of the generated procedure.

Generation Folder
Oracle Data Integrator project folder into which the procedure will be created.

You can click Search, to search for the project folder or click Clear Folder Selection if you want to remove the folder specified in this field.

Hierarchical/Linear View

The differences (new, deleted or modified) that exist between the data model defined in Oracle Data Integrator and the data server appear in a hierachical or flattened view. In the hierarchical view, for example, a new column will appear under a table node, and this table will appear with a modified marker. In the flatten view, all the changes appear at the same level.

The differences that appear in these views depend on the filters that are checked in the Filters option group.

Select the changes you want to apply by checking the Synchronization column checkbox. You can also select or unselect all the differences currently displayed by using the buttons on top of the views.

Filters

Check boxes to filter the type of changes you want to display