Fix Pack Notes for
WebSphere Business Integration (WBI) Toolset version 4.2.1.6

The patch notes contain the following sections: 
 
COMPLETED CHANGE REQUESTS

UPGRADE INSTRUCTIONS

ADDITIONAL DISCUSSION

UNINSTALL INSTRUCTIONS

COMPLETED CHANGE REQUESTS

This patch contains fixes for the following CRs based on customer reported and internally discovered issues.
 
CR Number
As of Version
Problem
41918(a.k.a. 33731)
4.2.1.6
System Manager: 
In the Edit Configuration editor of the System Manager, the name of a log file/trace file was not appropriately validated to exclude 9 characters \ / : * ? " < > | 
Fixing notes : because the text field that accept the name of the log file/trace file allows a full path of the log file to be entered (e.g. C:\temp\logfile.txt)  and so this fix cannot be validated against two characters \ and /.   The name of the log file/trace file is correctly validated not to contain characters such as : * ? " < > and |
34367
4.2.1.6
Connector Designer:  
Once-supported business objects and maps remain in the configuration file, causing dependency errors during project validation.  After applying this fix, maps associated to previously supported business objects will be removed as the file is saved.  Also, when a supported business object is deleted from the "Supported Business Objects" tab, its associated map will be removed.  The updated configuration file will pass validation.
33735
4.2.1.6
SNMP Agent:
The SNMP Agent was sending out traps with no useful information of where the traps originated from.  More specifically, the traps appened 127.0.0.1 as their origination host.  This fix made it so that the traps contain the SNMP Agent's IP Address so that receivers can determine where the traps came from. 
33301
4.2.1.6
Business Object Designer:
In the BO designer, in the left hand pane, the projects and the BOs are not in any sorted order.  They should be sorted alphabetically or by some other method. 
The fix makes projects and bo names sorted in a case-insensitive alphabetical order
33110
4.2.1.6
Map Designer:
When certain maps were opened with the preference 'validate map when open' set on the Map Designer, the Java code was not visible for transformation rules with incorrect attribute information. This bug has been fixed.
33095
4.2.1.6
Business Object Designer:
The BO Designer invokes a JVM to save BOs. This JVM was previously not tuned for large repositories. As of 4.2.1.6 the JVM was tuned to support at least 1000 bos.
32682
4.2.1.6
Process Designer:
Create collaboration template where start node immediately precedes decision node.  Have the node branch to 2 different action nodes.  Save the template and check out the java code - you'll see that the switch statement does not include the second branch because the start node automatically branches to the next node.  However, this behavior would be incorrect if the initial boolean value of the decision var was supposed to go to the next node after that. 
Fixing Notes: Connection between a start node and a decision node was disallowed.
32427
4.2.1.6
System Manager:
In the ServerComponent management section of the System Manager, when trying to change the PollFrequency in connector properties dialog only integer value can be set.
- seems to expect integer value only.
Fixed In fixed dialog PollFrequency can be set to integer, “key” and “no”.
23957
4.2.1.6
Log Viewer: 
While displaying a file in LogViewer, a customer selected "Edit --> Preferences" to display the User Configuration Options window. On this window the customer selected the "Columns" tab. The customer reordered the visible columns and clicked OK.  The order of the column data changed, but the column headings remained the same.
After applying this patch, the column headings will stay in sync with the column data.
32300
4.2.1.5
System Manager: 
Collaboration graphical view displays incorrect binding of incoming maps.
Fixing notes : If there are multiple incoming maps, collaboration view shows only one map. The fix has been made to display all the incoming maps in the tooltip of the map icon. Also, Edit definitions or properties menu item will bring up a selection dialog that will list all the incoming maps.
31874 (a.k.a. 22695)
4.2.1.5
Business Object Designer: 
Attributes of a business object definition, after saved in a file of type ".xls Spreadsheet", were not displayed correctly in Microsoft Excel. 
The fix has been made to correctly save business object attributes in a xls file.
30615
4.2.1.5
System Manager:
In Interchange Server Component Management, if user right-clicks and chooses properties for items on the server, e.g. for a connector, only the first 32 maps are shown, even though the connector can have more.   Fixed property dialog so that it can display  more than 32 items.
28820
4.2.1.5
Process Designer: 
BO Probes can generate very long names even under normal circumstances.  The problem is that in the repository CXREPOSBLOBS table the "ID" field has a maximum length of 80.
Fixing notes: Since the ID column length is restricted to 80 characters, we cannot change it.  Currently the probe ID is constructed with three parts, separated by a dot ("."):
collaboration_name.probe_link_id.current_millisecond
where "current_millisecond" is around 14 characters.  That leaves us 64 characters to work with.  Previously, the generated probe link ID is in the format "BOProbe.LinkTransition_37".  Now the Process Designer will shorten the generated probe link ID as much as possible, (i.e. in the format "BP1234"), so that leaves collaboration_name a maximum of 58 characters. If the user wants to use probe in their collaboration, their collaboration name cannot be longer than 58 characters.
27426
4.2.1.5
Process Designer: 
In the process designer user can create an action node with two service calls attached.  Saving and compiling work fine without any error message. But when user looks into the generated code it is only generated for the first service call that was attached to the action node.
Fixing notes:  As we do not support connecting two service calls to an action node at server/code generation level, we removed the support at the designer level too. So now onwards user can not connect more than one service call to an action node.
For an existing template that had this situation already designed in, on opening that diagram in Process Designer, one service call will be disconnected from the action node. On Closing that diagram, user will be prompted to save the changes made.
26726
4.2.1.5
Connector Designer: 
If an already available connector configuration was changed via Connector Configurator and saved as a new connector, the properties CW:NAME in CW:ConfigurationInfo and in CW:header in the .cfg file were not being updated.  After applying this patch, these properties will be updated as the file is being saved.
25674
4.2.1.5
System Manager:
The System Manager DOS window stays open once the System Manager application window comes up (using startcsm.bat).   The fix has been made to close the DOS window when System Manager comes up.
24901
4.2.1.5
Activity Editor: 
In Activity Editor, when multiple graphical components are selected on the canvas, only one of the selected component is moved by using the mouse; the other selected components are not moved.
After the fix,  multiple selected graphical components can be moved together by holding down the CTRL key as moving.
23813
4.2.1.5
Process Designer: 
In Process Designer, dragging a toolbar button into the workspace using  ALT + LEFT Mouse down, will remove the button from the toolbar.  There is no way to restore that button onto the toolbar again.
Fixed the bug by disabling the drag and drop action on the toolbar buttons.
23114
4.2.1.5
Process Designer: 
In Process Designer,  the "Advanced..." button is not initially visible in the Service Call properties dialog.  However, the window can be resized to show the hidden button.  This occurs only under the Windows Large Fonts setting. This can be set using Windows->Display Properties->General->Large Fonts.
Fixed the bug by making sure the dialog will be sized to fit the advanced button by default.
29111
4.2.1.4
Activity Editor: 
In a graphical activity, if a constant is declared to contain space characters " " only, then the generated Java code will trim the text and initialize the constant to null instead of the space characters.
Fixed code generation in order to prevent  trimming the value specified in activity 
constants.  The activity constant can now be initialized to space characters " ".
28699
4.2.1.4
Connector Designer:  
Customers ran into a problem where once-supported business objects and maps are not getting removed from the connector definition.  Therefore, dependency errors were thrown when trying to validate the project.  
After applying this fix, the customers will be able to delete selected business objects.  When the connector configuration file is re-saved, maps associated with the deleted business objects will be removed from the configuration file automatically.  The updated configuration file will pass when validation is checked and/or when the configuration is deployed.
26433
4.2.1.4
Activity Editor: 
In Activity Editor, when the "condition" function block is used, the initalization and assignment of port variables are put outside the condition scoop, which creates a problem for using temporary variable for port variables.
Fixed code generation to put the initalization and assignment of port variables in the scoop of the condition statement. (i.e.  inside the "if(..){...} else {...} constructs).
27849
4.2.1.3
Business Object Designer: 
For some BO projects with complex inter-dependencies, the BO Designer crashed when saving high level BOs. In particular, the BO Designer crashed when it was either not modified or had a modified sub-BO very low in the project hierarchy. The fixed consisted in replacing a recursive traversal of modified BOs with a linear stack traversal.
27504
4.2.1.3
Business Object Designer: 
An incorrect namespace of application specific information in the structure of BO schemas prevented the application specific information to be deployed to the server.  The namespace has been modified to make the deployment succeeded.
27091
4.2.1.3
Process Designer: 
In Process Designer for a collaboration template, the user cannot uncheck a 
compensation service call and have it stay that way.  If the user unchecks it, 
clicks "Apply", then closes, it is still unchecked when the user goes back in to the 
service call properties.  If the user saves the template, closes Process 
Designer, and opens it back up, the compensation service call is checked 
again. 
Fixed the bug by making sure that Process Designer is saving the modified service call properties properly.
25953
4.2.1.3
Business Object Designer: 
An error in the structure of BO schemas prevented them from successful deployment to the server. In particular, this created inconsistencies in the application specific information of BOs. The error was fixed and BOs should work as expected.
25121
4.2.1.2
Map Designer :
In a map that was created in release 3.1.2, in some cases, the "Set Value" transformation rule will not upgrade properly to 4.2.x versions.  This problem occurrs when the map is defined in 3.1.2 release, if the transformation rule is originally defined as "Move", "Join", "Split" or "Submap", then without deleting the transformation rule, define a "Set Value" transformation rule on top of the existing transformation rule.   In this case, the map is not associating the new "Set value" transformation rule with the destination attribute.  So after the map is upgraded to 4.2.x versions, the map shows the transformation rule as the original type (i.e. Move) instead of "Set Value" type, and when map is recompiled, it will generate code that will transform as the original rule does (i.e. code for "Move" is generated).

Fixing notes:
Since the problem was with the original 3.1.2 map in that the map itself did not save the "Set Value" information correctly, the workaround for this problem is provided as follows:
With this patch, if the problem is detected in maps, the following section can be added to the file "cwtools.cfg" in the WBI tools installation directory at  "<InstallationDirectory>\bin":

    [MapsUpgrade]
    AutoUpgradeOperations=no

After adding these two lines to the end of the "cwtools.cfg" file, when the maps are imported from ICS server for upgrade, ALL map transformation rules will be modified to be user-customized -- this will make the map to compile with the java code fragments that was generated in 3.1.2, thus allowing the "Set Value" and all other transformation rules work the same as in release 3.1.2.

WARNING:  with the flag " AutoUpgradeOperations" set to "no", upgrade for all the maps will be affected.  This means that the upgraded map will always use the Java code fragment that was generated with the map when the transformation rule is created and that these java code for the transformation rules will not be automatically upgraded in future releases.  Please use this setting with care.

24775 (a.k.a. 24783)
4.2.1.2
Activity Editor:
When an activity is saved, if the scrollbar is not at the original position, then the activity node's position is not saved properly, and so when the activity is reopened, the node may not be shown in the canvas.

Fixing notes:
Activity Editor is fixed to save the node's position with regard to the scroll position.  Also, node location checking is added --  when an activity is opened, Activity Editor will check to make sure that no object should be located outside of scrollable areas.  If any object is located outside of the viewable area (as is possible if the activity is created before this CR is fixed), then activity editor will adjust the node's position to display it at the nearest viewable location. 
Related to this is that "paste" of nodes in the activity canvas is also fixed.   Nodes will be pasted within the scrolled display area.  If the cursor is within the display area, nodes will be pasted at the cursor's location.  Otherwise, if the cursor is not currently in the display area, objects will be pasted beginning at the upper left corner of the current display area.

24568
4.2.1.2
SNMP: 
The SNMP Agent was causing memory leak for the WebSphere InterChange Server and itself. 
The fixing makes sure that there would not be any infinite growth in memory usage.
22935
4.2.1.1
System Manager : 
The System Manager was crashing by going out of available Memory 
a) When the user tries to delete a component from a project, 
b) When the user tries to deploy a large Repository to the Server. 
c) When the user tries to export a large Repository to a Repository Jar file. 
d) When the user tries to find the references or dependencies of a particular component by  right-clicking a component and choosing "Show dependencies", "Show References".. 
Fixing notes: 
The fix has been tested with projects imported from Repository Jar files of up to 9MB size.  In case the customer has a bigger repository, it may be needed to be deployed as two packages instead of a single package. 
In case the deployment to an active server fails, the customer can export the project to a Repository file(*.jar files) and then repos copy "in" the jar file using the "Repos_Copy" command line utility.
24880
4.2.1.1
Business Object Designer:
Business Object Designer did not adapt any App Spec Info of some business object with a length greater than 225 characters.

