Readme for
WebSphere InterChange Server and Toolset Fix Pack 4.3.0.1

 

COMPLETED CHANGE REQUESTS

PREREQUISITES

UPGRADE INSTRUCTIONS

TABLE OF INSTALLED FILES

UNINSTALL INSTRUCTIONS

 

 

Completed Change Requests

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

InterChange Server changes

APAR Problem tracking numbers

As of Version

Problem

JR20002 (CR60364)

4.3.0.1 

ICS hangs doing inplace migration from 4.1.1.9 to 4.3

JR21648 (CR60959)

4.3.0.1

Dynamic property change in a collabgroup corrupts all collabs in 4.3.0 (CR37770)

JR21666(CR60367)

4.3.0.1

4.2.2 failed flows do not migrate for hierarchical BO's to version 4.3

JR21667(CR60655)

4.3.0.1

ics_manager -stopgraceful -u... -p... not working 

JR21668(CR62007)

4.3.0.1

ics_manager -start does not prevent second instance to start

 JR21669(CR45667)

4.3.0.1

Email.jar can't be deployed

JR21656(CR45754)

4.3.0.1

ICS will shutdown immediately after reply success in destination VTC.

JR20027 (CR60416)

4.3.0.1

ICS log reports "[Mesg:XML Exception:UTF8]" after adapter bind

  

  

InterChange Server changes included from previous releases

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.

32728

4.2.2.4

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

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.

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

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.

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.

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

32096,34310

4.2.2.4

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

33530,33602,34992,42216,58551

4.2.2.4

Incorrect values are reported for collaboration and connector statistics.

35295

4.2.2.4

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

35933

4.2.2.4

ICS has memory leaks when used with CSM

60898

4.2.2.5

Installer provided to install server Fix Pack

27261

4.2.2.4

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

60362

4.2.2.4

ADK loosing connection

34598

4.2.2.4

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

37133

4.2.2.4

Collaboration does not return from recovery.

34906

4.2.2.4

Flow Manager:
Eclipse-based Flow Manager is much slower than the C++ version for the following tasks: resubmitting/deleting failed flows.

Just regression test flow manager

59657

4.1.1.13

