Readme
for
WebSphere Interchange Server (WICS) version 4.3.0.1 Limited Availability
Interim Fix 10
The readme contains the following sections:
This interim fix contains fixes for the following customer reported and internally discovered issues.
|
APAR |
As of Version |
Problem |
|
73729 |
4.3.0.1.LAIF10 |
ICS getting onto a hung |
|
73718 |
4.3.0.1.LAIF9 |
ConnectionCacheSweeper, fails with SQLState [08006]: [IBM-CrossWorlds]
[Oracle JDBC Driver] No more data available to read.DB
specific error: 0)] While
attempting to disconnect from data source. |
|
72907 |
4.3.0.1.LAIF8 |
WIP in-transit information not cleaned up in repos
database |
|
72853 |
4.3.0.1.LAIF7 |
java.lang.NullPointerException in in WIPTransaction context |
|
60059 |
4.3.0.1.LAIF7 |
ICS gets
unknown ORACLE error |
|
44471 |
4.3.0.1LAIF6 |
OAD cannot
re-start agent |
|
72142 |
4.3.0.1LAIF5 |
Incorrect event sequencing behavior for BOs with children |
|
67092 |
4.3.0.1LAIF5 |
MsgId:81147-As number of possible active sessions has reached
the threshold the login operation failed. |
|
44861 |
4.3.0.1LAIF4 |
Component
does not show correct status in CSM |
|
67060 |
4.3.0.1LAIF4 |
Connectors,
maps and relationships have no response after changing their status in CSM. |
|
72140 |
4.3.0.1LAIF4 |
MsgId:46018-flow
controlled resource is full |
|
66970 |
4.3.0.1LAIF3 |
Cannot
run collaboration with JMS delivery transport as a multithreaded process. See configuration instruction in Additional Discussion” section below. |
|
71739 |
4.3.0.1LAIF3 |
Incorrect
total flows collaboration statistic |
|
71161 |
4.3.0.1 LAIF2 |
ICS
receives duplicate events after MQ crash |
|
66830 |
4.3.0.1 LAIF2 |
LLBP collaboration unable to resubmit event |
|
71129 |
4.3.0.1
LAIF1 |
ics_manager -stop and -IsServerAlive does
not work when RBAC is enabled |
|
70557 |
4.3.0.1
LAIF1 |
Map
Compilation fails, when exported from Server |
Prerequisites
1. You must have installed WICS InterChange Server version 4.3.0.1 before installing this interim fix.
To upgrade to WICS 4.3.0.1 LAIF 10
1. Download the LAIF
package according to your WICS server operating system.
2.
Back up the files listed in the
table below to allow this interim fix to be uninstalled.
3.
Unpack the zip or tar package to
the WICS installation directory. For example on AIX® extract WICS_4301_LAIF10_UNIX.tar
to /usr/home/WebSphereICS if that is your installation directory.
Table of files installed by this interim fix (note that some of these files are installed by the ITLM installer)
|
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 |
66970 Configuration
instructions:
To configure multi-threading
for synchronous calls when the transport is JMS:
1.
By default ICS uses 1 thread for a sync call when the transport is JMS.
2.
To configure a larger default number of threads, modify InterchangeSystem.cfg
manually as shown below. ICS will use the value as the global default. (All
connector controllers with JMS transport will use this value).
3.
To configure multi-threading for an individual connector, use the connector configurator - Connector-Specific Properties tab to add a
new property as described below. The connector will use the value as the max
multi-thread number. This takes precedence over the global default value.
How
to modify InterchangeSystem.cfg manually:
Add
this xml node as an element in cw:ServerConfig
(just before </cw:ServerConfig>
)
<tns:property>
<tns:name>JMS</tns:name>
<tns:isEncrypted>false</tns:isEncrypted>
<tns:updateMethod>system restart</tns:updateMethod>
<tns:location>
<tns:reposController>false</tns:reposController>
<tns:reposAgent>false</tns:reposAgent>
<tns:localConfig>true</tns:localConfig>
</tns:location>
<tns:property>
<tns:name>SyncListenerConcurrency</tns:name>
<tns:value xml:space="preserve">15</tns:value>
<tns:isEncrypted>false</tns:isEncrypted>
<tns:updateMethod>system restart</tns:updateMethod>
<tns:location>
<tns:reposController>false</tns:reposController>
<tns:reposAgent>false</tns:reposAgent>
<tns:localConfig>true</tns:localConfig>
</tns:location>
</tns:property>
</tns:property>
Number
15 in this xml example is the max thread number
for a sync call when using JMS transport.
How
to add a property in connector configurator:
Add
a new property of "jms.SyncListenerConcurrency"
in Connector-Specific Properties, set Value to the desired max thread count.
Set property's type to String.
Uninstall Instructions
1.
To uninstall this interim fix, replace the new files with the backed-up
files form step 2 of the upgrade instructions above.
© 2005 IBM Corporation. Proprietary and Confidential. All Rights Reserved.