Release Notes for WebSphere Business Integration Toolset, Version 4.2.1

These release notes cover release information for WebSphere Business Integration Toolset, Version 4.2.1. They contain the following sections:
New in this release Installation, migration, upgrade, and configuration information
Product fix history Known problems and workarounds
Hardware and software requirements Documentation updates

Note: Important information about this product may be available in Technical Support Flashes issued after these release notes were published. These can be found on the WebSphere Business Integration support Web site, http://www.ibm.com/websphere/integration/wbiserver/support. Select the component area of interest and search the flashes section.

New in this release

The Server Component Management view has been added to System Manager. This view allows you to view and monitor the components on the server.

Product fix history

Between releases 4.2 and 4.2.1 of the toolset, the following CRs, based on customer-reported cases, were fixed.

System Manager

CR
number
Description
18317 If a collaboration is bound to another collaboration, the second collaboration does not reflect the binding in the graphical view. For example, if collaboration A is bound to collaboration B, collaboration A shows the binding in System Manager, but collaboration B does not.This is a refresh problem in System Manager. If both collaborations are open in the graphical view, then the binding is not reflected in the second collaboration.
20199 System Manager cannot disable or enable benchmarks in the server.
21686 Setting the in-transit persistence property in a group collaboration does not propagate that property to the other collaborations.
22091 At a resolution of 800x600 using the Italian locale, the Delete wizard truncates some strings.
22193 Meta-data Management Subsystem (MMS): The shutdown option has no effect. Components continue to be deployed in the shutdown state after deploying in start state.
22368 If the ReplyToQueue connector application-specific property under the application-specific hierarchical property ProtocolListenerFramework > ProtocolListeners > JMS_Listener is empty, then the WSDL Generation component throws an ArrayIndexOutOfBounds exception.

Web-based System Monitor

CR
number
Description
22372 Changing the Default View in the Create and Configure Views tool does not work properly after logoff.

Connector Configurator

CR
number
Problem
20733 Hover help text is in English in all items of the Property column.
22203 No warning message appears for overwriting a connector-specific property template.
You cannot create multiple values of a connector-specific property in the Connector-Specific Properties category.

Business Object Designer

CR
number
Problem
21493 Business objects generated in InterChange Server 4.1.1 by the XMLODA mark the ObjectEventId as the business object key attribute. This is not allowed in InterChange Server 4.2 and Business Object Designer may give numerous validation errors when saving such business objects.

Map Designer

CR
number
Problem
13780 When the "Validate Map When Open" preference option is enabled, Map Designer takes is slow to open up a map that uses large business objects (for example, business objects with more than 1000 attributes).
22064 When using a child business object's verb as the destination attribute of a transformation rule, the child business object must be created before the verb transformation in order for the verb to be assigned correctly in the child business object. The transformation rule in the child business object verb does not create the child business object instance.

SNMP

CR
number
Problem
21928 The SNMP tools, contrary to the other tools, have a set of default documentation shipped with them.

Flow Manager

CR
number
Problem
22117 Flow Manager, version 4.2, cannot resubmit a failed event resulting from canceling the event. When a waiting event is canceled in Flow Manager, the event does not become a failed event immediately; it typically takes few seconds for a waiting event to become a failed event, although it is shown as a failed event in Flow Manager. The error message returned is something like "The request to cancel ... has been accepted. Please check the status later."

Integrated Test Environment

In the previous release, the connector configuration files (*.cfg) had to be located in a path that does not include any spaces. This problem has been fixed.

Hardware and software requirements

Hardware and software requirements are included in the product documentation. See Installation, migration, upgrade, and configuration information for links to those guides.

Installation, migration, upgrade, and configuration information

Whether you are installing the software from the CD or downloading it from Passport Advantage and installing it from a local directory, refer to the System Installation Guide for Windows.

Known problems and workarounds

General

CR
number
Problem
The French character 0x9C might display incorrectly in some tools windows.
18986 Connector Configurator, Business Object Designer, Map Designer, Process Designer, and Relationship Designer show deleted projects in their project lists.

Workaround: Close all designer tools before deleting a project from System Manager.

