Generating and Deploying Data Services Overview of Generated Services

9 Creating an Integration Project 9-1 9 Creating an Integration Project This chapter describes the different components involved in an integration project, and explains how to start a project. This chapter contains these sections: ■ Section 9.1, Introduction to Integration Projects ■ Section 9.2, Creating a New Project ■ Section 9.3, Managing Knowledge Modules ■ Section 9.4, Organizing the Project with Folders

9.1 Introduction to Integration Projects

An integration project is composed of several components. These components include organizational objects, such as folder, and development objects such as interfaces or variables. Section 9.1.1, Oracle Data Integrator Project Components details the different components involved in an integration project. A project has also a defined life cycle which can be adapted to your practises. Section 9.1.2, Project Life Cycle suggests a typical project lifestyle.

9.1.1 Oracle Data Integrator Project Components

Components involved in a project include components contained in the project and global components referenced by the project. In addition, a project also uses components defined in the models and topology.

9.1.1.1 Oracle Data Integrator Project Components

The following components are stored into a project. The 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. Sub-folders can be inserted into folders. Folders contain Packages, Interfaces and Procedure. Packages The package is the largest unit of execution in Oracle Data Integrator. 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 interfaces, procedure or variable. See Chapter 10, Working with Packages for more information on packages. 9-2 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator Interface An interface is a reusable dataflow. It is set of declarative rules that describe the loading of a datastore or a temporary target structure from one or more source datastores. See Chapter 11, Working with Integration Interfaces for more information on interfaces. Procedure A Procedure is a reusable component that groups a sequence of operations that do not fit in the interface concept. Examples of procedures: ■ wait and unzip a file ■ send a batch of files via FTP ■ receive emails ■ purge a database Variable A variables value is stored in Oracle Data Integrator. This value may change during the execution. Sequence A sequence is an variable automatically incremented when used. Between two uses the value is persistent. User Functions User functions enable to define customized functions or functions aliases, for which you will define technology-dependant implementations. They are usable in the interfaces and procedures. See Chapter 12, Working with Procedures, Variables, Sequences, and User Functions for more information about the components described above. 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. Marker Component of a project may be flagged in order to reflect a methodology or organization. Flags are defined using the markers. These markers are organized into groups, and can be applied to most objects in a project. See Chapter 17, Organizing and Documenting your Work for more information on markers. Scenario When a package, interface, procedure or variable component is finished, it is compiled in a scenario. A scenario is the execution unit for production. Scenarios can be scheduled for automated execution. See Chapter 13, Working with Scenarios for more information on scenarios.