These release notes cover release information for WebSphere Business Integration Adapters, version 2.4.0, for AIX. They contain the following sections:
| New in this release | Installation, migration, upgrade, configuration |
| Product fix history | Known problems and workarounds |
| Hardware and software requirements | Documentation |
Note: Important information about this product may be available in Technical Support Flashes issued after these release notes were published. These can be found on the WebSphere Business Integration support Web site, http://www.ibm.com/websphere/integration/wbiserver/support. Select the component area of interest and search the flashes section.
This section lists the new features and improvements made in this release.
Between releases 2.3.1 and 2.4.0, the following CRs, based on customer-reported cases, were fixed.
| Tracking number |
Description |
| 23373 | Running connectors built with version 2.1 of Connector Development Kit (CDK) with the 2.3.1 CDK build returned run-time errors. |
| 23374 | Running connectors built with version 2.0 of Connector Development Kit (CDK) with the 2.3.1 CDK build returned run-time errors. |
| 23694 | A new method, setEventStatus, has
been added to CWConnectorEventStore. This is an alternate to the
existing setEventStoreStatus method call. The setEventStoreStatus
has been deprecated.
A new signature has been added to the getBO method of the CWConnectorEventStore class. This takes in a status parameter, and the status of the doVerbFor call in the getBO method will be returned in this parameter. The pollForEvents method in CWConnectorAgent has been further modularized. There is a new method getEventStore which gets the event store. The getBO method call can be overridden by the adapter. Fixed in 1.6.0. |
| 24108 | Running connectors built with version 2.2 of Connector Development Kit (CDK) with the 2.3.1 CDK build returned run-time errors. |
| 24230 | When using getdoubleValue(int i) or getdoubleValue(String str) from the CWConnectorBusObj class to retrieve a double from an attribute, if the value is a real double, such as 100,23, the method call is successful. If the value in the attribute is 100,00 or 100, the error "java.lang.ClassCastException: java.lang.Long" is returned. Fixed in 1.4.3. |
| 24699 | You were unable to pass a class name and BOPrefix in the data handler methods of the API. New methods have been added to handle Reader, Stream, and ByteArrays in the CWConnectorUtil class of the API. Fixed in 1.6.0. |
| 25364 | The Adapter Framework now uses the IBM ORB. CWConnEnv.bat, CWODAEnv.bat, CWODAEnv.sh, and CWConnEnv.sh have been changed to accommodate this move. Also, a new directory structure %INSTALL_DIR%\jre\ext has been introduced, so the scripts have been modified to accommodate this change as well. Fixed in 1.6.0. |
| 27592 | OSADDR and OAHOST were not part of JAVA_PROPERTY_FLAGS in the CWConnEnv.sh script. This prevented connectors running on different subnets from connecting with InterChange Server. These have been added.Fixed in 1.6.0. |
| 27718 | printStackTrace calls in the API were slowing the performance of the adapter for JDBC. Now, when catching the exception, the printStackTrace method is called only if the trace level for the adapter is set to 5. Fixed in 1.5.1. |
| 29263 | Error messages were logged for the methods in CWConnectorBusObj. This caused e-mail messages to be sent to the user. Some of these error messages have been removed. Fixed in 1.6.0. |
| 30086 | The getintValue and setintValue methods of the CWConnectorBusObj class were not localized. Fixed in 1.6.0. |
| Tracking number |
Description |
| 15011, 17268 | The third-party installation product did not halt an installation when not enough space was available. This has been fixed. |
| 11600 | Initial startup of Installer was slow during the initialization of a Java Virtual Machine (JVM). |
| 24023 | After an installation or
uninstallation, you saw the following warning in the console: Warning: Name: scrollbar This warning had no impact on the success of the installation or uninstallation. |
Hardware and software requirements are included in the product documentation. See Installation, migration, upgrade, and configuration information for links to those guides.
Whether you are installing the software from the CD or downloading it from Passport Advantage and installing it from a local directory, refer to the appropriate guide:
These guides also include general migration, upgrade, and configuration information.
Migration note
To allow a customer-created adapter from a previous release of Adapter Framework to function properly with this release, you must change the start scripts for both the connector and ODA. Two new environment variables have been introduced, CWJAVA and JRE_EXT_DIRS, to specify the location of the Java command and the Java run-time environment, respectively.
The new connector JVM command line looks similar to the following (changes highlighted in bold):
exec ${CWJAVA} ${JVM_FLAGS} -Djava.library.path=${LD_LIBRARY_PATH} -Djava.ext.dirs=${JRE_EXT_DIRS} -classpath ${CLASSPATH} AppEndWrapper ${CONNECTOR_TYPE}${CONNECTOR_AGENT} -n${CONNAME}Connector -s${SERVER} ${CON_START_OPTIONS} $3 $4 $5 $6 $7 $8 $9
The new ODA JVM command line looks similar to the following (changes highlighted in bold):
${CWJAVA} ${JVM_FLAGS} ${ORB_DEP} -Djava.ext.dirs=${JRE_EXT_DIRS} -classpath ${CWCLASSES} com.crossworlds.ODKInfrastructure.${CONNECTION} -l${AGENTNAME} -c${AGENTCLASS}
Adapter for CORBA installation note
If you install the adapter for CORBA, be sure to read the adapter release notes for additional information about prerequisite software.
The following problems have been found in this release:
| Tracking number |
Problem |
| 23482 |
Due to a WebSphere MQ limitation, adapters cannot write more than 100 MB of XML message text into an MQ queue for processing. This problem occurs when JMS is the transport and either WMQI or WAS is the integration broker. The adapter run time converts business objects into XML messages, which can become very large. Workaround: Avoid creating more than 25000 child objects per business object. |
| 23699 |
In a heavily stressed AIX 5.3 platform environment (running adapters with transport = JMS; broker = WMQI or WAS; a large number of child business objects; business object sizes larger than 1 MB; and concurrent consume sessions greater than 1), you may observe an OutOfMemory error after 10 to 12 hours of continuously running a connector agent. Workaround: Maintain concurrent sessions at one session. |
| 29249 | Business object attributes set to
zero can cause a parser error. The error returned is
"org.xml.sax.SAXParseException: An invalid XML character (Unicode:
0x0) was found in the element."
Workaround: Do not assign a hex 00 as the value of a business object attribute. Initialize business object fields to either an empty string or blanks. |
| 29420, 30721 | An adapter script change can improve the performance of an adapter. The JVM arguments contain a -mx option (Max heap size). Adding the -ms option (Min heap size) and setting its value to half of the maximum heap size will improve performance. Edit the adapterEnv.sh file located in the /bin directory. Locate the line that contains "JVM_ARGS=" and add the -ms option, for example, JVM_ARGS="-Xmx512m -Xms256m". |
| 31023 | If you already have WebSphere
Business Integration Adapters release 2.3 installed, and then
install WebSphere Business Integration Adapter Framework, 2.4, you
may experience a Java core dump error when running an adapter or an
ODA.
Workaround: Save your required adapter(s) to a temporary location, and then uninstall the WebSphere Business Integration Adapters release 2.3. You can then install Adapter Framework 2.4 and copy over your required adapter(s). |
| Tracking number |
Problem |
| 23778 | The title text on the Language Selection panel might be truncated depending on the language locale you choose. The Language Selection dialog cannot be resized. |
| 29755 |
The installation fails if you select an installation location that contains double-byte characters in the directory name. Workaround: Install in a path that contains no double-byte characters. |
| 31633 | A connector_manager_adapter script is generated by the installer program. The script references adapterEnv.sh, which was introduced with version 2.4.0 of Adapter Framework. If you are running an older version of Adapter Framework, adapterEnv is not available. To run this version of the adapter with a pre-2.4.0 version of the framework, change the reference from adapterEnv.sh to CWSharedEnv.sh in the connector_manager_adapter script. |
Product documentation is not included as part of the product package, either by CD or by electronic product distribution. The documentation for this product can be found in the following InfoCenters:
http://www.ibm.com/websphere/integration/wicserver/infocenter
http://www.ibm.com/websphere/integration/wbicollaborations/infocenter (for collaborations)
http://www.ibm.com/websphere/integration/wbiadapters/infocenter
To obtain the product documentation, visit the Web site and download the current documentation set for the release that you are using. Follow the instructions provided on the InfoCenter page to complete the installation.