These release notes cover release information for Version 3.4.0 of the IBM(R) WebSphere(R) Business Integration Adapter for Web Services. These release notes contain the following sections:
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. Click the product you are interested in; if flashes are available, they are located in Self help > Solve a problem > Flashes (Alerts).
This release supports JDK 1.4.2, and includes the following new features and improvements:
This version of the adapter supports bidirectional (bi-di) languages.
Refer to the Adapter for Web Services User Guide for detailed information about the adapter and the new features.
Between release 3.3.0 and 3.4.0, the following problems, based on customer-reported cases, were fixed.
Tracking number |
Description |
28828 | The connector fails when instantiating the protocol configuration meta-object that contains required attributes. |
37217 | The SOAP data handler does not populate business objects with elements having attributes and no children. |
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 System Installation Guide for UNIX or for Windows for more information. This guide includes general migration, upgrade, and configuration information.
For hardware and software requirements and configuration information specific to this adapter, refer to the Adapter for Web Services User Guide.
Make sure that you run this version of the adapter with WebSphere Business Integration Adapters run-time version 1.8.0 or later.
The WebSphere Business Integration Adapters API .jar files and the associated scripts (CWConnEnv.bat and CWODAEnv.bat for Windows(R); CWConnEnv.sh and CWODAEnv.sh for UNIX platforms) are installed by the WebSphere Business Integration Adapters API. Before installing the adapter, make sure that the WebSphere Business Integration Adapters run time is installed. If the version is not 1.8.0 or later, you must download the latest API. This section provides instructions for verifying the API version, downloading the latest version, and enabling the adapter to run on various versions of InterChange Server and Adapter Development Kit (ADK).
To check the version of the run time, locate the manifest file (ProductDir\lib\WBIA.jar) and open it in a suitable Java JAR editor. Look for the following lines:
Implementation-Title: "CWConnectorAPI"
Implementation-Version: 1.8.0
The line Implementation-version indicates the installed version of the API. If the version is not 1.8.0 or later, you must download the latest run time.
To download the latest version of the run time:
After you download and install the run time, you should see the following files:
lib\WBIA.jar
bin\CWConnEnv.bat (Windows)
bin/CWConnEnv.sh (UNIX)
bin\CWODAEnv.bat (Windows)
bin/CWODAEnv.sh (UNIX)
connectors\messages\CwConnectorAgentMessages.txt
This adapter runs only on the current Adapter Framework, version 2.6.0, which handles InterChange Server versions 4.2.2 and 4.3.0.
The following problems have been found in this release:
Tracking number |
Description |
59634 | The Web Services Adapter cannot generate a response to synchronous listener requests that use non-TLOs (top-level business objects). |
59584 | The Web Services Adapter cannot send HTTP(S) requests to URLs that contain non-English characters when destinations URLs are specified in the non-encoded form. As a workaround, use encoded URLs. |
59428 | The Web Services Description Language (WSDL) ODA cannot access WSDL files
through URLs that contain non-English characters when destination URLs
are specified in the non-encoded form. However, the WSDL ODA can successfully
process files with the local paths containing international characters.As
a workaround, you should use an encoded URL, or save the WSDL file to the
local storage and use the local path instead of the HTTP URL. |
23993 |
When the WSDL ODA encounters multiple inline schemas that import each other without providing schema locations, it logs warnings or errors; however, the business objects are generated properly. To work around this, separate each schema into an individual file and update the imports/includes to contain the appropriate file locations. Import these individual schema files into the WSDL document using an import statement with the appropriate file locations. |
24662 |
When WebSphere MQ 5.3 CSD03 is used as the JMS provider, the adapter's JMS listener cannot read message bodies after moving the message from the input queue to the in-progress queue. This is a problem with the WebSphere MQ application. |
N/A | In the XML ODA, bi-di characters are not supported as part of business object and business object attribute names. Consequently, after a business object template based on the XML/XSD files with attribute/element names having bi-di characters is generated, you must rename all business object names and attribute names that include non-Latin characters, so that they contain only Latin characters. |
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 Information Centers:
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.