Fix Pack Notes for
WebSphere Business Integration Adapter Framework Version 2.6.0.2

The patch notes contain the following sections:

COMPLETED CHANGE REQUESTS

UPGRADE INSTRUCTIONS

ADDITIONAL DISCUSSION

UNINSTALL INSTRUCTIONS

 

COMPLETED CHANGE REQUESTS

This patch contains fixes for the following customer reported and internally discovered issues.

Problem tracking numbers

As of Version

Problem

61985

2.6.0.2

Connector_manager -stopgraceful SAP does not work as documented

44949

2.6.0.2

2.6 Adapter runtime can't accept a cfg file that has a verion of 4.4.0

60685

2.6.0.2

WBIA Framework 2.4 recognizes "mrm" not "MRM"

43926

2.6.0.2

Connector and tool require to put CHANNEL and PORT when using local MQ binding

37590

2.6.0.2

2.4.0 framework fails converting XML message

61281

2.6.0.2

SAP adapter 2.6 is not putting invalid message to Fault queue.

61176

2.6.0.2

Error throw out when HTTPAdapter1.2.0.1IF poll using JMS as DeliveryTransport

44904

2.6.0.2

JMS transported adapter can't get the response in Sync model

44363

2.6.0.1

When DEE property is set to true, WSDL binding information is missing in the JMS message head

44635

2.6.0.1

pollForEvents method of adapter does not work in MAIN_SINGLE_THREADED mode

59316

2.6.0.1

Provide built-in message audit and tracking functionality - for Adapter Framework

58998

2.6.0.1

Security exits/JMS transport not handled in the adapter

59346

2.6.0.1

Wrong com.crossworlds.DataHandlers.cwxml generated by framework

44746

2.6.0.1

Print the adapter framework version

 

UPGRADE INSTRUCTIONS:

To perform an upgrade to this version of the WBI Adapter Framework:

1.      This is a fixpack to be applied to WBI Adapter Framework version 2.6.0. 

2.      Extract everything from the .tar or .zip file associated with your platform. If the extracted files are .tar files or .zip files, then extract everything from them also.

3.      Back up the files referenced in the table below according to your platform.

4.      Apply the changes prescribed in the table below.

After backing up the listed files, add, replace, or remove the following files and directories as indicated:

Platform [Win32;Solaris;AIX;HP_UX;Linux]

Add / Replace / Remove

File (Starting from WBIA installation directory)

Win32:Solaris:AIX:HP_UX :Linux

Replace

wbiart/wbiart.jar

Win32:Solaris:AIX:HP_UX :Linux

Replace

messages/WBIAdapterRuntime.txt

Win32:Solaris:AIX:HP_UX :Linux

Replace

5724G92J020600.sys

Prerequisites

You must have WBI Adapter Framework version 2.6.0 installed in order to install this fixpack.

 

ADDITIONAL DISCUSSION

1.       To enable the MQ Security Exit(CR58998) for the adapter:

- Launch Connector Configurator then set the type of 'DeliveryTransport' to 'JMS'

- Input the class name of MQ Security Exit as the last element by following format, 'queue_manager_name:channel_name:host_name:port_number:mq_security_exit_name'

- Put the class of MQ Security Exit in the library path or extend path of the adapter

- When the adapter is launched, the MQ Security Exit will be invoked.  If the class of MQ Security Exit can not be found, this feature will be treated as disabled.

2.       To use the BO trace (CR59316) feature:

1)     Enable 'BOTrace' property:

- ICS user or standalone broker user may use '-x' parameter in agent start script to configure 'BOTrace' property if Connector Configurator's patch is not available, for example '-xBOTrace=Full'.

- If Connector Configurator's patch is available, the user can configure 'BOTrace' property by Connector Configurator.   

2)     The options of 'BOTrace' value are as following:

When 'AgentTraceLevel' is 5, the property 'BOTrace' is not available.

When 'AgentTraceLevel' is lower than 5:

- Set 'BOTrace' to 'Full' to dump all BO's attributes.

- Set 'BOTrace' to 'Keys' to dump only BO's keys.

- Set 'BOTrace' to 'None' to disable BO's attributes dumping. 

3.       To support no namespace BO(CR37590)

If the “no” option was not available for property XMLNameSpaceFormat in Connector Configurator (It is supposed to be added in WebSphere Business Integration (WBI) Toolset version 4.3.0.1), user should edit the Connector Configuration file manually. 

- Open the Connector Configuration file by text editor

- Locate the “XMLNameSpaceFormat” property by search, here is a sample

<tns:property>

<tns:name>XMLNameSpaceFormat</tns:name>

<tns:type>String</tns:type>

<tns:subtype></tns:subtype>

<tns:value xml:space="preserve">short</tns:value>

<tns:description>Supports short and long name spaces in the bo's xml doc on the wire.</tns:description>

- Replace the value “short” or “long” by “no”.  As

<tns:property>

<tns:name>XMLNameSpaceFormat</tns:name>

<tns:type>String</tns:type>

<tns:subtype></tns:subtype>

<tns:value xml:space="preserve">no</tns:value>

<tns:description>Supports short and long name spaces in the bo's xml doc on the wire.</tns:description>

4.       AIX 5.3 supporting:

WebSphere Business Integration Adapter Framework supports AIX 5.3 since version 2.6.0.2.

Please refer to Installer technical notes for how to install Adapter Framework 2.6.0.x on AIX 5.3.

http://www-1.ibm.com/support/docview.wss?rs=695&context=SSMKUK&dc=DB520&uid=swg21201415&loc=en_US&cs=utf-8&lang=en

 

3. UNINSTALL INSTRUCTIONS

1.       To uninstall this fix pack, replace the new files with the files backed-up in step 3 of the upgrade instructions.

 

© 2005 IBM Corporation. Proprietary and Confidential. All Rights Reserved.
IBM WebSphere® Business Integration