9 Projects
Find out about projects in Oracle Data Integrator and how and when to create them.
Projects and Folders
Learn about projects and folders in Oracle Data Integrator.
A project is a collection of ODI objects created by users for a particular functional domain. However, only certain objects can belong to projects. Similarly, certain objects always belong to projects. Packages, procedures, and mappings always belong to folders, and folders always belong to projects. Variables, sequences, and user functions either belong to projects or can be created with global scope. Knowledge Modules (KMs) either belong to projects or can be imported with global scope. Also some KMs are considered built-in (neither project nor global). Markers always belong to a project.
A folder is a hierarchical grouping beneath a project and can contain other folders and objects. Every package, mapping, or procedure must belong to a folder.
When should you create folders? One guideline is to create a folder per “package” or scenario. Thus, all mappings that are used in the same package are grouped together. The folder represents all that is necessary for a given execution unit. As a result, maintenance is typically simplified.
It's not always easy to know when to create a project or when to create a subfolder within the same project. As a general rule, if you have a new functional domain or are starting an integration project, you should create a new project. Also, if you specifically want to keep objects separate from each other, you should create them in separate projects. On the other hand, a folder is useful when you want to organize an existing project. When you have a large number of mappings, procedures, or packages in a project, you should consider grouping them into folders. You can also use folders to set up different security levels within the same project. Each folder can have its own unique privileges. Remember that projects do impose strict boundaries on information sharing. This means that objects created in one project cannot be used by another project. If you want to enable an object to be used by other projects, you should make the object global. Thus, you enable the global variables, sequences, Knowledge Modules, and user functions to be used by any project. Folders, however, do not impose boundaries. Thus, objects in one folder can be used by any other objects in a project.
See Introduction to Integration Projects in Developing Integration Projects with Oracle Data Integrator.
See Organizing Projects with Folders in Developing Integration Projects with Oracle Data Integrator.
Create Projects and Folders
Learn the steps to create a project, or create a folder in Oracle Data Integrator.
- In the Designer Navigator, select New Project from the drop-down menu at the top of the Projects view.
- Name the project.
You should generally make it reflect the functional domain that it covers.
- Change the code to anything you like. (optional)
Even though the code is generated in UPPERCASE it doesn't have to remain that way.
The code is used as a prefix when referring to the variables created within this project.
Default marker sets are automatically added to your blank project. Similarly, a folder is created automatically to hold the mappings, packages, and procedures that you develop.
- Right-click the project or folder where you want to create the new folder.
- Select Insert Folder from the context menu.
- Give a name to the folder.
After the folder is created, you can drag it to other folders, or onto the parent project, to reorganize the structure of your project.
See Creating a New Project in Developing Integration Projects with Oracle Data Integrator.
See Organizing Projects with Folders in Developing Integration Projects with Oracle Data Integrator.