INSTRUCTIONS FOR APPLYING 4.1.0.2 FIXPACK:

The 4.1.0.2 FIXPACK is delivered with the following files:

For Windows:
CrossWorlds.jar

For Solaris:
CrossWorlds.jar, libCwPorting.so, libCwConnector.so

For AIX:
CrossWorlds.jar, libCwPorting.so, libCwConnector.so


Caution: Applying this patch will OVERWRITE your existing installation's files. IBM recommends backing up the existing files before applying this patch.

For Windows:
To apply the fixpack, create a %CROSSWORLDS%\patches directory, place the ICS_4.1.0.2_WIN.zip file into this directory and unzip the file to your %CROSSWORLDS% (c:/crossworlds by default) directory.

The patch installs the following files:
	in your %CROSSWORLDS%\lib directory:
		CrossWorlds.jar


For Solaris:
To apply the fixpack, create a $CROSSWORLDS/patches directory, place the ICS_4.1.0.2_SOL.zip file into this directory and unzip the file to your $CROSSWORLDS% directory.

The patch installs the following files:
	in your $CROSSWORLDS/lib directory:
		CrossWorlds.jar, libCwPorting.so, libCwConnector.so


For AIX:
To apply the fixpack, create a $CROSSWORLDS/patches directory, place the ICS_4.1.0.2_AIX.zip file into this directory and unzip the file to your $CROSSWORLDS% directory.

The patch installs the following files:
	in your $CROSSWORLDS/lib directory:
		CrossWorlds.jar, libCwPorting.so, libCwConnector.so

	
-------------------------------------------------------------------------
CrossWorlds 4.1.0.2 fixpack contains fixes for:
Probelm Tracking number 
14055
ICS fails to start up unless the Oracle Thin Driver is present.

14861 
CDK bug in the 4.1.0 release which causes any C++ connector on AIX may not be working (fails while trying to poll ).

15040
 CDK bug in the 4.1.0 release which causes any C++ connector on Solaris may not start.

11473
 Due to this bug, memory check does not work well on machines that have more than 2G physical memory in 4.1.0 release. One caveat of this fix is that it is possible that the customer can get OutOfMemory error even when the memory checker is turns on. In that case, please check two things: 
               a. if ICS server runs out of memory during boot up, then the customer needs to increase the JVM max heap value (-mx option). The memory checker only start up after the ICS server is up. In other words, memory checker cannot control the boot up memory usage. 
               b. make sure the system has enough swap space, the swap space should be 5 - 6 times larger than the JVM heap size (-mx option). and may be more if there are more than one App running on that machine.
 
15007
 Due to this bug the customer who has case sensitive MSSQL was getting different database errors in ICS. To fix it, the column names of database tables are checked and corrected in the code to follow proper upper/lowercase convention. 

14989
 Due to this bug, the customer cannot exit the Connector Agent in a single threaded mode when the MQ Series Queue Manager  comes down. This fix will allow the Connector Agent that starts in a single threaded mode to appropriately terminate and exit when the MQ Series transport is down. The caveat is that it will work only in case of MQSeries. This does not fix the other protocols like IIOP,HTTP,etc
 
14292
 User cannot input Business Object names, Collaboration names or DB Connection names of 80 characters or greater because we store this information in those fields of the database which are small. The fix involves widening those fields in the DB to 160 (or more) characters. 

14977
On DB2, when trying to discard unresolved flows from the CSM in release 4.1.0, the screen seems to be locked up and the flow takes around 6 minutes before being discarded. This problem is due to a bug in the server side and is fixed in this release.