Skip Navigation Links | |
Exit Print View | |
Migrating from eTL to Oracle Java CAPS Data Integrator Java CAPS Documentation |
Migrating From eTL to Oracle Java CAPS Data Integrator
About Migration to Oracle Java CAPS Data Integrator
About Using Migrated eTL Components in Java CAPS 6
Uploading the eTLMigrationTool SAR File to a Repository
To Upload the eTLMigrationTool SAR File
Importing eTL Projects Into Java CAPS 6
Building Data Integrator Projects
To Build a Data Integrator Project
Creating, Configuring, and Building BPEL 2.0 Modules for Data Integrator
To Use the Data Integrator Web Service in a BPEL 2.0 Module
Using Data Integrator Components as JBI Modules in Composite Applications
This topic provides instructions on customizing a CAPS repository-based BPEL 1.0 project so as to use an eTL collaboration from a Data Integrator project. Typically, such projects include eTL components that have been migrated to Java CAPS 6 Data Integrator projects.
Note - JAR files created from imported eTL projects are saved in the location JavaCAPS6\.netbeans\caps\eTL\Imported Projects\projname.
In this procedure, you will import the Data Integrator WSDL file into the CAPS repository-based project. Then, in the CAPS project and corresponding environment, you will: Find instances of the 5.1.x eTL collaboration and substitute the “execute” node from the imported WSDL; create appropriate connections and mappings; extend the project's connectivity map and environment with a JBI bridge, and create a new deployment profile.
Before You Begin
If necessary, start the CAPS repository, start the NetBeans IDE, and use Tools -> CAPS Repository -> Connect to connect to the repository.
Tip - If the installation defaults were retained, the Login ID is admin and the Password is adminadmin. If a repository is connected, the Projects window contains a top-level node labeled CAPS Library Components and the Services window contains a top-level node labeled CAPS Environments.
If you have not already built the Data Integrator project, do so now. If necessary, see Building Data Integrator Projects.
In the CAPS project folder, the project tree displays a new web service node corresponding to the eInsight (BPEL) engine.
The Business Process Editor (also called the BPEL 1.0 Editor) displays the uncustomized business process.
After you have restored all business process connections and mappings, you can close all instances of the BPEL 1.0 Editor.
The Connectivity Map Editor displays the unbridged connectivity map.
After you have substituted JBI Bridge components for eTL collaborations in all connectivity maps that require it, you can close all instances of the Connectivity Map Editor.
If any components do not map, double-check the environment to be sure that all necessary external systems have been defined and configured properly.
Next Steps
After the CAPS deployment profile is complete, you can use the corresponding EAR file in a composite application.