These release notes cover release information for WebSphere Business Integration Adapters, version 2.3.1, for Solaris. They contain the following sections:
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.
For details, refer to the Connector Development Guide for Java.
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 such as ior_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. |
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:
|
21679 | If you installed an adapter using the silent installation tool, the adapter did not start properly. |
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 the appropriate guide:
These guides also include migration, upgrade, and configuration information.
Make sure that you run adapters with WebSphere Business Integration Adapters (WBIA) API version 1.5.0 or later.
To check the version of WBIA 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.
To download the latest version of the WBIA API:
After you download and install the APIe, 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
To enable an adapter to work with various versions of ADK or InterChange Server, follow the appropriate procedure below:
In CWConnEnv.sh, set the CWVERSION variable to 4.X.
set CWVERSION="4.X"
In CWConnEnv.sh, set the CWVERSION variable to 4.1.X.
set CWVERSION="4.1.X"
In bin/CWODAEnv.sh, set the CWVERSION variable to 4.1.X.
set CWVERSION="4.1.X"
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: The solution is to recompile 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: The solution is to recompile connectors with the 2.0 CDK patch. |
23482 |
Adapters can not write more then 100 MB XML message text into MQ queue for processing because of the MQ limitation. This problem occurs when JMS is transport and broker is either WMQI or WAS. Adapter runtime converts Business Object into XML message which becomes huge in message size for WMQI and WAS broker. Workaround: Avoid creating more then 25000 child objects per Business Object or try to reduce the XML message size written into MQ Queue. |
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: The solution is to recompile connectors with the 2.2 CDK patch. |
CR umber |
Problem |
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. |
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. |
24067 | On the Language Selection panel, drop-down language list is only partially
translated for Brazilian Portuguese. This is caused by the version
of Java Virtual Machine (JVM) that Installer uses.
Workaround: Although IBM does not recommend this workaround, Installer can be forced to use the JRE that is installed on the machine by executing the following command:
|
24147 |
Text corruption occurs on all supported double-byte languages: Japanese, Korean, Simplified Chinese, and Traditional Chinese. Workaround: Run Installer in swing mode by executing the following command: ./setupsolarisSparc.bin -swing |
CR number |
Problem |
16868 | When you use the Java command ./setupsolarisSparc.bin
-Dtemp.dir=/home/user1/tmp to run Installer, the tmp directory is not cleaned
up. This increases the size of the tmp folder.
Workaround: Manually delete unwanted files from the tmp directory. |
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. |
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:
http://www.ibm.com/websphere/integration/wicserver/infocenter
http://www.ibm.com/websphere/integration/wbiadapters/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.