Readme for WBI Adapter for Web Services, version 3.4.2.2IF

The patch note contains the following sections:

CONNECTOR REVISIONS

UPGRADE INSTRUCTIONS

CONNECTOR REVISIONS

This patch contains the following revisions since the last maintenance release:

Available as of Version

CR Number/APAR#

Feature

Description

3.4.2.2IF

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, SOAP/HTTP(S) listener checks the correctness of host and port information specified in the request with host and port information of the listener itself. 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 end point, the host and port information of the request has to be changed before being sent to the SOAP/HTTP(S) listener (original request has host and port of the gateway). In some cases, such 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 host and port information of the request, 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 the cases when 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 host/port info of the request does not match the host/port info of the listener, the error message will be logged and request will be failed with 400 (Bad Request) status.

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

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

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

3.4.2.2IF

CR71572/JR22015

Support Userid/Password authentication when establishing connection to JMS provider.

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

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

3.4.2.2IF

CR71699/JR22016

The SOAP Data Handler appends new line after element opening tag; inconsistency with new line appearing for 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.

Value of true would add new line after element opening tag; false would append the element content right after the tag. Default is true for backward compatibility.

3.4.2.1IF

CR70984/JR21612

WSDL ODA does not recognize complex types derived by extensions in limited cases.

Fixed.

3.4.2.1IF

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.2.1IF

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.2.1IF

CR44131

WSDL ODA fails to display error message when it contains special characters.

Fixed.

3.4.2.1IF

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 WSDL file contains bidirectional script characters.

Fixed.

3.4.1.1IF

CR61927/JR21187

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

Fixed.

3.4.1

CR47158/JR20556

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

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

Example:

a. UseNewLine is set to true

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 configured ResponsetWaitTimeout value.

Fixed.

3.4.1

CR60193

SOAP/HTTP(S) Handler ignores 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 %CROSSWORLDS%/$CROSSWORLDS)
3.4.2.2IF	WIN & UNIX	Replace the file	%CROSSWORLDS%\DataHandlers\CwSOAPDataHandler.jar
3.4.2.2IF	WIN & UNIX	Replace the file	%CROSSWORLDS%\connectors\WebServices\CWWebServices.jar
3.4.2.2IF	WIN & UNIX	Replace the file	%CROSSWORLDS%\connectors\dependencies\WebServicesConnector.txt
3.4.2.1IF	WIN & UNIX	Replace the file	%CROSSWORLDS%\DataHandlers\CwSOAPDataHandler.jar
3.4.2.1IF	WIN & UNIX	Replace the file	%CROSSWORLDS%\ODA\WSDL\WSDLODA.jar
3.4.2	WIN & UNIX	Replace the file	%CROSSWORLDS%\ODA\WSDL\WSDLODA.jar
3.4.1.1IF	WIN & UNIX	Replace the file	%CROSSWORLDS%\ODA\WSDL\WSDLODA.jar
3.4.1	WIN & UNIX	Replace the file	%CROSSWORLDS%\connectors\WebServices\CWWebServices.jar
3.4.1	WIN & UNIX	Replace the file	%CROSSWORLDS%\DataHandlers\CwSOAPDataHandler.jar

June 30th, 2005 12:19 PM