Migrating From eTL to Sun Data Integrator

The topics listed here provide information and procedures for migrating projects from Sun SeeBeyond eTL Integrator 5.1.x (eTL 5.1.x) to Sun Data Integrator in Java Composite Application Platform System 6 (Java CAPS 6), and integrating them with other Java CAPS components and projects. These topics do not cover information on eTL, Java CAPS generally, or detailed instructions for designing projects using Data Integrator, which can be found elsewhere.

If you have any questions or problems, see the Java CAPS web site at http://goldstar.stc.com/support.

At a Glance

Once you are familiar with Java CAPS 6, you need little more than a reminder of the following key pieces of information, each covered in greater detail in the presented topics.

1. Initial migration from eTL to Data Integrator is done on a project-by-project basis after using the Uploader to install the eTLMigrationTool SAR file to the Repository.

2. To import an eTL project into Java CAPS 6, use NetBeans menu item Tools -> CAPS Repository -> Import Project and select its ZIP file. This creates two project folders: A Data Integrator (DI) project containing migrated eTL collaborations, and a CAPS Repository-based project containing repository-based artifacts.

3. After an eTL project is imported, you can use it in several different ways:

   • (JBI only; simple) Build the DI project and use its JAR file as a JBI module in a composite application project.

   • (JBI only; BPEL module) Build the DI project, use its WSDL as a partner role in a new BPEL process, and use the BPEL module's JAR file as a JBI module in a composite application project.

   • (Repository-based, with JBI Bridge) Build the DI project, import its WSDL into the CAPS Repository-based project and substitute it in Business Processes that reference eTL Collaborations, add and connect a JBI Bridge component into each Connectivity Map and a JBI external system into each CAPS Environment, create and build a deployment profile to generate an EAR file, and then use the repository-based project's EAR file as a JBI module in a composite application project.

What You Need to Know

The following topics provide information on what you should know about migrating eTL projects and using them in Java CAPS 6.

• About eTL Project Migration

• About Using Migrated eTL Components in Java CAPS 6

• About Runtime eTL Components

What You Need to Do

The following topics provide instructions on migrating eTL components and reusing them in Data Integrator.

• Uploading the eTLMigrationTool SAR File to a Repository

• Importing eTL Projects Into Java CAPS 6

• Using Migrated Data Integrator Components in a Composite Application

  Simplest case: No JBI bridge; only one or two eTL collaborations

  1. Building Data Integrator Projects

  2. Using Data Integrator Components as JBI Modules in Composite Applications

  BPEL 2.0 case: No JBI bridge; several eTL collaborations orchestrated by BPEL 2.0 module

  1. Building Data Integrator Projects

  2. Creating, Configuring, and Building BPEL 2.0 Modules for Data Integrator

  3. Using Data Integrator Components as JBI Modules in Composite Applications

  BPEL 1.0 case (repository-based): Using a JBI Bridge

  1. Building Data Integrator Projects

  2. Configuring Repository-based Projects to Use Data Integrator

  3. Using Data Integrator Components as JBI Modules in Composite Applications

More Information

For additional information about Data Integrator, see the following.

• Designing Data Integrator Projects