Known Issues for the Data Integrator Service Engine (Sun Java Composite Application Platform Suite 6.2 Release Notes)

Sun Java Composite Application Platform Suite 6.2 Release Notes

Known Issues for the Data Integrator Service Engine

The following are known issues for the Sun Data Integrator Service Engine:

There is a compatibility issue with existing eTL/Data Integrator projects (Modern) from previous Java CAPS releases that are migrated into Java CAPS 6.2. To resolve this issue, you need to update the build-impl.xml file for each project. The file is located in ProjectHome/nbproject. Add the following two entries for each project:
include name="org-openide-io.jar"/ include name="org.openide-explorer.jar"/

CR 6681744

Importing eTL 5.1.x projects into Java CAPS 6 using a command line results in an exception.

When importing 5.1.x projects, set the NB_HOME, DB_DRIVERS_HOME, ETL_MIGRATION_CLASSPATH and DB_DRIVER_PATH variables as shown below. Exceptions still persist if the eTL collaborations contain database tables. There are no issues when flat files are used. To work around the database table issue, restart the repository, and then rerun the import command. Alternatively, import the project using the NetBeans GUI.

set NB_HOME=C:/JavaCAPS6/netbeans 
set DB_DRIVERS_HOME=C:/JavaCAPS6/.netbeans/caps/modules/ext  
set ETL_MIGRATION_CLASSPATH=
   %NB_HOME%/ide9/modules/org-netbeans-modules-project-ant.jar; 

%NB_HOME%/ide9/modules/org-netbeans-modules-projectuiapi.jar; 
%NB_HOME%/ide9/modules/org-netbeans-modules-projectapi.jar; 
%NB_HOME%/platform8\lib\org-openide-util.jar;
%NB_HOME%/soa2/modules/org-netbeans-modules-etl-editor.jar; 
%NB_HOME%/soa2/modules/org-netbeans-modules-etl-project.jar; 
%NB_HOME%/platform8\modules\org-openide-dialogs.jar; 
%NB_HOME%/platform8\core\org-openide-filesystems.jar; 
%NB_HOME%/ide9/modules/org-netbeans-modules-db.jar; 
%NB_HOME%/platform8\modules\org-openide-nodes.jar; 
%NB_HOME%/platform8\modules\org-openide-text.jar; 
%NB_HOME%/xml2\modules\org-netbeans-modules-xml-validation.jar; 
%NB_HOME%/ide9\modules\org-netbeans-api-xml.jar; 
%NB_HOME%/soa2\modules\org-netbeans-modules-soa-ui.jar; 
%NB_HOME%/\platform8\modules\org-openide-loaders.jar; 
%NB_HOME%/platform8\modules\org-openide-windows.jar; 
%NB_HOME%/platform8\modules\org-openide-awt.jar; 
%NB_HOME%/xml2\modules\org-netbeans-modules-xml-xam-ui.jar;
%NB_HOME%/platform8\modules\org-openide-options.jar;  

set DB_DRIVER_PATH=%DB_DRIVERS_HOME%/db2adapter/db2builder.jar; 
%DB_DRIVERS_HOME%/stc/ewaycommon/com.stc.ewayrepositoryapi.jar; 
%DB_DRIVERS_HOME%/../com-stc-bpms-common.jar;
%DB_DRIVERS_HOME%/../com-stc-log4j.jar; 
%DB_DRIVERS_HOME%/otd/com.stc.otd.fwbuildapi.jar; 
%DB_DRIVERS_HOME%/stc/ewaycommon/com.stc.ewayutils.jar; 
%DB_DRIVERS_HOME%\oracleadapter\oraclebuilder.jar; 
%DB_DRIVERS_HOME%/sqlserveradapter/sqlserverbuilder.jar; 
%DB_DRIVERS_HOME%/sybaseadapter/sybasebuilder.jar;

CR 6694617

Importing eTL 5.1.x projects with fixed width tables fails at runtime. Runtime test resulted in a java.sgl.SQLException.

To work around this issue, check whether the execution of the imported eTL project fails due to the exception java.sql.SQLException: LOADTYPE property required in organization clause. If so, open the ETL Collaboration file and verify that the ORGPROP_LOADTYPE attribute is listed for each flat file table that is used. If the ORGPROP_LOADTYPE attribute is missing, then manually add it, save the Collaboration, and then rerun the project. For example:
<attr name="ORGPROP_LOADTYPE" type="java.lang.String" value="FIXEDWIDTH" /> <attr name="ORGPROP_LOADTYPE" type="java.lang.String" value="DELIMITED" />
CR 6705843

For a 5.1.x eTL project that was upgraded using the eTL Migration Tool and modified to use the JBI Bridge, command line codegen fails to create the EAR file.

To work around this issue, use the NetBeans GUI to build and deploy migrated Data Integrator projects.
CR 6707522

Changing the sun-etl-engine setting in the Loggers properties does not change log and message levels in the server log file.
CR 6669876

If you import a 5.1.3 eTL project into a Java CAPS 6.x environment, modify the ETL Collaboration, and then re-import the project, the ETL Collaboration does not refresh. In other words, you still see the changes you made earlier, though they should have been overwritten by the import process.

To work around this, do one of the following:
- Restart NetBeans. When you open the ETL Collaboration, it will be the original, imported version.
- Before you re-import the project, delete the ETL module from the Project window and then manually delete the directory JavaCAPSHome/.netbeans/caps/eTL/Imported Projects/ProjectName.