19283 Do not install WebSphere Business Integration Toolset in a directory with a name that contains word spaces (for example, C:\Program Files).

Workaround: When Installer prompts for a location to install, select a directory that contains no spaces in its name. When you are installing the tools plugins to an existing WebSphere Studio Application Developer Integration Edition (WSADIE) installation, make sure the existing installation directory does not contain spaces in its name.

System Manager

CR
number
Problem
18687 For user-created folders inside a project, System Manager returns an error when creating a collaboration object.

Workaround: Do not add, delete, or modify a project folder outside of System Manager. System Manager maintains the projects in the file system.

21697 Words are truncated in Brazilian Portuguese on the Delete wizard.
22302 If System Manager is not running, the designer tools display an error message while launching, .

Workaround: This is a warning message. Designers need System Manager for working with project information. You cannot work with System Manager projects until System Manager is launched.

Connector Configurator

You cannot create multiple values of a connector-specific property in the Connector-Specific Properties category. You must use the Connector-Specific Property Template wizard to create multiple values of a connector-specific property.

Process Designer

CR
number
Problem
20579 Information about Iterator may be lost in BPEL Import and Export processes.
20719 Asynchronous outbound and inbound service calls are not supported in BPEL Import and Export processes. For synchronous service calls, you might lose information about regular and compensation ports and business objects.
22643 Tangled decision nodes. The decision nodes are tangled when old templates are upgraded to new templates where the branch decision logic is moved from the individual links to a decision node. The problem arises because a decision node is inserted as a new node between action nodes (where there is no space for it). The branch ports are arbitrarily assigned to the outgoing links, which causes additional problems in the shape of the links. However, the branching logic itself is not affected

Workaround: Two new editing features are provided to clean up the appearance of tangled decision nodes:

  • You can swap decision node ports between any two ports by dragging one port to another while holding down the ALT key. This swaps the outgoing links with the underlying condition and exception expressions.
  • The orthogonal attribute of a link forces the shape of the link to toggle between a straight line and the right angled lines. To change the shape of the link, right-click the link and select “Orthogonal” from the menu. Any tangled links can be cleaned up by making them straight (and later orthogonal).
Process Designer allows a decision node to follow a start node, but a decision node should not follow a start node.

Relationship Designer

CR
number
Problem
24762 Relationship Designer might crash when you invoke from System Manager without first selecting an integration library project.

Workaround: Select an integration library project before invoking Relationship Designer from System Manager.

Web-based System Monitor

CR
number
Problem
23569 When creating a new Monitor or View in French, do not use the French character "ś" as part of the Monitor or View names. This character will display as a question mark (?).
23687 The Websphere 5.0.0 Administration Console for Brazilian Portuguese does not allow the configuration of System Monitor.

Workaround: Create and run the configuration script described below.