repos_copy -i makes quotes (') two quotes ('') in the repository

 

 

Toolset changes

 

APAR Problem tracking numbers

As of Version

Problem

JR20837 (CR 61638)

4.3.0.1

Reverse map functionality will crash Map designer in certain cases.

JR20843 (CR 61649)

4.3.0.1

Map Designer - Activity Editor: My Collection is not available for other Collaboration templates.

JR21016 (CR 61981)

4.3.0.1

Configuring InterChange Server with System Manager 4.3 - unable to set multiple email recipients

JR21048 (CR 62182)

4.3.0.1

Performance slowness with Business Object designer 4.3

JR20732 (CR 61342)

4.3.0.1

ICL projects disappear from System Manager

JR19437 (CR 45188)

4.3.0.1

DB Connection properties cannot be configured with Edit Deployment Descriptor functionality

JR19259 (CR 44811)

4.3.0.1

System Monitor 4.3 in Solaris environment - Cannot use 1.3.x ORB with a 1.4.x JDK error

JR19443 (CR 45276)

4.3.0.1

Map Designer: Error in Maths package using temp Objects

JR19141 (CR 44696)

4.3.0.1

Activity Editor did not generate code for “Equal”

JR20299 (CR 60726)

4.3.0.1

Cannot launch Log Viewer by specifying the log file as an argument.

JR19250 (CR 44805)

4.3.0.1

The "iterator" of Business Object Array generate error code in Activity Editor

JR20672 (CR 61190)

4.3.0.1

BO level App-Specific info disappearing on the restart of BO designer

JR19414 (CR 45150)

4.3.0.1

Generated java code in Activity Editor seems incorrect

JR20785 (CR 61561)

4.3.0.1

4.3.0 Web Services client incorrectly reads WSDLs from Expose Collaboration

JR21583 (CR 62251)

4.3.0.1

WSDL From Collaboration with 2 TLOs only creates one operation

JR20779 (CR 61492)

4.3.0.1

Business Object Probes fail during high volume/concurrent events

 

 

Toolset changes included from previous releases

Problem tracking numbers

As of Version

Problem

35774

4.2.2.5

FlowManager was hanging when a find operation was performed against 1000's of records. The 'event number' column was not resizeable in the resulting tabular view. This CR fixes both the problems.

43925

4.2.2.5

The MQ HOST_NAME was not allowed to be blank. This fix will allow the hostname to be set to a blank value.

44314

4.2.2.5

When BO's were saved from LogViewer the closing tag, '>' was missing in the created file. This problem is fixed now. The created BO's can be opened properly.

44394

4.2.2.5

In System Manager right click on a collaboration and expose it as a webservice. When this webservice is imported into WSAD5.1, it gives an error because the System Manager missed a couple of tags in the generated xml file correponding to the collaboration. This fix solves that problem.

59991

4.2.2.5

While editing static relationship in Relationship Manager, the original value disappears when we switch to a different row and come back.

60249

4.2.2.5

The Connector Configurator could not load App properties template file when the user uses it to open an existing connector file. This will result in potential problems such as Connector Configurator not knowing any useful info (for example valid values, and length limitation for a String type property) which are configured in App properties template file. The fix will enable Connector Configurator to load its corresponding App properties template file while opening an existing connector file.

44866

4.2.2.5

The changes made to Relationships using Relationship Designer was not reflected when seen through System Manager. If a relation is changed from Static to Dynamic, it'll be shown under correct folder now after the fix.

44907

4.2.2.5

In Connector Configurator when a user wants to set a range for a Connector-Specific property whose type is Time, the two border values of this range should comply with the format of time ie.. hh:mm and should not be random values. This fix implements that validation.

44908

4.2.2.5

In Connector Configurator the Connector-specific property whose type is Time should validate the Range of values. Previously even after setting a specific Range, the property was allowing entry of values outside of the range. Now this fix validates the values to fall within the set Range

44909

4.2.2.5

In Connector Configurator the Connector-Specific property whose type is int, should allow only values set between the range. This fix validates the range and does not allow for entry of values outside the configured range.

 58757

4.2.2.5

Recurring Events should not be shown as expired events. This fix solves that problem

 44384

4.2.2.5

In system manager, when you right click a user project and choose to deploy to WAS, and you choose "Export to a Directory",
the moment you start typing "c:", a error message pops up saying: "c: already exists, do you want to overwrite it?". That error handling needs to be moved to only run after the user finishes typing the whole path and clicks FINISH. This fix solves that problem

58623

4.2.2.5

 When a subdirectory is created in the directory where all the BOs of a component library are stored (usually %CROSSWORLDS%\Tools\WSWB203\Workspace\<your_ICL>\BusinessObjects, and you run "refresh view" in SystemManager and start BO Designer afterwards out of SystemManager, it will crash with a C++ error. This fix solves that problem

 58943

4.2.2.5

If System Manager disconnects from an InterchangeServer and tries to reconnect after PersistentNameServer and ICS have been restarted, System Manager gets an exception - org.omg.CORBA.OBJECT_NOT_EXIST:BAD_SERVER_ID:

 58626

4.2.2.5

If a subdirectory was created under %Crossworlds%\Tools\WSWB203\Workspace\<ICL>\BusinessObjects folder, the process designer did not allow choosing of BO in collaboration template. This fix will solve that problem.

 59596

4.2.2.5

In System Manager, System view does not refresh itself when the ICS is stopped\shutdown. The System View reflects the status of ICS properly only after the System Manager is closed and reopened. This fix solves that problem.

 60746

4.2.2.5

The current flowmanager does not have confirm delete as a default setting. This fix makes it default.

 45082

4.2.2.5

This fix will force the Connector Configurator to adopt the time format of 24-hour. This will avoid those potential errors caused by different locale's time format configuration

44868

4.2.2.5

The Flow Manager does not delete server and user that were deleted through the Option Window - The dialog that comes up when option button is clicked. Now this fix solves that problem.

61100

4.2.2.5

In system Manager while importing components from ICS into a project the progress bar was not working. This fix solves that problem.

44380

4.2.2.4

Connector Configurator/System Manager :
The MaxEventCapacity property of a connector was not validated in the range from 1 to 2147483647 in both Connector Configurator as well as the Property dialog of a connector in the Server Component view.  Consequently, the invalid values of "blank" and zero of this property were entered without an warning or error message.
Fixing notes: The MaxEventCapacity property is validated in range >  0 and <= 2147483647 in both Connector Configurator and System Manager.

43976

4.2.2.4

Business Object Designer:
A Integration Component Libraries (ICL) project  that had been already deleted  in System Manager still existed in  in the left panel of Business Object  Designer, even after invoking Refresh action.
Fixing notes: By applying Refresh action., all ICL projects that has no longer existed in System Manger disappear from Business Object Designer.

42501

4.2.2.4

System Manager:
Problem occurs when exporting solution using a user-defined (non-default) directory. Part of a solution is still exported to the default directory and later can not be found. 
Fixed path to export complete solution in a user-defined directory.

42169

4.2.2.4

Connector Configurator:
"Save as" in Connector Configurator does not work normally:
When user open a connector and save it to project as a new connector, the configurator system will create a new CXRConnectorXML instance which should have the new connector properties, but the pConnector still point to the old CXRConnectorXML instance.  When we change the GUI properties, they will be put to the old CXRConnectorXML instance. When user save the new connector again, pDoc will get the new CXRConnectorXML instance which has no change. So user looks lost his updates.

42134

4.2.2.4

Map Designer:
Maps saved with names > 76 chars cannot be deployed.
Fixing notes: The MapDesigner was checking for 80 characters as the limit for map names. It has been changed to 76 characters to be in sync with the ICS.

37765

4.2.2.4

Activity Editor:
When doing Business object (BusObj) assignments, Activity Editor generates code that uses the BusObj.setContent() to assign the value of one business object to another business object.  However, the BusObj.setContent() method do only a shallow copying and will make the destination business object and the source business object share the underlying content.  Thus, after the assignment, any further change in the source business object will also reflect in the destination business object.  This would cause a problem for a synchronous collaboration if the triggeringBusObj is changed after assignment.  This fix will replace the API that is used for business object assignment from BusObj.setContent() to BusObj.copy(), which will do a full copy of the underlying business object values.

37373

4.2.2.4

Repos Copy:
The issue  was the import from a repository jar file was failing when a collaboration Template's message files were named without locale as the suffix.
For example, if a Template was named WrapperFoundation , it had corresponding entries in a repository jar file when exported out of the server or System Manager:
1)WrapperFoundation.cwt
2)WrapperFoundation.java
3) one or more WrapperFoundation_en_US.txt (i.e. WrapperFoundation<locale>.txt files).
Some customers had repositories where the message files were named WrapperFoundation.txt without <locale> suffix.
The SystemManager was failing when the user tries to import this jar into an Integrated Component Library.
The Server was also failing when we repos_copy into the server.
Fixing notes: this fix is on the Tools side and will allow the user to import the jar into an ICL.  The Server side fix, which allows the user to import (repos_copy) the jar file into the server,  belongs to the Server side.

