These release notes cover release information for IBM(R) WebSphere(R) Business Integration Connect, Enterprise and Advanced Editions, Version 4.2.2. They contain the following sections:
New in this release | Limitations |
Product fix history | Known problems and workarounds |
Hardware and software requirements | Documentation |
Installation, migration, upgrade, and configuration information |
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 at http://www.ibm.com/software/integration/wbiconnect/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.1 and 4.2.2 and, the following problems, based on customer-reported cases, were fixed.
Tracking number |
Description |
34416 | Business Integration Connect processes intermittently went to 100% CPU utilization after losing the WebSphere MQ connection. This has been fixed. |
34552 | The Console Branding feature did not display an uploaded banner or console logo. This has been fixed. |
35095 | The last character of some XML documents was truncated to < or >. This has been fixed. |
35975 | PIP samples failed to compile after being imported into System Manager. This has been fixed. |
Hardware and software requirements are included in the product documentation. See Installation, migration, upgrade, and configuration information for links to those guides.
Whether you are installing the software from the CD or downloading it from Passport Advantage and installing it from a local directory, refer to Installing WebSphere Business Integration Connect.
The guide also includes general migration, upgrade, and configuration information. For notes on migration to version 4.2.2, refer to Limitations and Known problems and workarounds.
Business Integration Connect is not able to support PIPs that send XML documents with more than one format per action. For example, a typical one-action PIP sends an XML document of only one format to a receiver. The PIP 2A1 V1.0, however, uses two different formats for the service content.
If you create a PIP document flow package, the name of the PIP or its DTD and the names of the XML and XSD files in the PIP document flow packages cannot exceed 120 characters. If any of the names exceed this limit, Business Integration Connect cannot upload the PIP document flow package.
In one-way synchronous RosettaNet routing, the Sync Ack Required attribute determines whether the Digital Signature Required and Non-Repudiation of Receipt attributes take effect or not. The following two examples illustrate this functionality.
For example 1, consider a Participant initiated, one-way synchronous PIP with the following connection attributes:
In this example, the Sync Ack Required has priority and Business Integration Connect will return an "http 200" to the Participant and not generate a receipt acknowledgement even though the Non-Repudiation of Receipt attribute is Yes. Likewise, if the Community Manager initiates a one-way PIP to a Participant, Business Integration Connect will expect only an "http 200" status and no receipt acknowledgement.
For example 2, consider a Participant initiated, one-way synchronous PIP with the following connection attributes:
In this example, Business Integration Connect will generate a receipt acknowledgement with the correct message digest and signature. Likewise, if the Community Manager initiates a one-way PIP to a Participant, Business Integration Connect will expect a receipt acknowledgement with the correct message digest and signature.
Directory names cannot contain non-ASCII characters
This is a limitation of WebSphere Application Server, which responds to
WebSphere Business Integration Connect requests. It cannot handle a non-ASCII
character within a directory name. This includes all installation directories.
0C PIPs do not work with Community Participant Simulator
The Community Particpant Simulator (CPS), which is used to test connections
between Community Manager and a configured participant, does not work with
"0C" type RosettaNet PIPs. However, PIPs of other types can be
tested using the simulator.
The following problems have been found in this release:
After installation is complete, starting the router, receiver, and console services with the command ./startServer.sh server1 generates the following error message: ./startServer.sh server1This is an informational warning designed into the system and not an actual error. All services will function normally. |
Shutting down the receiver and router might fail on Solaris platforms.
The shutdown command (stopServer.sh server1) for the router or receiver
begins when executed, but it might process indefinitely.
Workaround: Stop the processing of the shutdown command, then run the following
commands for the router and receiver: |
A Windows services view may
incorrectly report the status of an IBM WebSphere Application Server
- bcgDocumentManager service.
Workaround: At a DOS command prompt, stop and restart the server. Stop the server by executing either the shutdown_bcg command or the stopserver command. When shutting down the server, the server name is not needed. Restart the server by executing the following command from the <WBICRoot>\router\was\bin directory: startserver server1. |
Events
may not show up in the Event Viewer.
Workaround: Stop and restart the WebSphere Application Server console, router, and receiver. These commands are operating-system specific and can be found in the installation guide. They are the same commands used to start the console, router, and receiver during installation. |
New users may not initially pick up the default time zone of the Hub Admin
user. If a user does not select a local time zone setting, the default
may be either blank or show GMT on initial login.
Workaround: New users should log out and log in again, and then choose the time zone of the Hub Admin user. |
Only one help topic is displayed at a time. If a help topic is already open and in the background, a newly selected help topic is not displayed. The original help topic remains in the background until it is closed. |
If a database connection is lost while starting the console server, no error message is displayed. However, graphics are missing from the console login screen, and a password entered into the console is invalid, even if it is correct. |
After successful product installation and login, the following error may appear in the console: SystemOut.log and the wbic_console.log: "ToString::generate() -- java.lang.ClassCastException: java.lang.Object. This is a misleading error caused within the logger itself. It does not represent a problem with the product functionality and can be safely ignored. |
A "font specified in font.properties not found" message may be displayed in the command window that executes the LaunchPad.sh command on some UNIX systems. This error does not cause any known problems with the application and can be safely ignored. |
When the Administration application programming interface is enabled or disabled, it should log an event BCG104013. It logs BCG104011 instead. |
Files generated by using the -options-generate option do not have correct data in the files. String resolvers of the form $P() or $W() should be replaced with the values seen on the installation wizard panels. This can be done by editing a supplied example response file or by replacing the string resolvers in the generated options file with the appropriate values using an editor before executing a silent installation. This problem occurs with both the Database Loader and the Hub installation wizards. |
After installing Business Integration Connect on AIX or Solaris systems and starting the Community Console, the login screen contains strings of questions marks ( "???") and the log file wbic_router.log contains an SQL -1022 error message. To clear this condition, after you install the product, stop and restart the DB2 instance. The DB2 commands are db2stop to stop and db2start to start the database instance. Consult your database administrator instructions on executing these commands in your specific database environment. |
After you migrate from Business Integration Connect 4.2.1, fix pack 1,
to version 4.2.2 on systems with DB2, the index UK_TRANSPORT_1 has the
incorrect schema.
Workaround: After the migration scripts have been executed, run the following commands from the DB2 command line:
|
When publishing events to an external queue using the event publishing application programming interface, the event code (BCG_EVENTCD) and the severity are not included. This will be addressed in the first fix pack to this release. For an interim fix, contact IBM technical support. |
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 Information Center:
http://www.ibm.com/software/integration/wbiconnect/library/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 Information Center page to complete the installation.