Release Notes for WebSphere Business Integration Adapters Version 2.3.1, for AIX

These release notes cover release information for WebSphere Business Integration Adapters, version 2.3.1, for AIX. They contain the following sections:
New in this release WebSphere Business Integration Adapters API
Product fix history Known problems and workarounds
Hardware and software requirements Documentation updates
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, http://www.ibm.com/websphere/integration/wbiserver/support. Select the component area of interest and search the flashes section.

New in this release

This section lists the new features and improvements made in this release.

WebSphere Business Integration Adapters Framework

WebSphere Business Integration Adapters API

For details, refer to the Connector Development Guide for Java.

Product fix history

The following CRs, based on customer-reported cases, have been fixed in this release.

WebSphere Business Integration Adapters API

CR
number
Description
12271 Support for a custom business object handler. A new interface, CWCustomBOHandlerInterface, has been added that has the method doVerbForCustom. Adapters using custom business object handlers must implement this interface. Also, the business object verb application-specific information must change so that CBOH=custom_BO_Handler_class_name (be sure to use the full path name, that is, begin the path with "com.").
17975 When catching a exception, WebSphere Business Integration Adapters API methods now log the exception message and print the stack trace.
19664

A new property, EventStoreFactory, has been added. If it is set to the connector's event store factory instance, say, com.crossworlds.connectors.JDBC.JDBCEventStoreFactoryInstance, it is used to get the event store; if it is not set to that instance the API tries to build the event store factory instance class name based on the package information. Also, TRUESTRING and FALSESTRING have been added to CWConnectorAttrType, and hardcoded "true" strings have been replaced with this.

19665 If any data other than integer is specified for pollQuantity, pollForEvents returns a FAIL.
19673 A new method, getAppText, which takes in a delimiter and a property name, has been added to CWConnectorBusObj. Based on the property name and delimiter, the value for the property in the application-specific information is returned.
22702 A new method, setDEEId, has been added in CWConnectorBusObj class. It sets the ObjectEventId attribute to the event ID:

public void setDEEId(String eventid)

returns AttributeNotFoundException, AttributeValueException.

22877 A new method, getEventStore, has been added to the CWConnectorAgent class. This method gets the event store from the connector and returns a CWConnectorEventStore object:

public CWConnectorEventStore getEventStore()

The default pollForEvents method has been changed to make a call to this method. Also, there is a default implementation for this method. It first looks at the EventStoreFactory property. The EventStoreFactory property must be set to the CWConnectorEventStoreFactory interface implementation. If it is, the instance of this class is built and gets the event store got from the connector. If the property is not set, the method tries to build the implementation name from the connector package.

The connector has the option to override this method and provide its own. This is helpful if the connector wants to use constructors other than the default constructor.

23369 The APPRESPONSETIMEOUT from the doVerbFor method call does not terminate the connector when doVerbFor is called from within pollForEvents. To enable this, the status must be propagated up to pollforEvents and pollForEvents must return APPRESPONSETIMEOUT.
23406 The EXISTS and RETRIEVEBYCONTENT verb constants have been added to the CWConnectorConstants class.
23612 For application-specific information at the attribute or business object level, the tags that have no values suchasior_file_name=;poa_name=server failed with "No such element found Exception". This has been fixed.
23620 Setting the configuration meta-object and creating the data handler is not done in one atomic (or synchronized) step. This was causing problems with the data handler base class when multiple threads entered the WebSphere Business Integration Adapters API. The code to call setConfigMO is now synchronized. Also, the method is called only once, and the subsequent calls continue creating the data handler.

WebSphere Business Integration Adapters Installer

CR
number
Problem
11983, 12221, 13382, 17788, 20169 Multiple problems in version 4.2.1.0 of the Component Selection panel have been fixed. They include:
  • The panel refreshes after each selection
  • Unreadable text in the panel when collapsing components
  • Selecting parent components does not select all subcomponents
  • Selecting one subcomponent selected all subcomponents
20679 If InterChange Server is your integration broker, make sure you install adapters from WebSphere Business Integration Adapters, version 2.3.1, in the directory where ICS is installed.

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 appropriate guide:

These guides also include migration, upgrade, and configuration information.

WebSphere Business Integration Adapters API

Make sure that you run adapters with WebSphere Business Integration Adapters API version 1.5.0 or later.

