These release notes cover release information for WebSphere(R) InterChange Server(TM), Version 4.3, for AIX(R). 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 |
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.
This section lists the new features and improvements made in this release.
Between releases 4.2.2 and 4.3, the following problems, based on customer-reported cases, were fixed.
Tracking number |
Description |
23061 |
If an LLBP collaboration receives a response to an inbound service call while the collaboration is stopped, then the response is not processed when the collaboration is restarted. This has been fixed. |
23248 |
If validate database connection is selected from the Server View, error messages are printed in the ICS log. No feedback is given in the GUI. This has been fixed. |
23879 |
If a collaboration is in an in-doubt state, System Monitor incorrectly displays the status color in red instead of yellow. This has been fixed. |
24374 |
If a collaboration is in a paused state before shutting down the ICS, the collaboration displays as inactive after ICS is restarted. This has been fixed. |
28505 |
Setting OAThreadMax and OAThreadMaxIdle in the InterchangeSystem.cfg does not apply to the ORB. To specify these two properties, add -Dcom.ibm.CORBA.ThreadPool.MaximumSize=your_specified_size and -Dcom.ibm.CORBA.ThreadPool.InactivityTimeout=your_specified_time to the CWSharedEnv.bat file. Also, to specify other CORBA properties, such as OAport, manually add the property to the configuration files (either the InterchangeSystem.cfg file or adapterConfig.cfg file) in the "CORBA" section. This has been fixed. |
29964 |
The Schema name for the Flow Monitoring Table (used for WebSphere Business Integration Monitor integration) is not configurable in InterChange Server. ICS does not use a schema name; instead, it defaults to the name of the data source user. If the schema name and user name are different for the WebSphere Business Integration Monitor data source, ICS may not find the required table. This has been fixed. |
31133 |
When flow monitoring is turned on for a group collaboration, the ENTER_COLLABORATION event of a child collaboration might be recorded before the START_SERVICE_CALL event of the parent collaboration. This changes the order in which events are recorded in the database. This has been fixed. |
32119 |
Maps that are deployed from System Manager are automatically started. However, if the deployed map is stopped and restarted after deployment, System Manager returns the error "Map has already been activated." The map cannot restarted. This behavior occurs, too, when maps are deployed using repos_copy. This has been fixed. |
Tracking number |
Description |
21313 |
The summary panel shows an incorrect amount of disk space required for installation. For a full installation, add approximately 6 MB to the displayed space requirements. |
Hardware and software requirements are included in the product documentation. See Installation, migration, upgrade, and configuration information for links to those guides.
For hardware and software requirements, installation, migration, upgrade, and configuration information specific to this product, refer to the System Installation Guide for UNIX.
Caution: The country in which you reside may have restrictions on the import, possession, use, or reexport to another country of encryption software. Before you download any encryption software, check your country's laws, regulations, and policies concerning the import, possession, use, or reexport of encryption software, to see if this is permitted.
For migration information, refer to the migration section of theSystem Installation Guide for UNIX.
The following problems have been found in this release:
Tracking |
Description |
24123 |
The temporary string variables declared for map transformations are not initialized and they have a null value. So during map transformations, data conversions on these variables with null values using DtpDataConversion.toXXX(Object objectData) throw DtpIncompatibleFormatException. |
29159 |
System Manager hangs when you right-click to stop a collaboration during debugging a break point; you cannot do anything on the GUI, including finishing the debugged flow. This happens in the debugger because a collaboration with running flows cannot be stopped. The System Manager process must be killed manually |
31603 |
InterChange Server messages (including log messages and other informational messages) are not localized. These messages are in English, and some of the ICS tools display these messages in English even if the tool is set up for a non-English locale. |
42846 |
System Monitor cannot count events that fail connectors in the Server Statistics view. |
43023 | Database-specific SQL reserved words should not be used while creating attributes in a relationship. Their use results in JDBC exceptions while creating the appropriate tables in the underlying database. For example, the SQL reserved words "index", "key", "char", and "table" should not be used in naming the relationship attributes. This exception occurs on SQL2000 on all platforms InterChange Server supports. Also avoid using these words when choosing other databases. |
43439 | When a JMS agent fails, the server is not notified until the heartbeat thread times out, which can take as long as 2 minutes. During this time, the same event might be sent twice to the agent because the collaboration thread can send the request to the agent, and the request sits in the queue. When the heartbeat thread times out, the waiting collaboration thread puts the same event in the failed event table. When the agent starts again, the same event is resubmitted. |
43441/43549 | The composite identity relationship (an identity relationship used to relate both parent business object and child business object) feature does not function in ICS 4.3. To use this feature, contact IBM Technical Support. |
Tracking number |
Problem |
When running the uninstaller, some files may remain on the system. Workaround: Remove the files manually. |
|
11600 | Initial startup of Installer may be slow during the initialization of a
JVM. Do not try to start Installer multiple times. |
20432 | No error message is returned when you enter Japanese characters for the InterChange server name. Installer does not support internationalized ICS names. |
24023 | General: After
installing or uninstalling, you may see following warning in the
console:
Warning: This warning has no impact on the success of the installation or uninstallation. |
32212 |
You must provide the following values in the OptionFile.txt file:
|
Tracking 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. |
Document |
Description |
System Installation Guide for UNIX |
Chapter 8, Upgrading the InterChange Server System. In the section "Preparing the existing ICS system," in the command shown for backing up the existing repository: repos_copy -sWICS -o repos_copy.in -uadmin -ppasswd there should be no space between the "-o" flag and the file name, and the example file name is inconsistent with the accompanying text The command should read as follows: repos_copy -sWICS -oRepository411.txt -uadmin -ppasswd |
System Installation Guide for UNIX |
Chapter 8, Upgrading the InterChange Server System. In the section "Validating the Upgrade." The third bullet point reads: Validate that all connectors found their given queues successfully. Select System View from the Server menu in System Manager, and verify that the connectors have green lights icons next to them, and that the status of the connectors is Inactive. The green light icon implies that the connector status is Active, so the bullet should read: Validate that all connectors found their given queues successfully. Select System View from the Server menu in System Manager, and verify that the connectors have green lights icons next to them, and that the status of the connectors is Active. |
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 Information Center page to complete the installation.
Product documentation is not included as part of the product package, either by CD or by electronic product distribution. The documentation for this product can be found in the following Information Centers:
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 Information Center page to complete the installation.