6.66 Sub-Model Editor

Use to create sub-models.

A sub-model is a group of functionally homogeneous datastores within a model. The datastores of a model can be inserted into a sub-model using drag-and-drop, or by automatic distribution.

The Sub-Model Editor has the following tabs:

Click Sub-Model Check to perform an immediate static check of the datastores in the sub-model. This check uses the Check Knowledge Module (CKM) shown at the model level.

6.66.1 Definition

Properties	Description
Name	Name of the sub-model used in the user interface of the Designer Navigator.
Code	Unique code of the sub-model.

6.66.2 Distribution

Use to define a distribution rule of the datastores in your sub-models.

Datastores, depending on the datastores distribution rule for each sub-model, are compared to the automatic assignment mask. If they match this pattern, then they are moved into the sub-model.

There are two methods to classify:

Click Distribution to apply the current rule to the datastores.
At the end of the reverse-engineering process, all rules are applied in the order specified in the Order of mask application after a Reverse field.

Properties	Description
Datastores Distribution rule	Determines which datastores will be considered and compared to the automatic assignment mask: No automatic distribution: No datastore is considered. Automatic Distribution of all Datastores not already in a Sub-Model: Datastores located in the root model in the sub-model tree are considered. Automatic Distribution of all Datastores: All datastores in the model (and sub-models) are considered.
Automatic Assignment Mask	Determines the pattern to which the datastores names must adhere, to be classified in this sub-model.
Order of mask application after a Reverse.	Determines the order in which the mask is applied at the end of a reverse-engineering process. Consequently, a rule with a high priority order on all datastores will have precedence. A rule with a high order on non classified datastores will apply only on datastores ignored by the other rules' patterns. At the end of the reverse-engineering process, new datastores are considered as non classified. Those already classified as a sub-model stay attached to their sub-model.

Properties

Description

Datastores Distribution rule

Determines which datastores will be considered and compared to the automatic assignment mask:

No automatic distribution: No datastore is considered.
Automatic Distribution of all Datastores not already in a Sub-Model: Datastores located in the root model in the sub-model tree are considered.
Automatic Distribution of all Datastores: All datastores in the model (and sub-models) are considered.

Automatic Assignment Mask

Determines the pattern to which the datastores names must adhere, to be classified in this sub-model.

Order of mask application after a Reverse.

Determines the order in which the mask is applied at the end of a reverse-engineering process.

Consequently, a rule with a high priority order on all datastores will have precedence. A rule with a high order on non classified datastores will apply only on datastores ignored by the other rules' patterns.

At the end of the reverse-engineering process, new datastores are considered as non classified. Those already classified as a sub-model stay attached to their sub-model.

"Creating and Organizing Sub-Models" in the "Organizing and Documenting Integration Projects" chapter in Oracle Fusion Middleware Developing Integration Projects with Oracle Data Integrator