Fixing notes:
Business Object Designer expands the App Spec Info length to 4000 characters.

UPGRADE INSTRUCTIONS 

Before applying this patch, it is highly recommended that  you backup the %CROSSWORLDS%/bin, %CROSSWORLDS%/lib, %CROSSWORLDS%/WBSM and %WSWB_PATH%/plugins folders (e.g.  C:\IBM\WebSphereICS\Tools\WSWB203\plugins).  In the case you want to uninstall the patch, replace those folders with the backups.

To perform an upgrade to this version of the WBI Toolset, please follow instructions in the correct order as follows:

  1. Make sure that you have InterChange Server  and Toolset version 4.2.1  installed.
  2. Update to the InterChange Server fix pack version 4.2.1.6 or later.
  3. Run the attached exe file (e.g. 4216_toolset_patch.exe).   Please notice that in the second step of the installing wizard, by default the installer enters the value of variable %CROSSWORLDS% as an installing directory name.  If you installed WBI ICS and Toolset version 4.2.1 at another location, use the Browse button to select the correct location.  The installer will do all installing work for you. 
Note that the path name "C:\IBM\WebSphereICS"assumes that IBM WebSphere Business Integration Toolset has been installed under an IBM WebSphere InterChange Server directory on the C drive. 

Below are a list of files that need to be replaced in this patch:
 
