| Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components | |
| Close Print View | |
| Upgrading: About eTL Project Migration |
|
Migrating From eTL to Sun Data Integrator
About Migration to Sun 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
Configuring Repository-based Projects to Use Data Integrator
To Use the Data Integrator Web Service in a BPEL 1.0 Module
Using Data Integrator Components as JBI Modules in Composite Applications
In Java CAPS 5.1.x, projects are saved as ZIP files that can be imported into Java CAPS 6. Individual eTL components can only be used in Data Integrator after the entire project has been imported.
Because Java CAPS 5.1.x is exclusively repository-based, you must install and start a
repository before you can migrate eTL projects into Java CAPS 6. Also, a
special tool called the eTL Migration Tool (eTLMigrationTool.sar) must be uploaded to the repository. If
this tool has not been uploaded, then 5.1.x projects that contain eTL components
cannot be imported into Java CAPS 6.
Importing a 5.1.x project that contains eTL components has the following results.
A Data Integrator project is created, containing the eTL collaborations.
A Repository-based CAPS project is created, containing the other CAPS 5.1.x project artifacts.
If the project contained one or more CAPS environments, their components are added to the Services window, under the CAPS Environments folder.