Note: The adapter documented in these release notes has not been internationalized. Do not run it against InterChange Server version 4.2.x unless you can guarantee that only ISO Latin-1 data will be processed.
The release notes contain the following sections:
Product fix history | WebSphere Business Integration Adapters API and run time |
Hardware and software requirements | Documentation updates |
Installation, migration, upgrade, and configuration information |
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.
Between releases 2.3.0 and 2.4.0, the following CRs, based on customer-reported cases, were fixed.
CR number | Description |
22225 | The XML ODA has a problem in generating correct business object definitions
for schema elements that use the same element name and element type. For
example, for the following schema definitions:
<xsd:element name="WFADOCMP" type="WFADOCMP" />no definitions are generated for element WFADOCMP because the element type is the same as the element name. Fixed in 2.4.0. |
22341 | The adapter fails to populate the meta-object with the correct message ID of the inbound message during event notification. Fixed in patch 2.3.1. |
22345 | The adapter fails to populate the meta-object with the correct priority of the inbound message during event notification. Fixed in patch 2.3.1. |
22682 | The adapter terminates when retrieving an empty message (this is expected behavior). The adapter has been enhanced so that it now reports an error but continues processing. Fixed in patch 2.3.2 |
22691 | The adapter fails to deliver a reply message to requestor after synchronously posting an event to thebroker; it reports that a reply queue is undefined. Fixed in patch 2.3.2. |
22716 | The adapter fails to properly isolate meta-data when processing simultaneous requests for the same business object. The result is that the adapter may apply a single set of meta-data to multiple requests rather than use the unqiue meta-data specified for each request. Fixed in patch 2.3.2. |
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 migration, upgrade, and configuration information.
For hardware and software requirements and configuration information specific to this adapter, refer to the Adapter for Telcordia User Guide.
Implementation-Title: "CWConnectorAPI"If the version is not 1.5.0 or later, you must download the latest WBIA run time.
Implementation-Version: 1.5.0
Implementation version indicates the current version of WBIA API.
lib\WBIA.jar
lib\WBIA\3.0.0\WBIA.jar
lib\WBIA\4.0.0\WBIA.jar
lib\WBIA\4.1.1\WBIA.jar
bin\CWConnEnv.bat (Windows)
bin/CWConnEnv.sh (UNIX)
bin\CWODAEnv.bat (Windows)
bin/CWODAEnv.sh (UNIX)
connectors\messages\CwConnectorAgentMessages.txt
set CWVERSION="4.X"UNIX: In CWConnEnv.sh, set the CWVERSION variable to 4.X.
set CWVERSION="4.X"
set CWVERSION="4.1.X"UNIX: In CWConnEnv.sh, set the CWVERSION variable to 4.1.X.
set CWVERSION="4.1.X"
set CWVERSION="4.1.X"UNIX: In bin/CWODAEnv.sh, set the CWVERSION variable to 4.1.X.
set CWVERSION="4.1.X"