For WICS Version
Platform [Windows]
Add / Replace / Remove
File (Starting from ~/IBM/WebSphereICS/
4.2.1.6
Windows 2000 Replace
bin/startcsm.bat
4.2.1.6 Windows 2000 Replace bin/BusObjDesigner.exe
4.2.1.6 Windows 2000 Replace bin/ConnDesigner.exe
4.2.1.6 Windows 2000 Replace bin/FlowManager.exe
4.2.1.6 Windows 2000 Replace bin/LogViewer.exe
4.2.1.6 Windows 2000 Replace bin/MapDesigner.exe
4.2.1.6 Windows 2000 Replace bin/MapToXML.exe
4.2.1.6 Windows 2000 Replace bin/DiagToXML.exe
4.2.1.6 Windows 2000 Replace bin/ProcessDesigner.exe
4.2.1.6 Windows 2000 Replace bin/RelationshipDesigner.exe
4.2.1.6 Windows 2000 Replace bin/RelationshipManager.exe
4.2.1.6 Windows 2000 Replace bin/Monitor.exe
4.2.1.6 Windows 2000 Replace bin/Castor.exe
4.2.1.6
Windows 2000 Replace
bin/enu_usa/BusObjDesignerRes.dll
4.2.1.6
Windows 2000 Replace
bin/chs_chn/BusObjDesignerRes.dll
4.2.1.6 Windows 2000 Replace bin/fra_fra/BusObjDesignerRes.dll
4.2.1.6 Windows 2000 Replace bin/jpn_jpn/BusObjDesignerRes.dll
4.2.1.6 Windows 2000 Replace bin/cht_twn/BusObjDesignerRes.dll
4.2.1.6 Windows 2000 Replace bin/ita_ita/BusObjDesignerRes.dll
4.2.1.6 Windows 2000 Replace bin/deu_deu/BusObjDesignerRes.dll
4.2.1.6 Windows 2000 Replace bin/esn_esp/BusObjDesignerRes.dll
4.2.1.6 Windows 2000 Replace bin/ptb_bra/BusObjDesignerRes.dll
4.2.1.6 Windows 2000 Replace bin/kor_kor/BusObjDesignerRes.dll
4.2.1.6
Windows 2000 Replace
bin/CxCommon2.dll
4.2.1.6
Windows 2000 Replace
bin/SvrIFace2.dll
4.2.1.6 Windows 2000 Replace bin/CxCommon.dll
4.2.1.6 Windows 2000 Replace bin/SvrIFace.dll
4.2.1.6
Windows 2000 Replace
bin/Utils.dll
4.2.1.6 Windows 2000 Replace bin/Utils411.dll
4.2.1.6
Windows 2000 Replace
bin/XRmi.dll
4.2.1.6 Windows 2000 Replace bin/ActivityEditor.dll
4.2.1.6 Windows 2000 Replace bin/ServerConnection.dll
4.2.1.6 Windows 2000 Replace lib/datamanager.jar
4.2.1.6 Windows 2000 Replace lib/xrmi.jar
4.2.1.6 Windows 2000 Replace lib/cwsnmpagent.jar
4.2.1.6 Windows 2000 Replace bin/cwconverter/cwconverter.jar
4.2.1.6 Windows 2000 Replace bin/cwconverter/cwconverter.bat
4.2.1.6 Windows 2000 Replace bin/cwconverter/com.ibm.btools.itools.cwconverter/xsls/CWM4_42/CWM4_42.xsl
4.2.1.6 Windows 2000 Replace WBSM/CWDashboard.war
4.2.1.6
Windows 2000 Replace
plugins/com.ibm.btools.csm
4.2.1.6
Windows 2000 Replace
plugins/com.ibm.btools.ics.tools
4.2.1.6 Windows 2000 Replace plugins/com.ibm.btools.itools.codeGen
4.2.1.6
Windows 2000 Replace
plugins/com.ibm.btools.itools.cwconverter
4.2.1.6
Windows 2000 Replace
plugins/com.ibm.btools.itools.datamanager

ADDITIONAL DISCUSSION




UNINSTALL INSTRUCTIONS

In part UPGRADE INSTRUCTIONS, you are recommended to backup the %CROSSWORLDS%/bin, %CROSSWORLDS%/lib, %CROSSWORLDS%/WBSM and %WSWB_PATH%/plugins folders for the purpose of uninstalling the patch.
If you have done the backup process, uninstall the patch by manually replacing the folders with the back-ups.

 

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