Patch Notes for

Version 1.6.6 of the IBM WebSphere Business

Integration Data Handlers

The patch note contains the following sections:

DATA HANDLER REVISIONS

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

Available as of Version	CR Number	Data Handler	Description
1.6.6	13696	xml	When transforming from XML to BO, the XML DataHandler now populates the entire Doctype, rather than just the Name of the Doctype. The entire text between the < and > characters for the Doctype is read: For example, if this was the Doctype tag: <!DOCTYPE Customer SYSTEM "cust.dtd"> The attrivute value would be: DOCTYPE Customer SYSTEM "cust.dtd"
1.6.5	16954	tpi-rnif	A new meta-object attribute "BOsWithLongNames" is added to allow tpi_rnif data handler to process documents with element or attribute names greater than 80 characters. For more configuration details, please see the section "Configuring the MO_DataHandler_RNET_for80CharRemedy Business Object" in the "WebSphere Business Integration for Electronics Solution Implementation Guide" document.
1.6.4	15653	xml	The enhancement for CR 15350 changed the default behavior of the data handler to fail if either an xml element or an attribute does not have a corresponding business object attribute. This caused the data handler to fail when processing attributes with a fixed value or which have a default value, as such attributes don't have a corresponding business object attribute. To support these type of xml attributes and at the same time make the data handler configurable to ignore undefined attributes independent of undefined xml elements, a new property, IgnoreUndefinedAttributes, has been added to the XML configuration meta-object. This property will have a default value set to true, so that the data handler will now ignore, generating a warning, if an xml attribute does not have a corresponding business object attribute. This default behavior was incorrectly stated as inconsistent in CR 15350. The user can now configure the data handler to ignore or fail on undefined xml elements or attributes, independent of each other, by making use of the IgnoreUndefinedElements and IgnoreUndefinedAttributes properties.
1.6.4	15611	xml	XML DataHandler loses data for nested wrappers
1.6.4	14059	swift	This patch includes the swift datahandler enhancement to support ISO 7775 <-> ISO 15022 ASBO mapping available in the 1.3.0 version of the SWIFT Connector.
1.6.3	15156	xml	During xml document to business object conversion, the data handler may produce incorrect number of child objects.
1.6.3	15350	xml	The enhancement for CR13906, ignore elements that are being read from an xml input stream, but do not exist in the business object definition, did not account for xml attributes that do not exist in the business object definition. If the IgnoreUndefinedElements xml meta-object attribute is set to true, then the data handler will now ignore both elements and attributes within an xml document that do not have corresponding attributes in the business object. Additionally, when IgnoreUndefinedElements xml meta-object attribute is set to false, the data handler will now fail if either an xml element or an attribute does not have a corresponding business object attribute. The previous behavior was inconsistent in that missing elements would cause the document to fail while missing attributes would simply generate a warning in the log.
1.6.2	15272	xml	When converting an xml document to a business object, the attribute corresponding to the doctype is populated with only the business object name. Yet when converting from business object to xml the data handler requires the doctype attribute's value to include "DOCTYPE". Thus making it impossible to convert from xml to business object then back to xml without manipulating the business object. The data handler has now been updated to include "DOCTYPE" in the doctype attribute.
1.6.1		swift	Support a limited set of SWIFT message parsing at the sub-field level. This complements an updated release of the SWIFT Adapter v1.3.0.
1.6.1	14874	xml	The enhancement for CR13906, ignore elements that are being read from an xml input stream, but do not exist in the business object definition, did not accommodate consecutive elements that are not present in the business object.

UPGRADE INSTRUCTIONS

To perform an upgrade to this version of the Data Handler:

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

For Version

Platform
Add / Replace / Remove
File (Starting from %CROSSWORLDS%/$CROSSWORLDS)

All Versions

WIN/Solaris/AIX

Replace

DataHandlers\CwDataHandler.jar

1.6.4

WIN/Solaris/AIX

Replace

repository\DataHandlers\MO_DataHandler_XML.txt

For Version	Platform	Add / Replace / Remove	File (Starting from %CROSSWORLDS%/$CROSSWORLDS)
All Versions	WIN/Solaris/AIX	Replace	DataHandlers\CwDataHandler.jar
1.6.4	WIN/Solaris/AIX	Replace	repository\DataHandlers\MO_DataHandler_XML.txt