Release Notes for IBM WebSphere Business Integration Server Express, Version 4.3.1, for Linux

These release notes cover release information for IBM(R) WebSphere(R) Business Integration Server Express, Version 4.3.1, for Linux(TM). They contain the following sections:
Overview Uninstallation information
Hardware and software requirements Known problems and workarounds
Installation and configuration information 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/software/integration/wbiserverexpress/support. Select the component area of interest and search the flashes section.

Overview

IBM WebSphere Business Integration Server Express and IBM WebSphere Business Integration Server Express Plus comprise the following components:

In addition to existing support on Windows(R) 2000, this release adds support for InterChange Server Express on the following operating systems:

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 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 WebSphere Business Integration Server Express Installation Guide for Linux.

Note: If you are installing the technology adapters and application adapters on the same machine, install the technology adapters first, through Server Express Plus, then install each application adapter through the Adapter Capacity Pack installer.

Known problems and workarounds

The following problems have been found in this release:

Component name Tracking number Description
Activity Editor 42343 In Activity Editor, you can select from a list of global variables in the Library Window to use in a custom activity. Global variables can be as simple as a Java variable (for example, of type String) or they can be as sophisticated as a business object variable (for example, of type BusObj). When a global variable is used in an activity, its assignment happens only at the end of the activity, so you should avoid using separate variables that have the same root variables in one activity.

Instead, you can do two sub-activities in different actions. If you must use variables with the same root, try to re-use the single root variable instead.

Adapters 43586 The AgentTraceLevel property for a connector running over the JMS delivery transport and using a local connector configuration (specified through the -c command line option) can only be dynamically updated once through System Manager during the connector's lifetime. Subsequent attempts to dynamically update this property will fail. A message resembling the following will be shown in the logs:

[Type: Warning] [MsgID: 14211] [Mesg: Dynamic update is not allowed for AgentTraceLevel. In the configuration file, value was already set for the connector agent and previously set value will be used.]

The AgentTraceLevel property for a connector running over the JMS delivery transport and using a local connector configuration should not be dynamically updated via System Manager. If the property needs to be modified, you must update the connector configuration file and restart the connector agent. Otherwise, the error just described will be encountered and a mismatch between the connector controller setting and the connector agent setting may be occur.
Adapter for JDBC 43503 When you use the ODA to generate a business object from a DB2 database server running on Linux, the Business Object Designer will hang. This occurs because the DB2 JDBC Applet Server does not start.

To work around this, log into the DB2 server, and run the following command: db2jstrt LISTENPORT.

Adapter for JDBC and Adapter for Oracle Applications 43246 The start script for the OracleAppsODA includes the xworacle.jar file in the DRIVERPATH, which does not list all tables in the Oracle database as expected. If you want to list all the tables in the database, you can work around this problem by using the native JDBC driver-classes12.zip file provided by Oracle. Set the driver path appropriately in the start scripts according to the instructions in the adapter user guide.
Adapter for JMS and Adapter for WebSphere MQ 37094 While processing an in-doubt message (from InProgressQueue) that originated from one of multiple configured input queues, the adapter retrieves the conversion properties based on the first input queue in the connector-specific properties.
Adapter for JMS 36438 Conversion property names in the application-specific information of the configuration meta-object and the dynamic meta-object names are case sensitive.
Adapter for JMS 36128 The adapter fails to initialize when the InputQueue property is not configured.
Adapter for JMS and Adapter for WebSphere MQ 34323 The samples for the JMS and WebSphere MQ adapters are designed to provide configuration and use of the adapters in a WebSphere InterChange Server Express environment. The instructions for using these samples are provided in technotes that describe how you can use the samples to send and receive business objects in a WebSphere Business Integration Server Express environment.