Verifying the version of the API

To check the version of the API, locate the manifest file (ProductDir/lib/WBIA.jar) and open it in a suitable Java JAR editor. Look for the following lines:

Implementation-Title: "CWConnectorAPI"
Implementation-Version: 1.5.0
Implementation version indicates the current version of WBIA API.

If the version is not 1.5.0 or later, you must download the latest WBIA API.

Downloading the API

To download the latest version of the API:

  1. Go to http://www.ibm.com.
  2. Click the Support and downloads tab.
  3. Under the Downloads heading, click All downloads & drivers.
  4. In the Enter search terms field, type "wbia api" and click Submit.

After you download and install the API, you should see the following files:

lib/WBIA.jar
lib/WBIA/3.0.0/WBIA.jar
lib/WBIA/4.0.0/WBIA.jar
lib/WBIA/4.1.1/WBIA.jar
bin/CWConnEnv.sh
bin/CWODAEnv.sh
connectors/messages/CwConnectorAgentMessages.txt

Enabling adapters for earlier versions of Adapter Development Kit and InterChange Server

To enable an adapter to work with various versions of ADK or InterChange Server, follow the appropriate procedure below:

InterChange Server versions 4.0.1, 4.1.0, ADK version 2.0.x

In CWConnEnv.sh, set the CWVERSION variable to 4.X.

set CWVERSION="4.X"
InterChange Server versions 4.1.x (except 4.1.0), ADK version 2.1.x

In CWConnEnv.sh, set the CWVERSION variable to 4.1.X.

set CWVERSION="4.1.X"
Running an Object Discovery Agent (ODA) against InterChange Server versions 4.0.1 and 4.1.x, ADK versions 2.0.x and  2.1.x

In bin/CWODAEnv.sh, set the CWVERSION variable to 4.1.X.

set CWVERSION="4.1.X"

Known problems and workarounds

WebSphere Business Integration Adapters run time

CR
number
Problem
23373 Running connectors built with version 2.1 of Connector Development Kit (CDK) with the 2.3.1 CDK build returns run-time errors.

Workaround: Recompile the connectors with the 2.1 CDK patch.

23374 Running connectors built with version 2.0 of Connector Development Kit (CDK) with the 2.3.1 CDK build returns run-time errors.

Workaround: Recompile the connectors with the 2.0 CDK patch.

23482

Due to a WebSphere MQ limitation, adapters cannot write more than 100 MB of XML message text into an MQ queue for processing. This problem occurs when JMS is the transport and either WMQI or WAS is the integration broker. The adapter run time converts business objects into XML messages, which can become very large.

Workaround: Avoid creating more than 25000 child objects per business object.

24108 Running connectors built with version 2.2 of Connector Development Kit (CDK) with the 2.3.1 CDK build returns run-time errors.

Workaround: Recompile connectors with the 2.2 CDK patch.

23699

In a heavily stressed AIX 5.3 platform environment (running adapters with transport = JMS; broker = WMQI or WAS; a large number of child business objects; business object sizes larger than 1 MB; and concurrent consume sessions greater than 1, you may observe an OutOfMemory error after 10 to 12 hours of continuously running a connector agent.

Workaround: Maintain concurrent sessions at 1 session

WebSphere Business Integration Adapters Installer

CR
number
Problem
11600 Initial startup of Installer may be slow during the initialization of a Java Virtual Machine (JVM). 

Workaround: Start Installer only once; do not try to start it multiple times.

17529,
21358,
21858,
21901
If you upgrade from a previous WebSphere Business Integration Adapters release to WebSphere Business Integration Adapters 2.3.1, when uninstalling WebSphere Business Integration Adapters 2.3.1 some folders and files may be left behind.

Workaround: Manually remove unwanted files or directories after uninstall has completed.

24023 After an installation or uninstallation, you may see following warning in the console:
    Warning:
           Name:  scrollbar
           Class: XmScrollbar
           The scrollbar page increment is less than one

This warning has no impact on the success of the installation or uninstallation.

Third-party installer

CR
number
Problem
15011, 17268 The third-party installation product does not halt an installation when not enough space is available.

Workaround: Make sure that you have enough disk space in the installation directory before starting the installation.

23778 The title text on the Language Selection panel might be truncated depending on the language locale you choose. The Language Selection dialog cannot be resized.

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 InfoCenters:

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