Readme for
WebSphere Interchange Server (WICS) version 4.2.2.4

 

The patch notes contain the following sections:

New in this release – ITLM enablement feature

Completed Change Requests

Upgrade Instructions

Additional Discussion

Uninstall Instructions

New in this release – ITLM enablement feature

 

IBM Tivoli License Manager (ITLM) enablement - A new inventory and license management tool is bundled as part of the WebSphere InterChange Server. Version 2.1 of the IBM Tivoli« License Management (ITLM) product provides a framework for this asset management. The same ITLM product is also provided with IBM WebSphere Business Integration Toolset 4.2.2.4. In the current release of both WebSphere InterChange Server and WebSphere Business Integration Toolset the ITLM product is enabled only for inventory support. A separate ITLM installer is provided to install ITLM. See step 4 in the upgrade instructions.

 

 

Completed Change Requests

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

Problem tracking numbers

As of Version

Problem

32669

4.2.2.4

Connector property MaxEventCapacity must be in the range 1 to 2147483647. The InterChange server was not enforcing this value range.

43668

4.2.2.4

ITLM enablement in ICS 4.2.2

37133

4.2.2.4

Collaboration does not return from recovery.

32728

4.2.2.4

System monitoring of connector state changes sometimes causes errors when the connector is stopped and restarted.

33530,33602,34992,42216,58551

4.2.2.4

Incorrect values are reported for collaboration and connector statistics.

42667

4.2.2.4

Error stopping and restarting a map. If the map properties are displayed or modified in CSM while the map is active then the map cannot be stopped and restarted.

35582

4.2.2.4

Java StackOverFlow error when attempting to start out of the box collaboration.

35933

4.2.2.4

ICS has memory leaks when used with CSM

32474

4.2.2.4

LLBP Async Inbound call fails with ServiceCallException when maps are used.

37770

4.2.2.4

Dynamic property change in a collaboration of a collabgroup destroys all collaborations

34598

4.2.2.4

Agent connection to ICS is very slow after ICS has been running a long time.

35281

4.2.2.4

OAD MQ trigger: first retry does not try in the time interval specified

46029

4.2.2.4

Adapter version should always be traced. Implemented in ADK.

35026

4.2.2.4

getOriginalRequestBO API not working.

34661

4.2.2.4

Cannot deploy BO with an attribute default value containing a single quote.

35295

4.2.2.4

OAD MQ trigger: multiple boot agent commands spawns multiple Activation threads

35070

4.2.2.4

ICS fails to boot up after deploy of 2 maps with same name (with different case)

32096,34310

4.2.2.4

Memory leak caused OutofMemory exception  when using an Async Inbound collab with LLBP.

27261

4.2.2.4

Native Maps not deleted from Registry when all Native Maps are deleted

34565

4.2.2.4

MsgID:11056 - Server will be shut down because collaboration cannot delete event

30073

4.2.2.4

MQ 2033 error message filling up the log files.

33000

4.2.2.4

start_server_service.bat should not have \bin\java after %CWJAVA%

36763,58347

4.2.2.4

Adapters cannot connect to the ICS after restarting the Persistent Name Server.

36874

4.2.2.4

When the Persistent Name Server is running on a separate machine from the ICS server, recovering the name server required copying the IOR repository file from the ICS machine to Name Server machine.  This has been fixed so that there is no need to copy the file.

34315

4.2.2.4

ICS server sometimes hangs during map deployment

29249

4.2.2.4

An invalid XML character <unicode: 0x0> was found in the element content of the document

34726

4.2.2.4

Invalid messages when received by adapter running with WBIMB are lost.

34472

4.2.2.4

MQ adapter throwing OutOfMemory error when processing large event

36131

4.2.2.4

The adapter framework throwing java.lang.ClassCastException: com.ibm.jms.JMSByte

43122

4.2.2.4

BO attribute MaxLength<8, "CxIgnore" causes validation exception on WAS broker

58242

4.2.2.4

size="0" in XML message from broker to adapters causes failure with ambiguous error message:

“There is no attribute at position “x” in business object definition”

ADK fixed to handle “size=0” to indicate the absense of a child object.

33729

4.2.2.4

Enable agent to retrieve Trace/Log configuration from server

58573

4.2.2.4

Restart/Retry feature is not killing polling threads on successive retries

58883

4.2.2.4

Cannot restart standalone adapters

29963

4.2.2.4

Can start more than one adapter with the same name.  Added checking to ensure that an adapter cannot be started more than once on the same platform. A message will be displayed to the user if this condition is detected.

 

 

 

36817

4.2.2.3

ICS startup gets null pointer exception if the name server is not running. Fixed ICS to log an error and exit.

36309

4.2.2.3

A collaboration in PAUSE state cannot be started after rebooting the ICS.

36147

4.2.2.3

Dynamic update of agent trace level does not work.

30977

4.2.2.3

No error recovery in ICS for MQSeries return code 2019 (connection failure). Error recovery has been added.

28780

4.2.2.3

ICS cannot start with separate databases configured for Repository, Event Management, and Transactions.

34696

4.2.2.3

Flow Manager connecting to ICS is very slow.

42294,35738,31422

4.2.2.3

Response BO is not updated if collaboration’s “Effective transaction level” is not equal to “None”

46185

4.2.2.3

