Fix
Pack Notes for
WebSphere Business Integration Adapter Framework
Version 2.6.0.4
The patch notes contain the following
sections:
This patch contains fixes for the following customer-reported and internally discovered issues and enhancements.
Adapter
Framework runtime changes
|
Problem tracking numbers |
As of Version |
APAR Number |
Problem |
|
72183 |
2.6.0.4 |
JR22842 |
ClassCastExceptions in MQConnector |
|
61774 |
2.6.0.4 |
JR22843 |
Controller/agent trace levels do not
get dynamically updated |
|
72313,73664 |
2.6.0.4 |
JR22327/JR22844 |
Msg can not be converted to BO with ADK 2.6.0, which was working fine
with 2.4 |
|
67476 |
2.6.0.4 |
JR22845 |
The pollforevent
message printed in the trace file when trace level is 1 |
|
72403 |
2.6.0.4 |
JR22122 |
HTTP Adapter fails after getting
incomplete message |
|
71557 |
2.6.0.4 |
JR22846 |
Why are local config
files needed for logging for connectors? |
|
73521 |
2.6.0.4 |
JR22847 |
Adapter crashes with error 17069 if it
cannot find its message file - no stack |
|
71274 |
2.6.0.4 |
JR22849 |
connector_manager -stat gives incorrect results |
|
71268 |
2.6.0.4 |
JR21551 |
MQDEAD message stays in delivery and
fault queue |
|
71388 |
2.6.0.4 |
JR22850 |
Log messages in the log file when kill
-9 option is used |
|
72509 |
2.6.0.4 |
JR22109 |
RequestResponse DH throws java class not found exception |
|
74028 |
2.6.0.4 |
JR22747 |
Child verbs changed from CxBlank to CxIgnore in AF 2.6 |
|
74255 |
2.6.0.4 |
JR22851 |
Adapterenv.sh needs to be corrected in AF 2.6.x.x |
|
72029 |
2.6.0.4 |
(Enhancement) |
WBI Adapter Framework backed-out
message processing function |
|
61907 |
2.6.0.3 |
JR21718 |
Unexpected
exception for CwConnector.dll |
|
62206 |
2.6.0.3 |
JR21579 |
Siebel
COM Connector is failing once in a while |
|
60690 |
2.6.0.3 |
JR21987 |
4.2.2.4
ICS breaks interfaces that the Siebel COM connector uses |
|
71559 |
2.6.0.3 |
JR21799 |
Duplicate
ObjectEventID |
|
71311 |
2.6.0.3 |
JR21772 |
Siebel
adapter hangs if it gets a Siebel-specific application error |
|
71515 |
2.6.0.3 |
JR21718 |
After
pressing 'q' to exit the Siebel adapter, we get a fatal error |
|
71399 |
2.6.0.3 |
JR21689 |
Agent
should stop polling events once the current MQ depth exceeds 90 percent of
maximum depth |
|
72342 |
2.6.0.3 |
JR22046 |
Customer
gets a Call Stack error while starting the Siebel adapter |
|
66866 |
2.6.0.3 |
(Enhancement) |
MQ
source does not stop polling when ICS is killed |
|
70839 |
2.6.0.3 |
- |
ADK fix
for WBI Server Express 4.4 - iSeries controlled end
of adapter |
|
60381 |
2.6.0.3 |
JR21959 |
cwservice command has 2 times -t option |
|
71857 |
2.6.0.3 |
JR21842 |
P.E. Synchronous scenarios do not work in
4.3.0.1 |
|
70953 |
2.6.0.3 |
JP21630 |
Error
message in case of different BO schema and XML sequence |
|
70841 |
2.6.0.3 |
JR21967 |
HTTP
Adapter: Out of memory |
|
70797 |
2.6.0.3 |
JR21986 |
Invalid
JMS type message needs to be clearer |
|
66754 |
2.6.0.3 |
JR21962 |
Meaning
of MsgID: 165 |
|
66616 |
2.6.0.3 |
JR21352 |
SAP
adapter can't restart when there is an RFC_ERROR_SYSTEM_FAILURE error |
|
70895 |
2.6.0.3 |
JR21958 |
Message
needs to be more meaningful |
|
66664 |
2.6.0.3 |
JR21414 |
Flooding
IDLControllerProxy fatal error : CORBA ORB
connection error |
|
07633 |
2.6.0.3 |
(Enhancement) |
DataHandler base class provides a mechanism for displaying the version |
|
35953 |
2.6.0.3 |
(Enhancement) |
Provide
printStackTrace functionality in base datahandler class |
|
25927 |
2.6.0.3 |
(Enhancement) |
Set
property when using Xerces 2 |
|
33724 |
2.6.0.3 |
(Enhancement) |
Support
for running an adapter as a service in stand-alone mode |
|
37142 |
2.6.0.3 |
(Enhancement) |
Exit
when the adapter message file is missing |
|
28564 |
2.6.0.3 |
(Enhancement) |
Print
the Adapter Framework version |
|
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 version 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 |
|
The
Adapter Framework 2.4.0 fails when converting an XML message |
|
61281 |
2.6.0.2 |
|
The SAP
adapter version 2.6 is not sending invalid messages to the Fault queue. |
|
61176 |
2.6.0.2 |
|
An error
is thrown when the HTTP Adapter 1.2.0.1IF polls using JMS as DeliveryTransport |
|
44904 |
2.6.0.2 |
|
JMS
transported adapter can't get the response in Sync model |
|
44363 |
|
|
When |
|
44635 |
|
|
The
adapter pollForEvents does not work in
MAIN_SINGLE_THREADED mode |
|
59316 |
|
(Enhancement) |
Provide
built-in message audit and tracking functionality for Adapter Framework |
|
58998 |
|
(Enhancement) |
Security
exits/JMS transport not handled in the adapter |
|
59346 |
|
|
Wrong com.crossworlds.DataHandlers.cwxml generated by the Adapter
Framework |
|
44746 |
|
|
Print
the Adapter Framework version |
WBI
Toolset changes
|
Problem tracking numbers |
As of Version |
Problem |
|
35232 |
4.3.0.2 |
Problem with trace/log files when
Locale is French. |
|
70818 |
4.3.0.2 |
4.2.2.5 Connector Configurator
flattens hierarchical configuration files. |
|
71926 |
4.3.0.2 |
Connector Designer 4225 issues with
HTTP Connector 1.0. |
|
45463 |
4.3.0.2 |
Connector Configurator
won't load customers' template for the 2nd time. |
|
73167 |
4.3.0.2 |
HCG_BIDI: No support for WAS broker in
Connector Configurator. |
|
72221 |
4.3.0.2 |
Appended connector-specific property
disappeared after 4.3.0.1 upgrade. |
|
73888 |
4.3.0.2 |
ConnectorConfigurator slow loading BO. |
|
66879 |
4.3.0.2 |
Test Connector problem with the Child
BO <CxIgrone> Display. |
|
44484 |
4.3.0.1 |
Need a
new connector property to explicitly turn on/off BO auditing message |
|
60329 |
4.3.0.1 |
Slow ICS
bring-up time causes auto-start adapters to fail on start-up |
|
45637 |
4.3.0.1 |
Connector
Configurator should validate the values of
connector-specific propertiess |
|
44774 |
4.3.0.1 |
Add
"no" option to property XMLNameSpaceFormat |
|
45148 |
4.3.0.1 |
The
description of standard property SynchronousRequestTimeout
is incorrect. |
|
44800 |
4.3.0.1 |
The
version of the adapter is wrongly displayed in Adapter Monitor |
|
59069 |
4.3.0.1 |
zh_tw_pre-TVT_english string on Load Adapter |
|
45586 |
4.3.0.1 |
"adminmgr" does not work normally |
|
62182 |
4.3.0.1 |
Slow
performance with Business Object Designer version 4.3 |
|
61342 |
4.3.0.1 |
ICL
projects disappear from System Manager |
|
60726 |
4.3.0.1 |
Cannot launch
Log Viewer by specifying the log file as an argument |
|
61190 |
4.3.0.1 |
Business-object
level application-specific information disappears on restarting Business
Object Designer |
Prerequisites
You must have WBI Adapter Framework version
Installing the fix pack
1. Ensure that Adapter Framework 2.6.0 is installed and note the install directory.
2. Back up Adapter Framework runtime files listed in next table.
3. Download the fix pack zip or tar file and unzip or untar the file to a local directory
4. Run the fix pack Installer corresponding to the operating system:
- Windows setupwin32.exe
- Linux setupLinux.bin
- AIX setupAIX.bin
- HP UX setupHP.bin
- Solaris setupSolarisSapc.bin
Please refer to the Installer technical notes for instructions on installing Adapter Framework 2.6.0.x on AIX 5.3.
Please refer to the Installer technical notes for instructions on installing Adapter Framework 2.6.0.x on SuSE 9.0.
Note: You can record the options you select when installing for subsequent silent installations. For more information see Installing silently.
5. Follow Installer wizard prompts to complete installation of the Adapter Framework fix pack. Note that the Installer will end or not proceed if any of the following occurs:
Declining the licensing agreement.
Installing on a Windows platform and you do not have administrative privileges, or if your user login exceeds 20 characters.
Providing a Destination directory name that is not also the installation directory for Adapter Framework 2.6.0
Not providing sufficient free disk space (Windows 300 Mb, All Unix platforms 150 Mb)
6. During fix pack installation, you may be prompted to overwrite existing files. To successfully install the fix pack, you must select Yes to All.
Windows registry entries
After installation on Windows systems, the fix pack Installer updates a registry folder under HKEY_LOCAL_MACHINE\SOFTWARE\IBM\WebSphere Business Integration.
Installing silently
1. Launch the fix pack Installer using the following command:
<install launcher executable> -options-record<install_settings_filename>
For example, on Windows systems: you enter
setupwin32.exe options-record mySettings.txt
2. Edit the file containing your settings (for example, mySettings.txt) by adding the following lines to the end of the file:
G replaceExistingResponse=yesToAll
G replaceNewerResponse=yesToAll
G createDirectoryResponse=yes
G removeExistingResponse=yesToAll
G removeModifiedResponse=yesToAll
For an example, see the settings.txt file bundled with the fix pack Installer.
3. To silently install, launch the fix pack Installer as follows:
<install launcher executable> -silent-options<install_settings_filename>
For example:
setupwin32.exe silent-options mySettings.txt
Table of Adapter Framework runtime files installed by this fix pack:
|
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 |
|
|
Win32:Solaris:AIX:HP_UX
:Linux |
Replace |
license.txt |
|
Win32:Solaris:AIX:HP_UX
:Linux |
Replace |
notices.txt |
|
Win32:Solaris:AIX:HP_UX
:Linux |
Replace |
lib/jmsmgr.jar |
|
Win32 |
Replace |
bin/cwservice.exe |
|
Win32 |
Replace |
bin/start_adapter.bat |
|
Solaris:AIX:HP_UX :Linux |
Replace |
bin/adapterEnv.sh |
|
Solaris:AIX:HP_UX :Linux |
Replace |
bin/start_adapter.sh |
|
Solaris:AIX:HP_UX :Linux |
Replace |
bin/connector_manager |
|
Win32:Solaris:AIX:HP_UX
:Linux |
Replace |
AdapterJRE/ (whole Dir) |
|
Win32:Solaris:AIX:HP_UX
:Linux |
Add |
jdk/ (whole Dir) |
|
Win32 |
Replace |
bin/CwConnector.dll |
|
Solaris |
Replace |
lib/libCwConnector.so |
Table of Toolset files installed by this fix pack For Windows installations only:
|
Platform
[Win32;Solaris;AIX;HP_UX;Linux] |
Add / Replace / Remove |
File (Starting from WBIA installation
directory) |
|
Win32 |
Replace |
bin/Data/Std/StdConnProps.xml |
|
Win32 |
Replace |
bin/Data/Std/StdConnProps_chs_chn.xml |
|
Win32 |
Replace |
bin/Data/Std/StdConnProps_cht_twn.xml |
|
Win32 |
Replace |
bin/Data/Std/StdConnProps_deu_deu.xml |
|
Win32 |
Replace |
bin/Data/Std/StdConnProps_esn_esp.xml |
|
Win32 |
Replace |
bin/Data/Std/StdConnProps_fra_fra.xml |
|
Win32 |
Replace |
bin/Data/Std/StdConnProps_ita_ita.xml |
|
Win32 |
Replace |
bin/Data/Std/StdConnProps_jpn_jpn.xml |
|
Win32 |
Replace |
bin/Data/Std/StdConnProps_kor_kor.xml |
|
Win32 |
Replace |
bin/Data/Std/StdConnProps_ptb_bra.xml |
|
Win32 |
Replace |
bin/BusObjDesigner.exe |
|
Win32 |
Replace |
bin/ConnDesigner.exe |
|
Win32 |
Replace |
bin/LogViewer.exe |
|
Win32 |
Replace |
bin/enu_usa/ConnDesignerRes.dll |
|
Win32 |
Replace |
bin/chs_chn/ConnDesignerRes.dll |
|
Win32 |
Replace |
bin/fra_fra/ConnDesignerRes.dll |
|
Win32 |
Replace |
bin/jpn_jpn/ConnDesignerRes.dll |
|
Win32 |
Replace |
bin/cht_twn/ConnDesignerRes.dll |
|
Win32 |
Replace |
bin/ita_ita/ConnDesignerRes.dll |
|
Win32 |
Replace |
bin/deu_deu/ConnDesignerRes.dll |
|
Win32 |
Replace |
bin/esn_esp/ConnDesignerRes.dll |
|
Win32 |
Replace |
bin/ptb_bra/ConnDesignerRes.dll |
|
Win32 |
Replace |
bin/kor_kor/ConnDesignerRes.dll |
|
Win32 |
Replace |
bin/CxCommon2.dll |
|
Win32 |
Replace |
bin/ServerConnection.dll |
|
Win32 |
Replace |
bin/XRmi.dll |
|
Win32 |
Replace |
bin/SMInterface.dll |
|
Win32 |
Replace |
lib/CrossWorlds.jar |
|
Win32 |
Replace |
lib/datamanager.jar |
|
Win32 |
Replace |
lib/vtc.jar |
|
Win32 |
Replace |
Tools/eclipse/plugins/com.ibm.btools.csm |
|
Win32 |
Replace |
Tools/eclipse/plugins/com.ibm.btools.itools.common |
|
Win32 |
Replace |
Tools/eclipse/plugins/com.ibm.btools.itools.codeGen |
|
Win32 |
Replace |
Tools/eclipse/plugins/com.ibm.btools.itools.ae.settings |
|
Win32 |
Replace |
Tools/eclipse/plugins/com.ibm.btools.itools.cwconverter |
|
Win32 |
Replace |
Tools/eclipse/plugins/com.ibm.btools.itools.datamanager |
|
Win32 |
Replace |
Tools/eclipse/plugins/com.ibm.btools.itools.wsdlgen |
|
Win32 |
Replace |
Tools/eclipse/plugins/com.ibm.btools.adaptermonitor |
|
Win32 |
Replace |
Tools/eclipse/plugins/com.ibm.btools.bdm |
|
Software |
Version and patch |
Support From Version |
Comments |
|
Operating system |
|||
|
Windows XP |
Service Pack 2 |
2.6.0.3 |
Supported only for development CR71584 |
|
AIX 5.3 |
|
2.6.0.2 |
|
|
Red Hat
Enterprise Linux 3.0 RHEL 3.0 ES RHEL 3.0 AS RHEL 3.0 WS |
Update 3 |
2.6.0.3 |
|
|
Red Hat
Enterprise Linux 3.0 RHEL 3.0 ES RHEL 3.0 AS RHEL 3.0 WS |
Update 4 |
2.6.0.4 |
|
|
SUSE Linux Enterprise Server(ES) SUSE Linux
Standard Server(SS) |
9.0 |
2.6.0.3 |
CR59606 |
|
Integration broker |
|||
|
WebSphere Application Server, |
5.0.2.6 |
2.6.0.3 |
|
|
WebSphere Business Integration Server Foundation |
5.1.1 |
2.6.0.3 |
CR60614 |
|
WebSphere MQ Integrator Broker |
2.1 CSD08 |
2.6.0.3 |
CR60615 |
|
WebSphere Business Integration Message Broker |
5.0 CSD04 |
2.6.0.3 |
CR60612 |
|
WebSphere Business Integration Message Broker |
5.0 CSD06 |
2.6.0.4 |
|
|
WebSphere Business Integration Message Broker |
6.0 |
2.6.0.4 |
CR67721 |
|
WebSphere InterChange Server |
4.3.0.1
|
2.6.0.3 |
|
|
WebSphere InterChange Server |
4.3.0.2
|
2.6.0.4 |
|
|
Websphere Process Server |
6.0 |
2.6.0.3 |
|
|
Other softwares |
|||
|
IBM WebSphere
MQ Server and Client |
5.3.0.2 with CSD08 and CSD10. |
2.6.0.3 |
CR71901 |
|
IBM WebSphere MQ Server and Client |
6.0 |
2.6.0.4 |
CR66891 Only for standalone adapters. |
|
Common Event Infrastructure |
- |
2.6.0.3 |
AF/ADK to provide LINUX support for CEI CR59603 |
|
Java Development Kit/Java Runtime
Environment |
|||
|
IBM JDK/JRE (for Windows, AIX, Solaris,
HP-UX, and Linux computers) |
1.4.2 SR1 |
2.6.0.3 |
CR 60616 |
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 MQ Security Exit as the last element using this
format:
'queue_manager_name:channel_name:host_name:port_number:mq_security_exit_name'
- Put the class MQ Security Exit in the library path or extend the
path of the adapter
- When the adapter is launched, the MQ Security Exit will be invoked. If MQ Security Exit cannot be found, this feature will be treated as disabled.
Note: Because MQ Security Exit applies to queue
manager, products do not support MQ Security Exit feature should not use the
same queue manager as Adapter Framework.
2. To use the BO trace (CR59316) feature:
1) Enable 'BOTrace' property:
- Users of ICS or a standalone broker may use the '-x' parameter in the agent start script to configure the 'BOTrace' property if the patch for the Connector Configurator is not available; for example '-xBOTrace=Full'.
- If the patch for Connector Configurator patch is available, the user can configure the 'BOTrace' property in Connector Configurator.
2) The 'BOTrace' values are as follows:
When 'AgentTraceLevel' is 5, the property 'BOTrace' is not available.
When 'AgentTraceLevel' is lower than 5:
- Set 'BOTrace' to 'Full' to dump all the BO's attributes.
- Set 'BOTrace' to 'Keys' to dump only the BO's keys.
- Set 'BOTrace' to 'None' to disable BO attribute dumping.
3.
To support no namespace
BO(CR37590)
If the no option was not available for the property XMLNameSpaceFormat in Connector Configurator, the user should edit the Connector Configuration file manually, as described below. (It should be added in the WebSphere Business Integration (WBI) Toolset version 4.3.0.1)
- Open the Connector Configuration file in a text editor.
- Locate the XMLNameSpaceFormat property by searching. Here is an example:
<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 follows:
<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 namespaces in the BO's XML doc on the wire.</tns:description>
4.
AIX 5.3 supporting:
WebSphere Business Integration Adapter Framework has supported AIX 5.3 since version 2.6.0.2.
5. To enable Adapter Monitor to support the MQ Security Exit feature(CR58998):
- Put the class MQ Security Exit into the directory <AF Installer>\Tools\eclipse\plugins\com.ibm.btools.adaptermonitor\lib.
- Modify the Adapter Monitor's plug-in manifest file plugin.xml which resides in the directory <AF Installer>\Tools\eclipse\plugins\com.ibm.btools.adaptermonitor. In the <runtime> segment, add a library name entry for MQ Security Exit.
For example, suppose MyMQExit.zip includes this class. Add the following library name entry to the <runtime> segment of plugin.xml.
<library name="lib\MyMQExit.zip"/>
6.
To enable the
enhancement(CR66866) with MQ DeliveryTransport for
the adapter:
A new command line parameter 'WhenServerAbsent' is incorporated to indicate whether the adapter with MQ transport should pause or shut down when ICS is killed. ICS users may use the '-x' parameter in the agent start script to configure the 'WhenServerAbsent' property; for example:
-xWhenServerAbsent=shutdown //Adapter with MQ transport will shut down if ICS is not available
-xWhenServerAbsent=pause //Adapter
with MQ transport will pause if ICS is not available
If the option is not set, the adapter will keep polling by default
7.
Adapter Framework backed-out
message processing function (CR72029):
Command line parameter CheckRedelivered is incorporated to indicate
Adapter Framework how to handle redelivered message.
-xCheckRedelivered=<Threshold>
<Threshold> should be
zero or positive number. The Adapter Framework will try to process messages up
to that number of times before put them to fault queue.
- Default value is 1, which makes Adapter Framework behaviors as
before without this parameter.
- Zero value means Adapter Framework will try to process redelivered
message instead of putting it to fault queue. Redelivered times will be written
to trace file.
- If user give invalid value, Adapter Framework will keep the default value , i.e. 1.
8.
To support messages without namespace which
from WMQI (CR72313, CR73664):
Command line parameter AFNamespaceAware is incorporated to indicate
whether XML parser will check namespace.
-xAFNamespaceAware=true or doesn't
set //Default. Working with xml
message have namespace
-xAFNamespaceAware=false //Working with xml
message have not namespace.
Note:
Adapter Framework will not support XML message with namespace and without namespace at same time.
9. To resolve the problem in CR71557, WebSphere InterChange Server V4.3 need to apply fix pack 2 and plus.
10. When broker is Websphere Business Integration Message Broker V6, please follow the original release guide of WBIMB V5 support.
- If migrate from WMQI 2.1 by mqsimigratemsgflows.exe, add parameter "-data" to locate the Workspace. e.g. mqsimigratemsgflows.exe -p <project name> d "<your message flow files directory>" -data <WBIMB6 directory>\eclipse\workspace
- If migrate
from WBIMQ V5, pay attention that queue manager listener default port is 2414
in WBIMB V6, but it is 1414 in WBIMB V5. You may need to change the default
port to 1414 to be consistent with WMQ queue manager and adapter configuration,
or vice versa.
You can uninstall fix pack 4, but only by uninstalling all of Adapter Framework 2.6.0. You uninstall by using an interactive (graphical) tool or silently (using scripts).
To launch the graphical Uninstaller on Windows platforms:
- Choose Start>Settings>Control Panel, double-click Add/Remove Programs, and specify the Adapter Framework or
- Run the following executable: <fix_pack_install_location>_uninst_ Adapter Framework\uninstaller.bin
To launch the graphical Uninstaller on Unix or Linux platforms:
- Run the following:
<fix_pack_install_location>_uninst_ Adapter Framework/uninstaller.bin
After you launch Uninstaller, follow and respond to the prompts presented by the wizard.
To launch a silent uninstall on Windows platforms:
- Run the following executable:
<fix_pack_install_location>_uninst_ Adapter Framework\uninstaller.exe silent
To launch a silent uninstall on Unix or Linux platforms:
Run the following executable:
<fix_pack_install_location>_uninst_Adapter Framework/uninstaller.bin silent
ฉ
2005 IBM Corporation. Proprietary and Confidential.
All Rights Reserved.