I’ve followed the ‘ODI Installation Guide for these different steps and added some custom comments, actions, you can still use the Installation Guide as reference guide.
First I’ve installed the administrator-version of ODI, so I’m able to define my own repositories and the second step I’ve performed was the definition of the schema for my master and work repository.
I hear you thinking … ‘what is a master and work repository, why do I need this?’ … well, the definition from the ‘ODI Installation Guide’ states the following:
- Master Repository: Data structure containing information on the topology of the company’s IT resources, on security and on version management of projects and data models. Mostly only one Master repository is needed.
- Work Repository: Data structure containing information on data models, projects, and their use. Several work repositories can be designated with several master repositories if necessary. However, a work repository can be linked with only one master repository for version management purposes.
In the previous step I’ve defined the 2 schema’s used for the master and work repository (create db-schema’s), now it’s time to actually create these 2 repositories.
Let’s create the master repository – creation of tables and automatic importing of definitions – for the schema we’ve defined ‘snmp’:
- Go to your Oracle Data Integrator in the Start Menu and select ‘Master Repository Creation’ from the ‘Repository Management’
- Define the settings of your database and your master repository-schema in the ‘Master Repository Creation Wizard’ as shown below (don’t forget to specify a meaningfull Id, not the default 0)
When you click OK the different components – tables, indexes, schema’s, … – will be created and imported into the master repository and you can follow up this creation in the log-window.
After everything is succesfully created a pop-up window will be shown informing you about the succesfull creation of the Master Repository.
Afterwards we will connect to our new master repository via the ‘Topology Manager’:
We’ve now succesfully created our master repository and connected to it via our Topology Manager.
The next step is to create the work repository. Go the 5th tab shown below in the Topology Manager to show the existing repositories, right-click on the Work Repository and choose ‘Insert Work Repository’.
Define the jdbc-driver and username and password for the schema you’ve created for the work repository.
You can test your connection to be sure all the settings were defined correctly and then click ok.
The next screen is shown to define the specific settings for the work repository, choose a unique ID and define a name for the work repository. Click OK.
To connect and work with our newly created work repository, perform the following:
- Choose the Designer-submenu in the Oracle Data Integrator menu of your Start Menu
- Choose to create a ‘New Data Integrator Connection’ choosing the first icon to the right of the dropdown-box for ‘Login name’
- Enter the different settings needed to be able to connect to your work repository. In the Database Connection – section you need to specify the connection the (Master Repository). In the last part you need to specify the Name of the Work Repository which can be chosen from a list. The name you’ve defined for the work repository will be shown in this screen.
- Click OK
- Choose these new settings to Login to the Oracle Data Integrator
Now I can perform the same steps as I’ve discussed in the previous blogs to be able to work on my customly defined master and work repository.
When you’ve got adminstrator privileges this is the standard way to go:
- create master and work repository schema’s on the database
- create master and work repository through the ODI as mentioned in this thread
- create different models, interfaces, … to work with these custom defined repositories.
I’ve done the same steps for my own ‘administrator’ environment as mentioned in the previous posts so I can work on my administrator environment and in the development environment.
In the previous post I’ve created the microsoft ODBC DataSource and I’ve reverse engineered my Excel file into a datamodel in the Designer, now it’s time to start creating interfaces.
Oeps … I’ve stumbled upon a ‘logical steps to perform when working with ODI’, and the logical step to perform after the definition of the model isn’t definining interfaces … let’s have a closer look :
Managing an Oracle Data Integrator project generally involves the following steps:
- Creating and reverse-engineering models. (Check!)
- Creating a project.
- Using markers (optional).
- Creating and organizing folders.
- Importing KMs.
- Creating and modifying reusable objects: Variables, Sequences, Interfaces, Procedures, User functions.
- Unit testing interfaces and procedures (back to step 6).
- Building packages from elements created in step 6.
- Integration testing the packages.
- Generating scenarios.
- Scheduling scenarios.
- Managing the scenarios in production.
- Maintenance, bug fixing and further modifications (back to step 6).
So the next step to perform – after we’ve created our data model – is to create a new project, a project is nothing more than a ‘container’ holding a group of objects created in Oracle Data Integrator.
- Go to the designer and choose the projects-tab, this is the default-tab shown when you open up designer. For our newly created work repository no projects are created yet so we can start building from scratch.
- Choose the first icon ‘Insert Project’
- Define a name for the new project
After we’ve defined the project the different objects that can be created in a project are shown, such as variables, knwoledge modules, sequences, …
The next step to perform is the creation of ‘folders’ to organize our interfaces, procedures and packages, but in my newly created projet a ‘First Folder’ has already been created.
Right-click on this folder and choose ‘edit’ and rename the folder to your own choice.
The next logical step would be to import Knowledge Modules of interest to our project, but in my case the default Knowledge Modules were already imported, so no actions need to be performed here.
Finally I’m ready to create interfaces to be able to link our source-data to our target-data, the definition given in the UserGuide is the following: ‘An interface consists of a set of rules that define the loading of a datastore or a temporary target structure from one or more source datastores.’.
I’ll keep you posted !