Patch Notes for Interchange Server

Fix Pack Notes for
WebSphere Interchange Server (WICS) version 4.2.0.7

The patch notes contain the following sections:

Completed Change Requests

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

Problem tracking numbers	As of Version	Problem
28259	4.2.0.7	ICS has memory leak
27034	4.2.0.7	Native Maps not deleted from Registry when all native maps are deleted
28441	4.2.0.7	Repository import from ICS to System manager takes a long time.
32246	4.2.0.7	Event Sequencing fails if Key is Child BO.
29106	4.2.0.7	Recovery fails to load BO when MaxEventCapacity set to 1.
23924	4.2.0.7	Cannot set default value apostrophe (‘) in BO Designer.
32149	4.2.0.7	Fixed ICS exception: java.util.EmptyStackException in CxCommon.FlowExecContext.removeLastFlowExecStatusEntry
31422	4.2.0.7	Fixed such that Transactional Collaboration receives the updated BO from the Agent in response to a Service Call
25283	4.2.0.7	Fixes the Relationship deployment when the repository is being deployed on IBM DB2 database
24568	4.2.0.7	The SNMP Agent was causing memory leak for the WebSphere Interchange Server and itself. This fix was listed in the WICS Tools fix pack 4.2.0.2 but is not fixed unless cwsnmpagent.jar is installed on the system where the SNMP agent is installed.
23011	4.2.0.5	ObjectEventId generated by mapping infrastructure was not always unique for both parent and child BO. Fixed in this Fix Pack
28179	4.2.0.5	In the connector definition, if the explicit binding box is checked, and set to <none> WICS server gets a Null Pointer Exception in the server during deploy of the maps.
31034	4.2.0.5	Collabutils.jar was incorrectly named as CollabUtils.jar in previous fix packs. It has been renamed in this fix pack.
25158:	4.2.0.4	Problem Description: When database connections are lost due to network or other problems the interchange server may run out of sessions and subsequently freeze.
23797	4.2.0.3	Problem Description: When the connector agent connects to the server, encrypted properties are not downloaded properly for example application password. This might cause malfunction in the functioning of the application connector. This is fixed in 4.2.0.3
24071	4.2.0.3	CwDBConnection class returns values with wrong datatypes (a decimal field is returned as Integer instead of BigDecimal). It is fixed.
23816	4.2.0.3	When binding a map in the connector configuration, allow <None> to be used with explicit binding.
23164	4.2.0.3	Connector optimized recovery failed. This has been fixed
22566	4.2.0.3	Previously, you could not upgrade from 3.1.2 directly to 4.2.0 when using IBM DB2 or SQLServer. This has been fixed.
22694	4.2.0.2	This fix creates proper map names for dependency checks when deploying a map with custom code.
16416	4.2.0.2	Previously multiple ICS servers sharing the same DB2 instance (repository) did not work properly. This has been fixed.
22845	4.2.0.2	Fixes the problem where some collaborations did not appear on the Monitor tool even though they were successfully deployed to the server.
22844	4.2.0.2	This fix addresses how the log messages is printed when a SOAP envelope is received.
22860	4.2.0.2	Previously, the server did not store sub-map dependencies properly; To fix this, redeploy the server in design mode and then reboot the server in production mode.
22772	4.2.0.2	Previously, deployment of collaboration templates with long names failed. This has been fixed.
22799	4.2.0.2	This fix adds the High Availability (HA) samples for AIX.
17420	4.2.0.2	This fix enables filtering (Filter.class) of child business objects with single cardinality at the child level; This had previously worked in 3.1.2.
21757	4.2.0.1	Using Microsoft SQL Server, this fix allows you to upgrade from 4.1.1 to 4.2. Note: upgrading from 3.1.2 to 4.2 using SQL Server may still have problems. The fix should be in the next Fix Pack. For now, you can upgrade from 3.1.2 to 4.1.0 first, and then upgrade from 4.1.0 to 4.2.0.
22202	4.2.0.1	Beginning with the 4.2 release, the Oracle thin driver is no longer embedded in the product. The database connectivity drivers for Oracle and Microsoft SQL Server are the IBM JDBC drivers. If you use the Oracle thin driver, this fix pack will automatically convert it into the supported JDBC driver.
22430	4.2.0.1	Fixes repository exports from the server. The server now includes message files when exporting a single collaboration template or map.

Upgrade Instructions

To upgrade to WICS 4.2.0.7,

1. This fix pack can be applied to WICS version 4.2.0 base or with any previous fix pack level. This fix pack includes all fixes from previous fix packs.

If you are currently using either WICS version 4.2.0.0 or 4.2.0.1:

1. Back up your data by doing a repos_copy out

2. Manually drop database tables and schemas (repos_copy -d will only drop the contents of the tables)

3. Apply the changes prescribed in the table below.

4. Start the WICS server

5. repos_copy in your backup data

If you have already upgraded to WICS version 4.2.0.3 or later then you only need to apply the changes as follows:

After backing up the listed files, add, replace, or remove the following files and directories as indicated:

Platform [Win32;Solaris;AIX]	Add / Replace / Remove	File (Starting from %CROSSWORLDS%/$CROSSWORLDS)
Win32:Solaris:AIX	Replace	lib/CrossWorlds.jar
Win32:Solaris:AIX	Replace	lib/cwsnmpagent.jar
Win32:Solaris:AIX	Replace	lib/datamanager.jar
Win32:Solaris:AIX	Replace	lib/Collabutils.jar
AIX	Add or Replace	samples/HA/HACMP (all files)

Prerequisites

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

Additional Discussion

Uninstall Instructions

When installing the fix pack, back up all the old files that are being replaced. To uninstall this fix pack, replace the new files with the backed-up files.