ICS IndexOutOfBounds exception in CxListBuffer fixed.

29654,35100,34856

4.2.2.3

Deploying 2 maps with the same BO’s causes explicit bindings for the maps to be lost.

34977

4.2.2.3

The Persistent Name Server does not restore the names after being restarted.

33366

4.2.2.3

Server does not generate persistent IOR file.

33337,33338,33339

4.2.2.3

Added Large Object support in ADK for the JText adapter.

34350,46118

4.2.2.3

JDBCConnector RetieveByContent verb fails if the select query encounters multiple matching records.

 

 

 

28441

4.2.2.2

Repository import from ICS to System manager takes a long time. The import time has been improved

31133

4.2.2.2

When flow monitoring a group collaboration, the events for a child and parent collaboration may be recorded in the wrong order.

32243

4.2.2.2

Added support for a custom schema name for the Flow Monitoring database. The Flow Monitoring table may now reside under a schema different than the database user name.

33219

4.2.2.2

Added messages which indicate that the server is attempting to reconnect to a lost database connection.

30371

4.2.2.1

ICS runs out of memory during stress runs. DataDirect Database Drivers upgraded for SQL Server and Oracle databases.

31329

4.2.2.1

An error dialog pops up during repository imported into Tools from ICS server.

32199

4.2.2.1

Adapter framework always prepends connector name to ObjectEventId. After applying this patch, a new standard connector property, EnableOidForFlowMonitoring, will be added for ICS brokers.  The property is a Boolean with a default of false.  If the property is set to true, the ADK will mark the incoming ObjectEventID as a foreign key for Flow Monitoring.

 

 

Upgrade Instructions 

Please read: Upgrade procedure is changed significantly from previous releases

To upgrade to WICS 4.2.2.4

1.      Download all 4 files from the appropriate download link according to your WICS server operating system.

2.      Back up the files listed in the table below to allow the fix pack to be uninstalled.

3.      Unpack the zip or tar package to the WICS installation directory. For example on AIX® extract WICS_4224_AIX.tar to /usr/home/WebSphereICS if that is your installation directory.

4.      Run the ITLM installer: setup.bin or setup.exe. Installation of this ITLM feature is required with WICS 4.2.2.4 fix pack. 

5.      For Unix installations only: update bin/PersistentNameServer.sh as follows:

a)Replace line 15 “. VAR_CWHOME/bin/CWSharedEnv.sh” with the corresponding line from the original file backed up un step 1.

 

b) For the Java command to start the TransientnameServer, set the JVM property CosNamingPersistencyFile to point to the file CxCosNameRepos.ior in the ICS installation directory.  For example: add -DCosNamingPersistencyFile="/usr/home/WebSphereICS422/CxCosNameRepos.ior"

as follows:

# start tname server

exec ${JAVA} -DCosNamingPersistencyFile="/usr/home/WebSphereICS422/CxCosNameRepos.ior" ${COS_NAME_HOOK} -classpath ${CWCLASSES} com.ibm.CosNaming.TransientNameServer -ORBInitialPort ${ORB_PORT}

6.      For Unix installations only: Update CWSharedEnv.sh as follows:

a) Insert the following line just above CWCLASSES: ITLM=${CROSSWORLDS}/lib/ITLMToolkit.jar:${CROSSWORLDS}/lib/jlog.jar

 

b) Append  "${ITLM}:" to CWCLASSES line resulting in:

CWCLASSES=${JRT}:${WLICENSE}:${CORECW}:${DATAHANDLERS}:${DATADI            RECT}:${XML_PARSER}:${DATAMANAGER}:${ITLM}:

Table of files installed by this fix pack

Platform [Win32;Solaris;AIX;HP_UX]

Add / Replace / Remove

File (Starting from WICS installation directory)

Win32:Solaris:AIX:HP_UX

Add

bin/CC001616J040202.sys

Win32:Solaris:AIX:HP_UX

Add

bin/CC000976J040202.sys

Win32:Solaris:AIX:HP_UX

Add

bin/CC001133J040202.sys

Win32:Solaris:AIX:HP_UX

Add

bin/CC001351J040202.sys

Win32

Replace

bin/start_server.bat

Win32

Replace

bin/start_server_service.bat

Win32

Replace

bin/PersistentNameServer.bat

Solaris:AIX:HP_UX

Replace

bin/PersistentNameServer.sh

Win32:Solaris:AIX:HP_UX

Replace

lib/CrossWorlds.jar

Win32:Solaris:AIX:HP_UX

Replace

lib/xwbase.jar

Win32:Solaris:AIX:HP_UX

Replace

lib/xworacle.jar

Win32:Solaris:AIX:HP_UX

Replace

lib/xwsqlserver.jar

Win32:Solaris:AIX:HP_UX

Replace

lib/xwutil.jar

Win32:Solaris:AIX:HP_UX

Add

lib/ITLMToolkit.jar

Win32:Solaris:AIX:HP_UX

Add

lib/Jlog.jar

Win32:Solaris:AIX:HP_UX

Replace

messages/InterchangeSystem.txt

Prerequisites

1.      You must have version 4.2.2 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.2.4 or later.
 

Additional Discussion

 

Uninstall Instructions

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.

© 2004 IBM Corporation. Proprietary and Confidential. All Rights Reserved.