| Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components | |
| Close Print View | |
| Upgrading: About Using Migrated eTL Components in Java CAPS 6 |
|
Migrating From eTL to Sun Data Integrator
About Migration to Sun Data Integrator
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
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.
Note - 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.