Note: The line numbers in the following script are used only for reference. They are not part of the script itself. See the explanation of line numbers following the script.

  1. set x [$AdminConfig getid /Node:yournode/]
  2. $AdminConfig create Server $x {{name ICSMonitor}}
  3. $AdminApp install C:/IBM/WebSphereICS/WBSM/CWDashboard.war { -contextroot /ICSMonitor -MapModulesToServers {{CWDashboard CWDashboard.war,WEB-INF/web.xml WebSphere:cell=yourcell,node=yournode,server=ICSMonitor }} -nopreCompileJSPs -installed.ear.destination " C:\Progra~1\WebSphere\AppServer\installedApps\yournode" -distributeApp -nouseMetaDataFromBinary -nodeployejb -appname CWDashboard.war -createMBeansForResources -noreloadEnabled}
  4. set y [$AdminConfig getid /Node:yournode/Server:ICSMonitor/]
  5. set jvm [$AdminConfig list JavaVirtualMachine $y]
  6. $AdminConfig modify $jvm {{classpath {C:\Progra~1\WebSphere\AppServer\installedApps\yournode\CWDashboard.war.ear\CWDashboard.war\WEB-INF\lib\vbjorb.jar;C:\Progra~1\WebSphere\AppServer\installedApps\yournode\CWDashboard.war.ear\CWDashboard.war\WEB-INF\lib\xerces.jar}} {genericJvmArguments {-Dorg.omg.CORBA.ORBClass=com.inprise.vbroker.orb.ORB -Dorg.omg.CORBA.ORBSingletonClass=com.inprise.vbroker.orb.ORBSingleton}}}
  7. $AdminConfig modify $jvm {{systemProperties {{{name DASHBOARD_HOME} {required false} {value "C:\Progra~1\WebSphere\AppServer\installedApps\yournode\CWDashboard.war.ear\CWDashboard.war"}} {{name DASHBOARD_URL} {required false} {value http://yournode.your.url/ICSMonitor}}}}}
  8. $AdminConfig save

Replace the boldface text in the script with values for your local environment. You can check for appropriate values in setupcmdline.bat in the Websphere bin directory. That file includes SET with variables that were set during the WebSphere installation. For example:


SET WAS_HOME=C:\Program Files\WebSphere\AppServer
SET WAS_CELL=Peace
SET WAS_NODE=Peace

Line 1

Set yournode to the server node, the equivalent of WAS_NODE.

Line 2

No change.

Line 3

Change C:/IBM/WebSphereICS to the name of the directory you chose during WebSphere ICS installation (if you took the default you do not need to change this directory).

Change C:\Progra~1\WebSphere\AppServer to the WAS_HOME directory.

Change yourcell to the local cell name, for example, WAS_CELL

Change yournode to the local node name, for example, WAS_NODE.

Line 4

Change yournode to the local node name, for example WAS_NODE.

Line 5

No change.

Line 6

Change C:\Progra~1\WebSphere\AppServer to the WAS_HOME directory.

Change yournode to the local node name, for example, WAS_NODE.

Line 7

Change C:\Progra~1\WebSphere\AppServer to the WAS_HOME directory.

Change yournode.your.url to the fully qualified server URL, for example, www.ibm.com.

Line 8

No changes.

Once you have created a script with the commands above, save the script to a file called scriptfile.jacl (this example uses the recommended directory WebSphere_Install\AppServer\util) and execute the wsadmin command as described below:

At the C:> prompt:

C:\PROGRA~1\WebSphere\AppServer\bin\wsadmin –f C:\PROGRA~1\WebSphere\AppServer\util\scriptfile.jacl

Note: The boldface type indicates text that might be different depending on your installation directory.

If you change to the WebSphere bin directory, the command is:

C:> wsadmin –f C:\PROGRA~1\WebSphere\AppServer\util\scriptfile.jacl
23820 When changing the color theme of graphs (Bar, Line, Stacked Bar), you must click on the large color box choice for the colors to be set properly. Do not use the small color boxes for choosing the color theme.
24490 If using WebSphere 4.0.5 with Simplified Chinese on the HP or Solaris platform, change the GB2312 key in the converter.properties file from Cp1386 to EUC_CN to avoid exceptions and corruption on the Web-based System Monitor. The converter.properties file is located in WebSphere/AppServer/properties.

System Monitor (Monitor.exe)

CR
number
Problem
23967 System monitor does not allow users to register servers with the same name but different capitalization.

SNMP

CR
number
Problem
8089 The SNMP Agent and SNMP Configuration Manager are installed together as a bundle, even though the Agent and the Manager can function on separate machines.
Because on UNIX platforms only root users can use port 161, the default port for the SNMP Agent running on a UNIX platform is 1161. On a Windows platform, the default port remains 161.

Integrated Test Environment

CR
number
Problem
24300 The test environment console text and ICS console context menu text is not translated.
The ITE console menu now color-codes the text depending on the message type: normal text in black, warnings in blue, and errors in red.

Documentation updates

Product documentation is not included as part of the product package, either by CD or electronic product distribution. The documentation for this product can be found in the following InfoCenter: http://www.ibm.com/websphere/integration/wicserver/infocenter

To obtain the product documentation, visit the Web site and download the current documentation set for the release that you are using. Follow the instructions provided on the InfoCenter page to complete the installation.

Copyright IBM Corp. 1997, 2003