The technote for the JMS adapter can be found at the following location:
http://www-1.ibm.com/support/docview.wss?rs=0&q1=JMS+adapter&uid=swg21174512&loc=en_US&cs=utf-8&cc=us&lang=en
The technote for the WebSphere MQ adapter is available at the following location:
http://www-1.ibm.com/support/docview.wss?rs=0&q1=WebSphereMQ+adapter&uid=swg21174510&loc=en_US&cs=utf-8&cc=us&lang=en
Adapter for JMS and Adapter for WebSphere MQ 33728 During event processing, when multiple conversion properties match either the InputFormat or InputQueue, or both, of an input message, the adapter tries to incorrectly use the last matched business object attribute in the static meta-object as a map for the input message. In such cases, the adapter should pass the message content to the data handler to allow the data handler to determine the business object name.

To work around this, configure unique InputFormat and InputQueue keys for each of the BusinessObjectType_verb attributes in the static meta-object.

Adapter for JText 46499 If more than one file matches the event mask in MVS PDS, and FTPRenameExt is specified, the connector archives only one file and is not able to rename and archive the second file. To work around this, specify both FTPArchiveDir and FTPRenameExt as blank, so that the MVS event file is deleted without being renamed.
Adapter for JText 43454 When the JText adapter is polled with the EventExt attribute of the JText configuration meta-object MO_JTextConnector_Default set to blank, the polling fails and the adapter terminates.
Adapter for JText 35571 A provision to specify 'EOF' as a value to the EndBODelimiter in the binary processing mode is required.
To work around this, for all files with no other EndBODelimiter than the EOF itself, use a Hex editor to include a couple of bytes (for example, FF02) as the delimiter, and specify the bytes as the EndBODelimiter.
Adapter for JText 34834 Secure FTP support is required by JText. The password field, visible to the JText system administrator now, would not be visible to anyone with Secure FTP.
Adapter for WebSphere Commerce 42516 When WebSphere Commerce, Business Edition, version 5.5 with Fix Pack 4 (or earlier version) is used on the commerce server, the store user cannot be created properly with the WebSphere Commerce adapter. The store user cannot log onto the store because of improper authority. A Websphere Commerce efix is required to fix this problem. The efix is JR20090 on WebSphere Commerce 5.5 with Fix Pack 4.
Adapter for WebSphere MQ 34969 During synchronous event processing, a report message is not sent for data handler errors.
DB2(R) Enterprise on Windows 35380 DB2 Enterprise does not restart the database manager when Windows restarts. Because the database manager is not running, two problems can occur if Windows restarts during the installation of WebSphere Business Integration Server Express or Express Plus:
  • The repository creation can fail. When this occurs, the Installer log includes the following message line:
    No start database manager command was issued.
  • The startup of InterChange Server Express can fail, because without the database manager running, InterChange Server Express cannot connect to SMB_DB. When this occurs, the InterchangeSystem log file messages include the following line:
    No start database manager command was issued.

You can address both of these problems by taking the following steps:

  1. Open the DB2 Control Center.
  2. Expand the All Cataloged Systems folder, then expand the folder for your host, and then expand the Instances folder.
  3. In the Instances folder, right-click the DB2 icon, and click Start.
    The following DB2 message displays:
    DB2START processing was successful.

After you have performed these steps, you can create a repository and successfully start InterChange Server Express.

DB2 Enterprise and DB2 Express uninstallers on Windows 35380 If either DB2 Enterprise or DB2 Express and WebSphere Business Integration Server Express or Express Plus have previously been installed and uninstalled, the repository creation fails during reinstallation of WebSphere Business Integration Server Express or Express Plus. This occurs because the uninstallation process for DB2 Enterprise and DB2 Express does not remove aliases for databases from the directory C:\DB2\aliases_directory.

Therefore, the alias for the InterChange Server Express repository called SMB_DB, which is created during the original installation of WebSphere Business Integration Server Express or Express Plus, remains after the uninstallation of DB2. Although the existence of this alias does not affect the reinstallation of DB2 Enterprise or DB2 Express, when WebSphere Business Integration Server Express or Express Plus is reinstalled, the repository creation fails because the system finds the old SMB_DB alias.

To work around this, manually delete the SMB_DB database before uninstalling and reinstalling DB2 Enterprise or DB2 Express. Deleting the actual database eliminates its alias.

