Tuesday, June 24, 2014

Oracle Data Integrator Project Components in ODI 12c

Oracle Data Integrator Project Components in ODI 12c

The following components are stored into a project. They appear in the in the Project accordion in the Designer Navigator, under the project's node.
Folder
Folders are components that help organizing the work into a project. Folders contain packages, mappings, procedures, and subfolders.
Packages
A package is a workflow, made up of a sequence of steps organized into an execution diagram. Packages assemble and reference other components from a project such as mappings, procedure or variable.
Mappings
A mapping is a reusable dataflow. It is a set of declarative rules that describes the loading of one or several target datastores from one or more source datastores. See 
Procedure
A Procedure is a reusable component that groups a sequence of operations that do not fit in the mapping concept.
Examples of procedures:
1)     Wait and unzip a file
2)     Send a batch of files via FTP
3)     Receive emails
4)     Purge a database
Variable
A variable's value is stored in Oracle Data Integrator. This value may change during the execution.
Sequence
A sequence is a variable automatically incremented when used. Between two uses the value is persistent.
User Functions
User functions allow you to define customized functions or "function aliases," for which you will define technology-dependent implementations. They are usable in mappings and procedures.
Knowledge Modules
Oracle Data Integrator uses Knowledge Modules at several points of a project design. A Knowledge Module is a code template related to a given technology that provides a specific function (loading data, reverse-engineering, journalizing).
Markers
A component of a project may be flagged in order to reflect a methodology or organization. Flags are defined using markers. These markers are organized into groups, and can be applied to most objects in a project.
Scenarios

When a package, mapping, procedure, or variable component has been fully developed, it is compiled in a scenario. A scenario is the execution unit for production. Scenarios can be scheduled for automated execution. See 

No comments:

Post a Comment