IBM WebSphere Business Integration Adapter for Web Services, version 3.4.4.IF1 Notes

These notes contain the following sections:

Adapter revisions

Upgrade instructions

Adapter revisions

The following table lists the revisions made since the last release.

Adapter Version

CR number/APAR number

CR details

Description of fix done

3.4.4.IF1

CR85006/JR24391

During Business Object to SOAP payload transformation, elem_value ASI does not properly work in the SOAP Header Business Object container.

SOAP Data Handler now correctly processes headers with elem_value ASI functionality.

3.4.4

CR83289

Add support for AIX 5L 5.3 Maintenance Level 2.

Support for AIX 5L 5.3 Maintenance Level 2 has been added (on WebSphere Business Integration Adapter Framework, version 2.6.0.3 and higher)

3.4.4

CR83147/JR23228

WSDL ODA start scripts reference J2EE.jar (non-existing dependency file).

WSDL ODA starts scripts no longer reference J2EE.jar.

3.4.4

CR74364/JR22768

SOAP Data Handler sets encodingStyle attribute on encoded element level only. (Applicable to SOAP 1.1, rpc/encoded payloads only.)

Clients that are not fully compatible with SOAP 1.1 specifications might require the Body element of SOAP 1.1 messages to contain an encodingStyle attribute. In order to do that, SOAP Config MO has a new property SetEncodingOn with possible values of Element (previous behavior, default) and Body. Please note that the SOAP Data Handler will not explicitly disable encoding on the child elements when the encodingStyle attribute is set on the Body element, so compliance with SOAP 1.1 specifications will be Business Object dependent.

3.4.4

CR73942/JR22655

The Adapter for Web Services ignores the elementFormDefault attribute in the Web Service Definition Language (WSDL) files and therefore does not generate the conforming SOAP request messages when elementFormDefault has a value of "qualified".

Fixed.

3.4.4

CR74500/JR22989

Asynchronous outbound requests do not fail when there is a JMS provider error.

Fixed.

3.4.4

CR74502/JR22989

When a non-recoverable JMS provider failure occurs, the adapter does not clean up resources and therefore fails to reconnect.

Fixed.

3.4.4

CR83174/JR23062

The SOAP Data Handler outputs empty elements during request processing.

This behavior has been corrected to be consistent with previous versions of the data handler. Empty tags will not be generated for elements with null values, except in the case of a nillable element.

3.4.4

CR74454/JR22924

The SOAP/JMS Handler does not terminate the adapter when JMS exceptions occur.

A new property TerminateOnJmsError, child of JNDI hierarchical property, has been introduced. Possible values are true and false (the default). If the value of the TerminateOnJmsError is set to true, the adapter terminates when irresolvable JMS-related exceptions are encountered during request processing through the SOAP/JMS handler.

3.4.4

CR67791/JR22927

During event notification, the adapter does not trace synchronous response payload.

Fixed in Trace Level 5.

3.4.4

CR59634/CR83247/JR23249

Failure in event processing of payloads resolving to Non-TLOs.

Fixed.

3.4.4

CR83266/JR22577

During synchronous request processing, a request is not failed when the adapter cannot populate the TLO response business object attribute.

Fixed.

3.4.3

CR67572

A non-recoverable error in parsing SOAP messages and XSD content in WSDL files occurs due to an incompatible version of the XML/XSD parser in the classpath.

Fixed by removing "%INSTALLEDDIR%\connectors\WebServices\dependencies\j2ee.jar"

3.4.3

CR67583/JR22528

During synchronous request processing, the adapter ignores HTTP error responses with empty payloads.

Fixed. All error responses with empty payloads will result in failure of the originating request.

3.4.3

CR71832/JR22014

SOAP/HTTP(S) listeners fail redirected HTTP(S) requests.

Problem background:

