Release Notes for Version 2.6.0 of the IBM WebSphere Business Integration Adapter for JDBC

These release notes cover release information for Version 2.6.0 of the IBM(R) WebSphere(R) Business Integration Adapter for JDBC. These release notes contain the following sections:
New in this release WebSphere Business Integration Adapters API and run time
Product fix history Known problems and workarounds
Hardware and software requirements Documentation updates
Installation, migration, upgrade, configuration

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. Click the product you are interested in; if flashes are available, they are located in Self help > Solve a problem > Flashes (Alerts).

New in this release

New features and improvements made in this release include the following:

New operating system support

The JDBC Adapter now runs on 64-bit AIX(R) (32-bit JVM on 64-bit AIX).

New language support

Support for bidirectional (bi-di) languages has been added to the adapter and ODA.

Refer to theAdapter for JDBC User Guide for detailed information about the Adapter for JDBC and the new features.

Product fix history

Between release 2.5.0 and 2.6.0, the following problems, based on customer-reported cases, were fixed.

Tracking
number
Description
35258 Printing of stack traces for exceptions caught at major events in the JDBC Adapter has been added.
31759 A problem with LogAtInterchangeEnd e-mail notification was fixed in Fix Pack 2.4.4.
35455 Containers in a wrapper business object are not being deleted. This problem was fixed in Fix Pack 2.4.4.
35954 Copy attributes are not propagated to child container business objects. This problem was fixed in Fix Pack 2.4.4.
35078 The adapter does not shut down when polling fails, with SPBeforePoll call enabled.
43390 Support is needed for the retrieval of large CLOB objects as parameters of stored procedures.
36188 The connector property RetryCountAndInterval does not work for child business object data.
58660 The adapter returns an error message if the output parameter of a stored procedure is RS (ResultSet).
59112 The adapter fails to open a new database connection after a ping query fails.

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

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 general migration, upgrade, and configuration information.

For hardware and software requirements, installation, migration, upgrade, and configuration information specific to this product, refer to the Adapter for JDBC User Guide.

Upgrade notes

WebSphere Business Integration Adapters API and run time

Make sure that you run this version of the adapter with WebSphere Business Integration Adapters run-time version 1.8.0 or later.

The WebSphere Business Integration Adapters API .jar files and the associated scripts (CWConnEnv.bat and CWODAEnv.bat for Windows(R); CWConnEnv.sh and CWODAEnv.sh for UNIX platforms) are installed by the WebSphere Business Integration Adapters API. Before installing the adapter, make sure that the WebSphere Business Integration Adapters run time is installed. If the version is not 1.8.0 or later, you must download the latest API. This section provides instructions for verifying the API version, downloading the latest version, and enabling the adapter to run on various versions of InterChange Server and Adapter Development Kit (ADK).

Verifying the run-time version

To check the run-time version, 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.8.0

The line Implementation-version indicates the installed version of the API. If the version is not 1.8.0 or later, you must download the latest run time.

Downloading the run time

To download the latest version of the run time:

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

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

lib\WBIA.jar
bin\CWConnEnv.bat (Windows)
bin/CWConnEnv.sh (UNIX)
bin\CWODAEnv.bat (Windows)
bin/CWODAEnv.sh (UNIX)
connectors\messages\CwConnectorAgentMessages.txt

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

This adapter runs only on the current Adapter Framework, version 2.6.0, which handles InterChange Server versions 4.2.2 and 4.3.0.

Known problems and workarounds

The following problems have been found in this release:

Tracking
number
Description
41966 The JDBC ODA cannot generate a business object from the nickname of a stored procedure when using the Oracle thin driver, because the driver does not support analysis of Synonyms to StoredProcedures. To work around this, either use the actual stored procedure name to generate the business object using the ODA, or construct the business object manually.
43888 The JDBC ODA shows stored procedure node names with a ";1" suffix when analyzing an SQL Server database. This is an issue with the SQL Server database for which there are no fixes. To work around this problem, you can manually remove the ";1" in the ASI generated for the stored procedure attributes in the generated business object.
41967 The Framework cannot process more than 20,000 property values when displaying the ODA configuration properties or asking the user for business object definition-specific properties. Ensure that no more than 10,000 values are returned in the drop down list, or the ODA will hang.
N/A WebSphere Business Integration Adapters and InterChange Server do not support bi-di characters as part of business object and business object attribute names. Consequently, after the business object template is generated based on the database tables with column names containing bi-di characters, you must rename all business object names and attribute names that include non-Latin characters to include only Latin characters.
N/A In the JDBC ODA, Hebrew table and column names for the DB2 OS/390 IBM Universal JDBC driver restrict how non-Latin characters should be specified as part of an SQL query. In particular, it does not correctly process SQL queries having bi-di characters as part of table and column names if the table and column names are not enclosed by parentheses. Consequently, since business object templates generated by the JDBC ODA do not enclose table and column names in parentheses in the application-specific information (ASI), if you are using those templates for communication with OS/390 DB2 through the IBM Universal JDBC driver, you must modify the table and column names in the business object templates as follows:
All TN=<table name> appearances in the business object level ASI should be replaced with TN=”<table name>”
All CN=<column name> appearances in the business object attribute level ASI should be replaced with CN=”<column name>”
N/A Due to limitations of the DB2 OS/400 IBM Universal JDBC driver, table column names, including bi-di characters are excluded from the generated business object template. Consequently, only columns containing Latin names are considered during business object template generation. If a table has no Latin columns, no business object template is generated.
If you are using a DataDirect JDBC driver, you will see the following issues:
41973 The DataDirect SQL driver does not support analysis of TimeStamp type columns. For attributes that are linked to TimeStamp type columns in the database, correct the attribute type manually in the business object definition.
41977 When using the DataDirect SQL driver, the OracleApps ODA does not generate appropriate application-specific information for stored procedures that return result sets. The driver does not support analysis of the return type when the stored procedure returns a result set. For example, the stored procedure returns @RETURNVALUE, which the ODA cannot use to generate an attribute. To work around this, manually add the attribute in the business object definition.
The DataDirect Oracle driver does not provide information on keys when the business object is generated from the nickname of a table, and it does not support analysis of nicknames. To work around this, you must modify the business object after it is generated.

Documentation updates

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 Information Centers:

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.

Copyright IBM Corp. 1997, 2004