About Migration to Sun Data Integrator

The information presented here explains only the concepts involved in migrating from eTL to Data Integrator. Task-based step-by-step migration procedures are found in other topics.

In Java CAPS 6, the product previously known as Sun SeeBeyond eTL Studio has been superseded by Sun Data Integrator. Although the functional capabilities and much of the look-and-feel has been retained, the architecture has changed. Accordingly, a tool is provided for migrating eTL 5.1.x projects to Java CAPS 6, and components migrated from eTL are used in different ways in Data Integrator and composite applications.

About eTL Project Migration

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.

About Using Migrated eTL Components in Java CAPS 6

As with all Java CAPS 6 projects, the Data Integrator project must be built, creating a WSDL file: a file that describes the web services provided by the project.

For Data Integrator projects created from imported eTL projects, the WSDL files created by building the projects are located in JavaCAPS6.netbeans\caps\eTL\Imported Projects\.

For a composite application project to be usable as an executable Service Assembly, it must include as one of its JBI modules one or more of the following files.

• A project JAR file, in the case of a purely JBI-based project. This type of composite application could include either no BPEL module or one or more BPEL 2.0 modules.

• A project EAR file, in the case of a repository-based CAPS project. The CAPS project must be updated to include a JBI bridge, and then rebuilt. Typically, this type of composite application reuses BPEL 1.0 business processes in the repository-based CAPS project.

JBI modules can be added to the composite application either by dragging them into the CASA Editor or by right-clicking the composite application's JBI Modules folder in the project tree.

About Runtime eTL Components

For any project that uses repository-based CAPS components in conjunction with a JBI bridge, the CAPS environment components must be properly configured to reflect the runtime environment. These runtime components are located in the NetBeans Services window, under Servers -> CAPS Environments.

For any Data Integrator project that uses a flatfile type of database (also called a Data Mashup database), the properties of the sun-etl-engine must be properly configured. This runtime component is located in the Services window, under Servers -> GlassFish V2 -> JBI -> Service Engines.

For any Data Integrator project that uses a relational database, the database resources and connection pools must be properly configured. This is accomplished using the Admin Console application, under Common Tasks -> Resources -> Connectors -> Connector Resources | Connection Pools.