36851

4.2.2.4

System Manager:
Unable to create part error in ICS System View 4.2.2.2.
Fixing notes: Overflow occurred when integer type was used to store time values. Replaced integer types with long types so that overflow doesn't occur.

36393

4.2.2.4

System Manager/Properties:
When a connector has many Supported BOs and maps (on the order of 100) it takes a long time (180 seconds) to display the dynamic properties in System Manager.  During this time, the ICS experiences 100% CPU usage. Customers typically need to access this window on a production system in order to change log/trace settings or flow settings for the connector.
Fixing notes:  When user need display or change log/trace settings of a connector properties, the dynamic properties of the connector will be displayed in system manager faster than before. When users click Associated Map tab of the connector properties dialog, the response time will be long to load its supported BOs and maps.

36078

4.2.2.4

Business Object Designer:
Business Object Designer automatically fixes attributes with MaxLength = 0 to MaxLength = 255. This fix is to turn off this behavior but still requires a manual change from users:
1) Open file %CROSSWORLDS%\bin\cwtools.cfg
2) Add the following segment at the end of this file:
    [preferences]
    AllowZeroLengthAttr = true

Fixing notes: This is a preliminary fix and the implementation may change later on (e.g. instead of editing cwtools.cfg you'll have to use the UI).

35677

4.2.2.4

Connector Configurator:
Exception occurs when saving to project after switching brokers:
When user switches a connector's broker type from WMQI to WAS or from WAS to WMQI, an exception will occur. This will prevent user from switching a  connector's broker type between WMQI and WAS once this connector has been created.

35029

4.2.2.4

Dashboard:
In System Monitor if changing the Display items for a table and having the Refresh Rate in 'Set Options' set to greater then 0, then the auto refresh would not work properly. This has been fixed.

34906

4.2.2.4

Flow Manager:
Eclipse-based Flow Manager is much slower than the C++ version for the following tasks: resubmitting/deleting failed flows. Just Regression test this CR.

34342

4.2.2.4

Business Object Designer:
Business Object Designer isn't showing the child business object's application specific information (ASI) properly.

34184

4.2.2.4

Map Designer:
Map Designer join dialog cannot display long attribute name.
Fixing notes: The cells that display the attribute name are provided with cursors to move to the invisible area. Tool tip is also provided to see the entire string.

33735

4.2.2.4

SNMP:
SNMP manager does not receive the host name from the SNMP agent.
The traps sent out by the SNMP Agent did not contain the correct origination host name of the trap.  The origination host name for traps are all set to "localhost", which results in whatever machine name the network manager is on to be displayed.  The correct origination host name of the trap should be the host name that the SNMP Agent is running on.  This has been fixed in the 4.2.2.3 patch.

32841

4.2.2.4

System Manager:
When there is more than one GBO in the collaboration ( the map names are explicitly bound in the connector)  the Tree and the graphical views in the SM show the incorrect map name for the collaboration.

 

 

Prerequisites

 

1.      You must have version 4.3.0 of WebSphere InterChange Server and/or Toolset installed in order to install this fix pack.

2.      You must install the Fix Pack to both the WebSphere InterChange Server and Toolset installations.

 

Upgrade Instructions 

 

Installer restriction for AIX, HP-UX, and Solaris:

To install this fix pack on AIX, HP_UX, or Solaris you must install from the same user that was used to install the base WebSphere InterChange Server 4.3.0 product.

 

Installer restriction for Solaris:

To install this fix pack on Solaris you must not install from the root user.

 

 

To apply this Fix Pack on a Windows system:

1.      The Fix Pack Installer for Windows is a combined installer for both InterChange Server and Toolset Fix Pack 4.3.0.1.  The installer will apply the fix pack for the InterChange Server or Toolset or both depending on what you have installed.

2.      If both server and Toolset are installed on the same system they must have been installed to the same directory.

3.      Shut down the InterChange Server if it is installed and running on the same system.

4.      Back up the files listed in the table below for the InterChange Server or Toolset or both depending on what you have installed.  This enables the fix pack to be uninstalled.

5.      Download and run the fix pack Installer

To apply this Fix Pack on a Unix or Linux system:

1.      Restriction: to install this fix pack on Unix or Linux, you must install from the same user that was used to install the base WebSphere InterChange Server 4.3.0 product.

2.      The Fix Pack Installer for Unix and Linux systems is for InterChange Server only since the Toolset is not supported on these systems.

3.      Shut down the InterChange Server if it is running.

4.      Back up the files listed in the table below for the InterChange Server. This enables the fix pack to be uninstalled.

5.      Download and run the Fix pack Installer corresponding to the Operating System on which the InterChange Server is installed.

Table of InterChange Server files installed by this fix pack

Platform [Win32;Solaris;AIX;HP_UX;XLINUX]

Add / Replace / Remove

File (Starting from WICS installation directory)

Associated Feature

(File is installed only if the associated feature was installed)

Win32:Solaris:AIX:HP_UX :XLINUX

Replace

bin/CC001616J040300.sys

Server

Win32:Solaris:AIX:HP_UX

Replace

bin/CC000976J040300.sys

ICSAccess for EJB

Win32:Solaris:AIX:HP_UX

Replace

bin/CC001133J040300.sys

ICSAccess

Win32:Solaris:AIX:HP_UX

Replace

bin/CC001351J040300.sys

ICSAccess for Connectors

Win32:Solaris:AIX:HP_UX :XLINUX

Replace

lib/CrossWorlds.jar     

Server

Win32:Solaris:AIX:HP_UX :XLINUX

Replace

lib/datamanager.jar 

Server

Win32:Solaris:AIX:HP_UX :XLINUX

Replace

repository/Email.jar

Server

Solaris:AIX:HP_UX :XLINUX

Replace

bin/ics_manager

Server

Win32:Solaris:AIX:HP_UX :XLINUX

Replace

jre

Server

Win32:AIX

Replace

copyright

Server

Win32:XLINUX

Replace

docs

Server

AIX

Replace

license

Server

Win32:Solaris:AIX:HP_UX :XLINUX

Replace

WBSM/CWDashboard.war

Server

Win32:Solaris:AIX:HP_UX :XLINUX

Replace

WBFEM/WAS/FailedEvents.war

Server

Win32:Solaris:AIX:HP_UX :XLINUX

Replace

WBFEM/WAS/FailedEvents.war

Server

Win32:Solaris:AIX:HP_UX :XLINUX

Replace

WBFEM/FailedEvents.jar

Server

 

 

 Table of Toolset files installed by this fix pack – For Windows installations only:

Win32

Replace

bin/Data/Std/StdConnProps.xml

Tools

Win32

Replace

bin/Data/Std/StdConnProps_chs_chn.xml

Tools

Win32

Replace

bin/Data/Std/StdConnProps_cht_twn.xml

Tools

Win32

Replace

bin/Data/Std/StdConnProps_deu_deu.xml

Tools

Win32

Replace

bin/Data/Std/StdConnProps_esn_esp.xml

Tools

Win32

Replace

bin/Data/Std/StdConnProps_fra_fra.xml

Tools

Win32

Replace

bin/Data/Std/StdConnProps_ita_ita.xml

Tools

Win32

Replace

bin/Data/Std/StdConnProps_jpn_jpn.xml

Tools

Win32

Replace

bin/Data/Std/StdConnProps_kor_kor.xml

Tools

Win32

Replace

bin/Data/Std/StdConnProps_ptb_bra.xml

Tools

Win32

Replace

bin/BusObjDesigner.exe

Tools

Win32

Replace

bin/ConnDesigner.exe

Tools

Win32

Replace

bin/MapDesigner.exe

Tools

Win32

Replace

bin/LogViewer.exe

Tools

Win32

Replace

bin/ProcessDesigner.exe

Tools

Win32

Replace

bin/enu_usa/ConnDesignerRes.dll

Tools

Win32

Replace

bin/chs_chn/ConnDesignerRes.dll

Tools

Win32

Replace

bin/fra_fra/ConnDesignerRes.dll

Tools

Win32

Replace

bin/jpn_jpn/ConnDesignerRes.dll

Tools

Win32

Replace

bin/cht_twn/ConnDesignerRes.dll

Tools

Win32

Replace

bin/ita_ita/ConnDesignerRes.dll

Tools

Win32

Replace

bin/deu_deu/ConnDesignerRes.dll

Tools

Win32

Replace

bin/esn_esp/ConnDesignerRes.dll

Tools

Win32

Replace

bin/ptb_bra/ConnDesignerRes.dll

Tools

Win32

Replace

bin/kor_kor/ConnDesignerRes.dll

Tools

Win32

Replace

bin/enu_usa/ProcessDesignerRes.dll

Tools

Win32

Replace

bin/chs_chn/ProcessDesignerRes.dll

Tools

Win32

Replace

bin/fra_fra/ProcessDesignerRes.dll

Tools

Win32

Replace

bin/jpn_jpn/ProcessDesignerRes.dll

Tools

Win32

Replace

bin/cht_twn/ProcessDesignerRes.dll

Tools

Win32

Replace

bin/ita_ita/ProcessDesignerRes.dll

Tools

Win32

Replace

bin/deu_deu/ProcessDesignerRes.dll

Tools

Win32

Replace

bin/esn_esp/ProcessDesignerRes.dll

Tools

Win32

Replace

bin/ptb_bra/ProcessDesignerRes.dll

Tools

Win32

Replace

bin/kor_kor/ProcessDesignerRes.dll

Tools

Win32

Replace

bin/Utils.dll

Tools

Win32

Replace

bin/ActivityEditor.dll

Tools

Win32

Replace

bin/CxCommon2.dll

Tools

Win32

Replace

bin/ServerConnection.dll

Tools

Win32

Replace

bin/XRmi.dll

Tools

Win32

Replace

bin/SMInterface.dll

Tools

Win32

Replace

bin/CC001224W040300.sys

Tools

Win32

Replace

lib/CrossWorlds.jar

Tools

Win32

Replace

lib/datamanager.jar

Tools

Win32

Replace

lib/ConfigWizard.jar

Tools

Win32

Replace

lib/flowmanager.jar

Tools

Win32

Replace

lib/relmgr.jar

Tools

Win32

Replace

lib/vtc.jar

Tools

Win32

Replace

Tools/eclipse/plugins/com.ibm.btools.csm

Tools

Win32

Replace

Tools/eclipse/plugins/com.ibm.btools.itools.common

Tools

Win32

Replace

Tools/eclipse/plugins/com.ibm.btools.itools.codeGen

Tools

Win32

Replace

Tools/eclipse/plugins/com.ibm.btools.itools.ae.settings

Tools

Win32

Replace

Tools/eclipse/plugins/com.ibm.btools.itools.cwconverter

Tools

Win32

Replace

Tools/eclipse/plugins/com.ibm.btools.itools.datamanager

Tools

Win32

Replace

Tools/eclipse/plugins/com.ibm.btools.itools.msg.importer

Tools

Win32

Replace

Tools/eclipse/plugins/com.ibm.btools.itools.collaboration.debugger

Tools

Win32

Replace

Tools/eclipse/plugins/com.ibm.btools.itools.testingenv

Tools

Win32

Replace

Tools/eclipse/plugins/com.ibm.btools.itools.wsdlgen

Tools

Win32

Replace

Tools/eclipse/plugins/com.ibm.btools.adaptermonitor

Tools

Win32

Replace

Tools/eclipse/plugins/com.ibm.btools.bdm

Tools

Win32

Replace

Tools/eclipse/plugins/com.ibm.btools.dashboard.assemblewizard

Tools

 

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. You must uninstall the fix pack on both InterChange Server and Toolset installations.

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