According to HTTP 1.1 specifications (http://www.w3.org/Protocols/rfc2068/rfc2068), section 5.2, the SOAP/HTTP(S) listener checks the accuracy of host and port information specified in the request with the listener's host and port information. If there is a mismatch, the listener will stop processing the request and respond with a 400 (Bad Request) status code.

Issue:

When incoming requests are being routed by an enterprise gateway system in order to hide the endpoint, the request host and port information has to be changed before being sent to the SOAP/HTTP(S) listener (the original request has the gateway host and port). In some cases, this change is not supported by the gateway or is troublesome to implement in the gateway system.

Solution:

A new SOAP/HTTP(S) listener property has been introduced to solve the above issue. Please note that using this property to disable the validation of the request host and port information, puts the SOAP/HTTP(S) listener out of compliance with HTTP 1.1 specification, section 5.2. Use of the new property should be restricted to cases where an enterprise gateway system change is undesirable.

To use this feature, add the following property to the SOAP/HTTP(S) Listener Property:

Property Name

Possible Values

HostInfoValidation

FailRequest - if the request host/port info does not match the listener host/port, the error message will be logged and the request will be failed with 400 (Bad Request) status.

LogError - if the request host/port info does not match the listener host/port info, the error message will be logged and request execution will continue.

Ignore - there will be no validation performed on the request host/port info.

Note: If the property does not exist, the SOAP/HTTP(S) listener will DEFAULT the property value to FailRequest.

3.4.3

CR71572/JR22015

Support User ID and Password authentication when establishing a connection to JMS provider.

The Adapter for Web Services now supports two new properties under the JNDI hierarchical property:
JMSProviderUserid
JMSProviderPassword.

Note: If the value of the JMSProviderUserid property is not empty, a new authentication method will be used.

3.4.3

CR71699/JR22016

The SOAP Data Handler appends a new line after the element opening tag; which is inconsistent with the new line appearance of nil elements.

Nil elements will not contain new lines after the opening tags.

Non-nil elements will behave according to the property UseNewLine of SOAP Data Handler MO. Possible values are true/false.

A value of true would add a new line after the element opening tag; false would append the element content right after the tag. The default is true for backward compatibility.

3.4.3

CR70984/JR21612

WSDL ODA does not recognize complex types derived by extensions when no additional elements are added to the extended complex type.

Fixed.

3.4.3

CR62274/JR21338

The SOAP Data Handler does not support n-cardinality SOAP Attributes on Simple Type Elements by using elem_value ASI.

Fixed.

3.4.3

CR29113/JR21611

WSDL ODA and SOAP Data Handler do not support nillable elements.

A new ASI "nillable=true" is now supported.
Nillable attributes are supported in Business Object to SOAP message transformations only.

3.4.3

CR44131

WSDL ODA fails to display an error message when it contains a NULL (0x0000) character.

Fixed.

3.4.3

CR61927/JR21187

WSDL ODA fails to resolve Business Objects types when complex types are defined in the separate inline schemas.

Fix from 3.4.1.1IF merged with 3.4.2.

3.4.2

CR61067

WSDL ODA fails to generate Business Objects when the WSDL file contains bidirectional script characters.

Fixed.

3.4.1

CR47158/JR20556

The adapter appends a new line to the beginning of the content returned from a call to a child data handler.

The SOAP Data Handler MO now supports a new property UseNewLine with possible values of true/false. A value of true would add a new line at the beginning of the result obtained from a call to a child data handler; false would append the content right after the element opening tag. The default is true for backward compatibility.

Example:

a. UseNewLine is set to true

<ParentElement>
content obtained from a child datahandler</ParentElement>

b. UseNewLine is set to false

<ParentElement>content obtained from a child datahandler</ParentElement>

3.4.1

CR59943/JR20556

The SOAP/JMS protocol handler does not fail a request that has no response within a configured ResponsetWaitTimeout value.

Fixed.

3.4.1

CR60193

The SOAP/HTTP(S) Handler ignores a synchronous response payload if HTTP header Content-Length is not specified.

Fixed.

UPGRADE INSTRUCTIONS

Add, replace, or remove the following files and directories as indicated below:


For Connector Version	Platform	Add / Replace / Remove	*File (Starting from %INSTALLEDDIR%* or $INSTALLEDDIR)**
3.4.4.IF1	WIN and UNIX	Replace the file	\DataHandlers\CwSOAPDataHandler.jar
3.4.4	WIN and UNIX	Replace the file	\DataHandlers\CwSOAPDataHandler.jar
3.4.4	WIN and UNIX	Replace the file	\connectors\WebServices\CWWebServices.jar
3.4.4	WIN and UNIX	Replace the file	\connectors\messages\WebServicesConnector.txt
3.4.4	WIN and UNIX	Replace the file	\ODA\WSDL\WSDLODA.jar
3.4.4	WIN	Replace the file	\ODA\WSDL\start_WSDLODA.bat
3.4.4	UNIX	Replace the file	\ODA\WSDL\start_WSDLODA.sh
3.4.3	WIN and UNIX	Remove the file	\connectors\WebServices\dependencies\j2ee.jar
3.4.3	WIN and UNIX	Replace the file	\connectors\WebServices\CWWebServices.jar
3.4.3	WIN and UNIX	Replace the file	\connectors\messages\WebServicesConnector.txt
3.4.3	WIN and UNIX	Replace the file	\DataHandlers\CwSOAPDataHandler.jar
3.4.3	WIN and UNIX	Replace the file	\ODA\WSDL\WSDLODA.jar
3.4.2	WIN and UNIX	Replace the file	\ODA\WSDL\WSDLODA.jar
3.4.1	WIN and UNIX	Replace the file	\connectors\WebServices\CWWebServices.jar
3.4.1	WIN and UNIX	Replace the file	\DataHandlers\CwSOAPDataHandler.jar

July 18th, 2006 4:00 PM