Use to create a new model and other Topology objects.
The required connection details to create a new model are:
Login Name: Name of the login defined to the Master or Work Repository.
User: Oracle Data Integrator user name.
Password: Oracle Data Integrator user password.
These parameters have been specified in the Repository Connection Information Editor.
The Create New Model and Topology Objects wizard has the following steps:
Step 2 - Associate the new model with a new or existing data server
Step 3 - Associate the new model with a new or existing physical schema
| Properties | Description |
|---|---|
| Name | Name of the model used in the user interface. |
| Technology | Technology of the data model.
As a data model is linked to a single technology, it is a physical data model whose datatypes are native to this technology. |
| Logical Schema | Logical schema of the topology to which this model is attached. |
| Context | Context in which the new model is executed. |
| Properties | Description |
|---|---|
| Name | Name of the data server, as it appears in the user interface.
Note: For naming data servers, it is recommended to use the following naming standard: <TECHNOLOGY_NAME>_<SERVER_NAME>. |
| Technology | Only Appears if the Technology selected for the Model is of type Generic SQL.
Technology linked to the data server. |
| User | User name used for connecting to the data server. |
| Password | Password linked with the user name.
Note: This password is stored encrypted in the repository. |
| Driver List | Provides a list of available drivers to be used for the data server. |
| Driver | Name of the driver used for connecting to the data server. |
| URL | Provides the connection details. |
| Properties | Description |
|---|---|
| Key | Key identifying this property. This key is case-sensitive. |
| Value | Value for the property. |
Note:
For data servers that use ODI Special Drivers, the Key is pre-populated and only the Value must be entered. For information on ODI Special Drivers, see the Data Server Editor section.Click Test Connection to verify that the connection is working.
| Properties | Description |
|---|---|
| Name | Name of the physical schema, as it appears in the graphic interface. It is calculated automatically and is read-only. |
| Datasource (Catalog) | Only appears if the Technology selected supports Catalogs.
Name of the catalog in the data server. |
| Schema (Schema) | Only appears if the Technology selected supports Schemas.
Name of the schema in the data server. Schema, owner, or library where the required data is stored. Caution: Oracle Data Integrator lists all the schemas present in the data server. Sometimes, Oracle Data Integrator cannot draw up this list. In this case, you should enter the schema name, respecting the case. |
| Datasource (Work Catalog) | Only appears if the Technology selected supports Catalogs.
Indicate the catalog in which you want to create these objects. For some data validation or transformation operations, Oracle Data Integrator may require work objects to be created. |
| Schema (Work Schema) | Only appears if the Technology selected supports Schemas.
Indicate the schema in which you want to create these objects. For some data validation or transformation operations, Oracle Data Integrator may require work objects to be created. It is recommended that you create a specific schema dedicated to any work tables. By creating a schema named SAS or ODI in all your data servers, you ensure that all Oracle Data Integrator activity remains totally independent from your applications. Caution: Oracle Data Integrator lists all the schemas present in the data server. Sometimes, Oracle Data Integrator cannot draw up this list. In this case, you should enter the schema name, respecting the case. Note: If you do not set a Work Schema, it defaults to the Schema during the execution. |
For more information, see Context Editor, Data Server Editor, Physical Schema Editor.
Oracle Fusion Middleware Developing Integration Projects with Oracle Data Integrator