Documentation 44024 WebSphere Business Integration Server Express Installation Guide for Linux
In the section "Configuring System Monitor and Failed Event Manager when using a Web server," the example command is incorrect. It should appear as follows:
Home_directory/IBM/WebSphereServer/CWDashboard.sh \
"/opt/IBM/WebSphere/Express502/AppServer" \
hostname.ibm.com "Home_directory/IBM/WebSphereServer" \
"DB2_Installation_Dir/java" y
Documentation 44025 WebSphere Business Integration Server Express Installation Guide for Linux
In the section "Viewing WebSphere Business Integration Server Express and Express Plus files and directories," one table entry is missing. In addition to the entry "logs" there should be an entry called "log" with the following description: "This directory includes several log files related to product installation and uninstallation, such as installer logs for the InterChange Server Express
(wbi_server_exp_install_log.txt), the Adapter Capacity Pack (adapterCPInstallLog.txt), and the Collaboration Capacity Pack (collabCPInstallLog.txt)."
A similar correction needs to be made in the section "Installing WebSphere Business Integration Server Express and Express Plus using the GUI." The final sentence in the second paragraph following the installation procedure should read, as follows: "The log file called wbi_server_exp_install_log.txt, which details the installation process, is located in the directory ProductDir/log."
Documentation 44026 WebSphere Business Integration Server Express Installation Guide for Linux In the section "Installing WebSphere Business Integration Server Express and Express Plus using the GUI," in the bulleted list that follows the installation procedure there is a bullet that reads as follows: "Added a new system variable called LD_ASSUME_KERNEL to the /etc/profile file and set its value to 2.4.19." The installer creates this system variable only on Red Hat Linux systems; it does not create it on SuSE Linux systems.
Documentation The Data Handler Guide guide incorrectly refers to and provides documentation for the binary host data handler. The binary host data handler is not included in the product.
Documentation The guide for the MetaSolv Adapter should state that the Metasolv Adapter now supports Product Service Request (PSR) and Local Service Request (LSR) modules.
Documentation For all guides, the "New in this release" section should read as follows:
In addition to existing support on Windows 2000, this release adds support for InterChange Server Express on the following operating systems:
  • IBM OS/400 V5R2, V5R3
  • Red Hat Enterprise AS Linux 3.0, Update 1
  • SuSE Linux Enterprise Server 8.1 with SP3
  • Microsoft Windows 2003
Documentation In the Quick Start Guide, the following path, which is located in step 1 of the "Starting InterChange Server Express" section of the "Validating your Linux installation" chapter, is incorrect: $cd /home/USER/IBM/WebSphereICS/bin

The correct path is: $cd/home/USER/IBM/WebSphereServer/bin or $cd/ProductDir/bin

The following explanatory path information has also been added to this section.

Notes: In the scripts shown above:
"$" is the Linux command line prompt
"cd" is a command used to change directories
"bin" is a folder within the product installation directory
Installer (Adapter Capacity Pack) 44001 When you do a remote or local Capacity Pack installation for the Adapter for Metasolv and JD Edwards OneWorld on Windows 2000 and try to launch the adapter, it terminates with an error: The input line is too long. This is because of the command line length issues on Windows 2000. You will see the same problem with WebSphere Business Integration Adapters for Siebel and Oracle Applications when you do a remote CP install. A workaround to this issue is planned for a technote to be available after this release.
Installer (All) 46851 Unresolved text from resource bundles may appear in the window during file transfer. In particular, the following might display:
$L(com.ibm.wbi.install.common.i18n.WBIProductResources, businessIntegrationServerExpressPlusProduct.
displayName)
What should display is:
WebSphere Business Integration Server Express Plus V4.3.1
Installer (All) 43593 The title text may be truncated on the message dialog boxes due to its length; however, the intended content of the message displays.
Launchpad 43688 IBM WebSphere Application Server V5.0.2.4 for Linux cannot be installed on Red Hat Enterprise Linux AS 3.0. Use IBM WebSphere Application Server - Express V5.1 instead.
Launchpad 58560 The Toolset Express component is automatically installed when the Samples component is being installed, even if you clear the check box next to Administrative Tools and Development Tools. This happens because the Launchpad GUI does not refresh correctly to reset the check boxes.
Server (Samples) 43775 There is an error in the \mqseries\RemoteServerSample.mqsc file.

