Readme for
WebSphere
Interchange Server (WICS) version 4.2.1.7 fix pack
The patch notes contain the following sections:
This patch contains fixes for the following CRs based on
customer reported and internally discovered issues.
Problem tracking numbers |
As of Version |
Problem |
34598 |
4.2.1.7 |
ICS Memory leak when used with IsServerAlive |
35738 |
4.2.1.7 |
duplicate() api is not working. "triggeringBusObj
= BusObj.duplicate()" in a child collaboration does not return the value
to the parent collaboration when transaction level > none. |
32728 |
4.2.1.7 |
Error
restarting connector after setproperty in ICSMonitor |
35935 |
4.2.1.7 |
Flow manager slow coming up. |
33732 |
4.2.1.7 |
Connectors and collaborations deployed in start
state are not starting. A message will
now be issued that ICS reboot is required when new connectors or
collaborations are deployed. |
34866 |
4.2.1.7 |
When Collaboration has the transaction level set to
anything other than "None", it does not recognize changes made to
BOs in response to service call |
34857 |
4.2.1.7 |
The deployment does not work properly if there is a
Jobschedule already deployed to the server. |
35026 |
4.2.1.7 |
getOriginalRequestBO api
returns null. Fixed to return the correct BO. |
29654 |
4.2.1.7 |
Explicitly Bound maps in Adapters lose binding |
34565 |
4.2.1.7 |
ICS shuts down with error “MsgID:11056
- Server will be shut down because collaboration cannot delete event”. The problem occurs for collaborations
configured with “pause on critical error” if an agent reconnects after an
error. |
34315 |
4.2.1.7 |
ICS server sometimes hangs during map
deployment |
28780 |
4.2.1.7 |
ICS cannot start with separate databases configured
for Repository, Event Management, and Transactions. |
34310 |
4.2.1.7 |
ICS leaks memory of 1 BO for each asynchronous
inbound service call to a Long Lived Business process (LLBP). Eventually ICS will run out of memory
depending on the size of the BO. |
28259 |
4.2.1.7 |
ICS memory leaks have been fixed in transactional
collaborations and in collaborations invoked via Access Framework API. |
30977 |
4.2.1.7 |
No error recovery in ICS for
MQSeries return code 2019 (connection failure). Error recovery has been
added. |
25882 |
4.2.1.7 |
User Defined Database Connections cannot be
redeployed. |
29324 |
4.2.1.7 |
AgentTraceLevel cannot be dynamically updated. |
29106 |
4.2.1.7 |
Losing events when Max concurrent events set to 1
and system crashes |
34338 |
4.2.1.7 |
4.2.1.6 ICS Fix Pack corrupts verb ASI containing
single quotes |
28332 |
4.2.1.7 |
Message file unavailable after migration from 3.1.2
to 4.2.1 |
32595 |
4.2.1.7 |
Server access call failed on Japanese characters in
BO |
31428 |
4.2.1.7 |
error in ics_manager.sh and startup scripts on AIX |
32501 |
4.2.1.7 |
Fixes CollabGroupException - “can’t identify head (direction)
of a collaboration group” during ICS Boot time. |
33199 |
4.2.1.7 |
ControllerStoreAndForwardMode works only after one connector startup. |
27989 |
4.2.1.7 |
Compiling collaboration template which uses deprecated API throws
“error: Failed to compile.” |
32149 |
4.2.1.7 |
ICS exception received: java.util.EmptyStackException in
CxCommon.FlowExecContext.removeLastFlowExecStatusEntry. The exception is
handled now. |
28441 |
4.2.1.7 |
Repository import
from ICS to System manager takes a long time. The import time has been improved. |
23924 |
4.2.1.7 |
Cannot set default value to apostrophe (') in BO
Designer. Apostrophe can now be used. |
32474 |
4.2.1.7 |
LLBP Async Inbound call fails with service call
exception when maps are used. |
29980 |
4.2.1.7 |
Error encountered when importing relationships into
ICL from server using Deep:
“CxCommon.Exceptions.DeployHaltException: Cannot Export Component *n as
Repository information is not available." |
27112 |
4.2.1.7 |
Incomplete messages were written to the log file
for Collaborations. Now more detailed messages are logged. |
31059 |
4.2.1.7 |
Log message format was wrong when same file is used
for logging and tracing by ICS, making it unreadable by Log Viewer. The
format has been corrected. |
15919 |
4.2.1.7 |
Connector controller showed as active when the
queue manager was stopped abruptly (End method = immediate). It was possible
to stop and start connectors even though the queue manager was not running.
With the fix, connector will be deactivated if the queue manager is stopped.
It will also check for connectivity with the queue manager on state change. |
31422 |
4.2.1.5 |
Fixed such that Transactional Collaboration
receives the updated BO from the Agent in response to a Service Call |
30073 |
4.2.1.4 |
MQ Reason Code 2033 message shows
up way too many times in the ICS log and stderr, making them difficult to
understand. So this fix excludes MQ Reason code 2033 message from appearing. |
23011 |
4.2.1.4 |
ObjectEventId generated by
mapping Infrastructure was not always unique for both parent and child BO.
Fixed in this Fix Pack |
30350 |
4.2.1.4 |
Some failed events are not showing up in the flow manager as expected |
25930 |
4.2.1.4 |
Collaboration group breaks when
duplicate names exists for collaborations and connectors |
25932 |
4.2.1.4 |
FlowControl resource creation
fails when duplicate connector and collaborations exist. |
28966, 27584 |
4.2.1.4 |
ASync Inbound Service call is
processed as a failed event when there are no subscribers for the BO. ICS
traces (@trace level 2) the SQL Exception to ICS trace file instead of ICS log |
25471 |
4.2.1.3 |
Fixes the XML datahandler problem
when it was not able to parse the XML message that contained no namespace definitions To
support the parsing of xml messages without namespaces defined, you must add
a connector-specific property to the connector definition called
XMLNameSpaceFormat. The value of this property should be set to 'no' |
25880 |
4.2.1.3 |
MQ exception rc=2019 using
SAP adapter with large (25mb) messages when MQ connection failure occurs.
This fix enables the ICS to recover from the MQ connection failure without
exception |
25927 |
4.2.1.3 |
When apache v2.0.2 xml
parser is used performance is slower. This fixes the performance problem. |
29943 |
4.2.1.3 |
repos_copy command with –arp option had an intermittent error
that caused a failure to deploy the repository updates in WICS version
4.2.1.1. This fixes the problem. |
28179 |
4.2.1.3 |
Rosetta Net deploy maps
causes Null Pointer Exception in server - In the connector definition, if the
explicit binding box is checked, and set to <none> we get a Null
Pointer Exception in the server during deploy of the maps. |
27719 |
4.2.1.3 |
WBIA 2311 Err. msgs no
longer appended to XML message |
24895 |
4.2.1.3 |
Deploy with compile
errors: no error message in System Manager. Requires WICS Tools fix pack
version 4.2.1.3. |
22144 |
4.2.1.1 |
Exception starting the TPI
Adapter “Incompatible object argument for function call” was caused by
incompatible version of xerces (v2.0.2). The problem is fixed. |
24556 |
4.2.1.1 |
Problem: Subject of Email sent by logError() is not easy to read. Fixed in this Fix Pack |
24600 |
4.2.1.1 |
Problem solved: With CR we are reducing the size of xml that is
sent to WMQI. This is done by compressing the namespaces in the bo xml
document. This is a configurable behavior. Standalone connectors that want to
use it need to configure a property "XMLNameSpaceFormat" and set
its string value to "short" (without the quotes of course). They
can add this property to the app specific property in the connector config
file with the help of Conn Designer.
short XMLNameSpaceFormat is supported only with
RFH2MessageDomain standard property set to 'xml'. When RFH2MessageDomain is
set to 'mrm', only long XMLNameSpaceFormat is supported. |
22249 |
4.2.1.1 |
Fixed
memory leak that caused server crash on deploy or export of large repository.
Related WBI Tools CR 22935 |
|
|
|
24735 |
4.2.1.1 |
Adapter could
not be restarted after changing the “encrypted” option. Error message was
“Unable to decrypt the attribute using ID. Reason: Encrypted property value
is wrong.” The problem is fixed by this fixpak. |
To upgrade to WICS 4.2.1.7
1.
Back up the listed files first to
allow the fix pack to be uninstalled.
2.
Apply the changes prescribed in the table below:
3.
For AIX, Solaris, or HP_UX systems: If you have not already installed
WICS 4.2.1.3 fix pack then you must back up the file bin/CWSharedEnv.sh and run
the script bin/ics4213_patch.sh. This script must be run from the bin directory
of your WICS installation. This script
will modify the file: bin/CWSharedEnv.sh to improve the performance of WICS
when XERCES v2.0.2 XML parser is being used. The script also makes a backup
copy in bin/CWSharedEnv.sav4213. You
should make your own back up copy for uninstall purposes. The presence of your
own back up copy will indicate that the file needs to be replaced in uninstall.
Platform [Win32;Solaris;AIX;HP_UX] |
Add / Replace /
Remove |
File (Starting from WICS installation directory) |
Win32:Solaris:AIX:HP_UX |
Replace |
lib/CrossWorlds.jar |
Win32:Solaris:AIX:HP_UX |
Replace |
lib/cworion.jar |
Win32:Solaris:AIX:HP_UX |
Replace |
lib/datamanager.jar |
Win32:Solaris:AIX:HP_UX |
Replace |
lib/xrmi.jar |
Win32:Solaris:AIX:HP_UX |
Replace |
messages/InterchangeSystem.txt |
Win32 |
Replace |
DevelopmentKits/cdk/lib/Release/CwConnector.dll |
Win32 |
Replace |
DevelopmentKits/cdk/lib/Release/CwConnector.lib |
Win32 |
Replace |
DevelopmentKits/cdk/lib/Debug/CwConnector.dll |
Win32 |
Replace |
DevelopmentKits/cdk/lib/Debug/CwConnector.lib |
Win32 |
Replace |
bin/cwservice.exe |
Win32 |
Replace |
bin/start_server.bat |
Win32 |
Replace |
bin/CdkTools.dll |
Win32 |
Replace |
bin/CwConnector.dll |
Win32 |
Replace |
bin/HAICS.dll |
Win32 |
Replace |
bin/HAICSex.dll |
Solaris:AIX:HP_UX |
Add |
bin/ics4213_patch.sh |
Solaris:AIX |
Replace |
lib//libbenchmark.so |
Solaris:AIX |
Replace |
lib/libCwConnector.so |
Solaris:AIX |
Replace |
lib/libCwPorting.so |
Solaris:AIX |
Replace |
lib/libMemoryService.so |
Solaris:AIX |
Replace |
lib/libpasswordInput.so |
HP_UX |
Replace |
lib/libCwPorting.sl |
HP_UX |
Replace |
lib/libCwConnector.sl |
Prerequisites
1.
You
must have version 4.2.1 of WICS installed in order to install this fix pack.
2.
This
server fix pack requires that you install WICS Toolset fix pack 4.2.1.7 or
later.
1.
When installing the fix pack, you should first back up all the old files
that are being replaced. To uninstall this fix pack, replace the new files with
the backed-up files.
2. For AIX, Solaris, and HP_UX systems: If you updated bin/CWSharedEnv.sh as in step 3 of the installation instructions above; then you must also replace this file with your back-up copy.
© 2004 IBM Corporation. Proprietary and Confidential. All Rights Reserved.