These release notes cover release information for IBM(R) WebSphere(R) Business Integration Adapters, version 2.6.0, for HP-UX. 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.
Between releases 2.4.0 and 2.6.0, the following CRs, based on customer-reported cases, were fixed.
| Tracking number |
Description |
| 35632 | DisableNumberFormatGrouping will used to determine whether to use grouping when calling CWConnectorBusObj.setintValue(..)/setfloatValue()/setdoubleValue(). The default if not set will be false. Without grouping 1,234,567 will be kept as 1234567. A new property DisableLocaleFormating will be used to determine whether to perform any formating on numbers. The default for this property is false. |
| 33705 | Two new properties were added, MaxDoublePrecision and MaxFloatPrecision, to set the double and float precisions independent of the locale. The setdoubleValue and setfloatValue methods now use these property values if set, instead of the default locale precision. Fixed in Patch 1.6.1. |
| 30617 | A new property, RetrieveVerb, has been introduced. For backward compatibility, the verb will be set by default to RetrieveByContent. The adapter can set the RetrieveVerb to override this default. If the property is set, it will be used as the retrieval verb in getBO. |
| 33784 | A new method signature has been added for fetchEvents. The method signature is: public Vector fetchEvents(int pollQuantity) throws ConnectionFailureException, FetchEventsFailedException. This method also has a default implementation for backward compatibility that consists of a call to the original method and returns the eventsToProcess Vector in CWConnectorEventStore. The StatusChangeFailedException is caught and is transformed to ConnectionFailureException. In pollForEvents, the new method is called. APPRESPONSETIMEOUT is returned if there is a ConnectionFailureException. For FetchEventsFailedException, a FAIL status is returned from pollForEvents. |
| Tracking number |
Description |
| 46029 | An RAS aid has been added to always trace the version of the adapter used. |
| 46185 | CxListBuffer's endsWith() method does not properly return a value of false when it cannot locate the specified search value.The IndexOutOfBoundsException in CxListBuffer has been fixed. |
| 30977 | The adapters do not behave correctly when a 2019 error is generated by MQSeries. |
| 29963 | More than one adapter with the same name can be started. Checking has been added to ensure that an adapter can not be started more than once on the same platform. A message will be displayed if this another adapter with the same name is detected. |
| 33337, 33338, 33339 | Large Object support should be added. |
| 32412 | The C++ adapter cannot be started because the CWConnector.dll is missing from the package. |
| 34350 | Using JDBCConnector, the RetrieveByContent verb does not retrieve the business object if the select query encounters multiple records. |
| 46118 | RetrieveByContent verb processing fails in the JDBC Adapter. |
| 34472 | The MQ adapter returns an OutOfMemory error when processing a large event. Code has been added to check for an OutOfMemory exception in the polling thread. If found, a message will be logged and the adapter will exit. |
| 34726 | Invalid messages are lost when they are received by the adapter running with WebSphere Business Integration Message Broker. Messages of this type will not be routed to the fault queue. |
| 36131 | Adapter Framework responds with a ClassCastException error when JMS messages of an unexpected type are received. Tracing has been added to indicate the error that has occurred. |
| 36763, 58347 | Adapters cannot connect to InterChange Server after restarting the Persistent Name Server. |
| 36147 | Dynamic updates of the agent trace level do not work. |
| 32199 | Adapter Framework always prepends a connector name to ObjectEventId. A new connector property has been added for InterChange Server brokers, EnableOidForFlowMonitoring. This property is a Boolean with a default value of false. If it is set to true, the ADK will mark the incoming ObjectEventId as a foreign key for flow monitoring. |
| 29420, 30721 | An adapter script change can improve the performance of an adapter. The JVM arguments contain an -mx option (Max heap size). Adding the -ms option (Min heap size) and setting its value to half of the maximum heap size will improve performance. Edit the start_adapter.bat file located in the \bin directory. Locate the line that contains "set JVMArgs" and add the -ms option. For example: set JVMArgs="-mx128m -ms64m %JVMArgs%" |
| 29249 | Business object attributes set to zero can cause a parser error: org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x0) was found in the element. |
Using WebSphere Business Integration Adapters version 2.6.0 while earlier versions are installed on the same physical machine is not recommended. If different versions of WebSphere Business Integration Adapters version 2.6.0 are required, you should use separate machines.
Supported InterChange Server versions include 4.2.2 to 4.3.
Supported adapters include any released with WebSphere Business Integration
Adapters versions 2.3.1 to 2.6.0.
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 Installing WebSphere Business Integration Adapters, V.2.6.
Migration note
To allow any adapter from a previous release of Adapter Framework to function properly with this release, you must change the start scripts for both the connector and ODA. Please refer to the Adapter Migration Guide for the specific changes required.
Adapter for CORBA installation note
If you install the adapter for CORBA, be sure to read the adapter release notes for additional information about prerequisite software.
This release includes the following limitations:
The following problems have been found in this release:
|
Tracking number |
Problem |
| 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 WebSphere MQ Integrator or WebSphere
Application Server is the integration broker. The adapter run time converts
business objects into XML messages, which can become very large. |
| N/A | Adapters storing meta/configuration data in meta business objects (as part of default values) or regular business objects (as part of run time instances content) might not fully support processing of bi-di data with right-to-left direction. The incorrect processing might occur only if this meta/configuration data guides the connector in the processing of application-specific information (ASI), and includes specifications of data handler classpath, data encoding, queue names, and so on. To work around this, you must put a specific definition for each one of the meta business objects. Specifically, you must add the BIDI.METABUSINESSOBJECT=YES specification to business object level ASI of each meta business object. |
| Tracking number |
Description |
| 44407 | When IBM 32-bit SDK for use with IBM WebSphere Business Integration Adapter Framework Installer is running in traditional Chinese, simplified Chinese, and Korean locales, the text on Installer's welcome panel gives the impression that the Software Development Kit (SDK) version is 2.6.0. Version 2.6.0 actually refers to IBM WebSphere Business Integration Adapter Framework and not IBM SDK. This is not a problem when the installer is running in other locales. |
| 29755 |
The installation fails if you select an installation location that contains
Simplified Chinese, Traditional Chinese, Korean, or Japanese characters
in the directory name. |
| Tracking number |
Description |
| N/A | If a non-bi-di keyboard layout (for example, an English one) is selected when you copy bi-di characters from an external location (for example, Notepad) and paste them into C++ based WebSphere Business Integration Tools with GUI, the bi-di characters are displayed as question marks. To avoid this problem, you should use the bi-di keyboard layout when copying from external sources to a C++ based WebSphere Business Integration Tools GUI component. |
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 InfoCenters:
http://www.ibm.com/websphere/integration/wicserver/infocenter
http://www.ibm.com/websphere/integration/wbicollaborations/infocenter (for collaborations)
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.