In the following expression, the highlighted text is incorrect:
DEFINE CHANNEL(CH_ICS_TO_AGENT) CHLTYPE(SDR) TRPTYPE(TCP) REPLACE +
XMITQ(TO_AGENT) DESCR('Server to Agent') +
CONNAME('172.16.15.96(1415)')

The expression should read as follows (see highlighted text):
DEFINE CHANNEL(CH_ICS_TO_AGENT) CHLTYPE(SDR) TRPTYPE(TCP) REPLACE +
XMITQ(XMITQ_TO_AGENT) DESCR('Server to Agent') +
CONNAME('172.16.15.96(1415)')

To work around this, modify the \mqseries\RemoteServerSample.mqsc file after installation.
System Monitor 43360 If you create a view with more than 20 monitors from the Create and Configure Views page, you might encounter an exception when you select the view. Limit the number of monitors in a view to less than 20.
System Monitor 42481 System Monitor supports running the Web Application Server and client in the same locale. If the server and client are in different locales, text will display in both languages. If it is not possible to run the server in the same locale as the client, set the locale on the JVM to be the same as the client locale by performing the following steps:
  1. From WebSphere Application Server, start the WebSphere Application Server Administrator Console (for Express, you must enable the adminconsole application):
  2. Go to Java Virtual Machine via the following path:
    Servers > Application Servers > ICSMonitor > Process Definition > Java Virtual Machine
  3. Add the following arguments to the generic JVM arguments:
    -Duser.language=language code -Duser.region=country code
    Replace language code and country code with your specific language and country codes.
  4. Restart the InterChange Server monitor server, and set the client browser to the same language used in the previous step.
System Monitor 43759 If you are using Netscape 4.7x with double byte character languages, the characters may not display in Netscape. To configure Netscape to enable the double byte character set characters to display, follow these steps:
  1. From the View menu within Netscape, select Character Set > Unicode (UTF-8).
  2. From the View menu, select Character Set > Set Default Character Set.
  3. Open the Edit menu and select Preferences.
  4. From the Preferences window, select Appearance > Fonts.
  5. In the For the Encoding field, select Unicode.
  6. In the Variable Width Font field, select Lucida Sans Unicode.
  7. Select Use my default fonts, overriding document-specified fonts.
  8. Click OK.
Tools - Activity Editor 36145 The color marking in the Java(TM) code editor within the Activity Editor cannot handle quotation marks within strings; however, this should not affect compilation.

Documentation

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 IBM WebSphere Business Integration Server Express InfoCenter.

The following documents can be found on that Web site:

Map Development Guide
Business Object Development Guide
Collaboration Development Guide
Data Handler Guide
Access Development Guide
WebSphere Business Integration Server Express Installation Guide for Windows
WebSphere Business Integration Server Express Installation Guide for Linux
WebSphere Business Integration Server Express Installation Guide for OS/400
Quick Start Guide
System Implementation Guide
System Administration Guide
Adapter for COM User Guide
Adapter for e-Mail User Guide
Adapter for Exchange User Guide
Adapter for iSeries User Guide
Adapter for JD Edwards OneWorld User Guide
Adapter for JDBC User Guide
Adapter for JMS User Guide
Adapter for JText User Guide
Adapter for Lotus Domino User Guide
Adapter for MetaSolv Applications User Guide
Adapter for mySAP.com (SAP R/3 V. 4.x) User Guide
Adapter for Oracle Applications User Guide
Adapter for PeopleSoft User Guide
Adapter for Portal Infranet User Guide
Adapter for Siebel eBusiness Applications User Guide
Adapter for SWIFT User Guide
Adapter for Telcordia User Guide
Adapter for Web Services User Guide
Adapter for WebSphere Commerce User Guide
Adapter for WebSphere MQ User Guide
Adapter for XML User Guide

Collaborations for Customer Relationship Management
Collaborations for Procurement
Collaborations for Financials and Human Resources
Collaborations for Order Management

Copyright IBM Corp. 2004