IBM WebSphere Adapter for JDBC, version 6.0.2.2 notes

This document contains the following sections:
Enhancements and fixes
New and modified connector properties
Upgrade notes

This table lists the enhancements and fixes in fix pack version 6.0.2.2.
Enhancements
#CRAPARTitleDetails
172741Enable Enterprise Metadata Discovery (EMD) for all manual application-specific information editing.
Symptom: To build a hierarachy of child business objects the user must manually change the business objects.
Resolution: EMD can build a hierarachy of both multiple and single cardinality child business objects, including KeepRelationship, Ownership, and Required application-specific information by getting input from the user and setting foreign keys appropriately in parent and child business objects.
272810Add the new property DriverConnectionProperties to Managed Connection Factory and Activation Specification
Symptom: There is no way to specify any driver-specific properties on the connection.
Resolution: Enable EMD to specify DriverConnectionProperties and add to the Managed Connection Factory and Activation Specification. They are used appropriately when establishing a connection to the database.
360808Add a prepared statement cache to the adapter
Symptom: Caching of prepared statements is not supported in the adapter.
Resolution: The adapter now supports prepared statement caching. To use a prepared statement cache in the adapter, create a data source and enable the prepared statement cache in WebSphere Application Server. Specify the data source JNDI name in the adapter for the benfits of prepared statement cacheing. This feature is available only if a data source is used to connect to the database.
472815Add support for generating appropriate application-specific information for globalized data types
Symptom: Certain globalized data types like NCHAR, NVARCHAR , and so on, are not supported.
Resolution: Support for the following globalized data types is now provided: NCHAR, NVARCHAR, NTEXT, TEXT, RAW, MONEY, and SMALLMONEY.
572805Provide support for wrapper business objects
Symptom: Wrapper business objects are not supported.
Resolution: Support is provided for the construction of wrapper business objects in the Enterprise Metadata Discovery using input provided by the user.
668834The Enterprise Metadata Discovery should to display stored procedure(SP) names as SPName (PkgName).
Symptom: The stored procedures are displayed in the EMD as PackageName.SPName, sorted by stored procedure name (SPName), not by package name (PackageName), making it difficult to easily locate a stored procedure. For example, if package A includes one stored procedure called DSP, and package B includes another stored procedure called CSP, the EMD displays these stored procedures in the following order: B.CSP A.DSP.
Resolution: Stored procedures are now displayed in the EMD as SPName (PackageName), sorted by SPName. For example, if package A includes one stored procedure called DSP, and package B includes another stored procedure called CSP, the EMD displays these two stored procedures in the following order: CSP(B) DSP(A).
786355Equivalent support of the WebSphere Business Integration Adapter application-specific information, UNVL, is needed in the JCA adapter.
Symptom: In the WebSphere Business Integration Adapter, when the connector retrieves data from the database and the SELECT statement returns a null value for an attribute, the connector ignores it by default. If a value has been specified for the UNVL parameter of the attribute's application-specific information, the adapter uses that value to represent the null value. This was not supported in the adapter.
Resolution: UNVL equivalent support is now provided.
Fixes
#CRAPARTitleDetails
187216JR26282The Retrieve operation returns length of the BLOB data instead of the actual BLOB data
Symptom: Instead of returning the complete BLOB contents, the adapter only returns the length of the blob data as a hexadecimal value.
Resolution: Fixed. The adapter returns the complete BLOB contents.
287658JR26244Trigger usage with MS SQL Server 2000 returns wrong User Identity (UID).
Symptom: With MS SQL Server 2000, when a row is inserted in a table, for instance "customer," a trigger fires and inserts a row in the event table. Both tables use the Identity column as the primary key. For further processing, the UID of the inserted "customer" row should be retrieved, but the adapter retrieves the UID of the row inserted into the event table instead.
Resolution: Fixed. The adapter returns the correct UID.
387349JR26243The Update operation on a business object with n-cardinality children creates the last child business object only if it is not there already.
Symptom: The child table has an integer data type automatically generated column as the primary key. When the Update operation is performed on a parent table with mulitple children having the primary key as unset (because the child table has an automatically generated primary key), the adapter creates only the last child business object.
Resolution: Fixed.
488947JR26628The JDBC adapter retrieves incorrect data for child objects when a parent business object contains two single cardinality children with foreign keys referring to the same attribute.
Symptom: When a business object contains two child objects of the same type representing foreign keys to the same table, the adapter retrieves two instances of the last child object, rather than one of each.
Resolution: Fixed. The adapter correctly retrieves the data for single cardinality children.
569043JDBC JCA with XA transaction with non-WPS (WebSphere Process Server) DataSource cannot connect to a local database.
Symptom: DataSource cannot connect to a local database with non-WPS (WebSphere Process Server).
Resolution: The DataSource is now created with the adapter.
687193The execute operation on the Stored Procedure (SP) fails when the SP has IN/OUT parameters.
Symptom: When Stored Procedure (SP) used with IN/OUT parameters, execute operation failed.
Resolution: Parameters of type IO are registered.
787159The adapter generates a ClassCastException exception for binary types within a stored procedure.
Symptom: When Stored Procedure (SP) used for binary types, adapter generates ClassCastException.
Resolution: Binary types are handled properly for stored procedure parameters.
889008Adapter throws the SQLException "maximum open cursors exceeded" after retrieving data from Oracle DB in certain requests.
Symptom: Adapter throws the SQLException "maximum open cursors exceeded" after retrieving data from Oracle DB in certain requests.
Resolution: Fixed. Adapter closes the cursors after retrieving the data.
969773JDBC adapter throws NullPointerException when using Custom delete query for inbound operation.
Symptom: When custom delete query used in Inbound operation, Adapter throws the NullPointerException.
Resolution: Fixed. The custom delete query operation works as expected.


This table lists new and modified connector properties
#VersionAdded or ModifiedPropertyLocation
16.0.2.2AddDriverConnectionPropertiesActivationSpec and ManagedConnectionFactory


To upgrade to the fix pack version 6.0.2.2, do the following.
1. Ensure that you have followed the "Installation Instructions" section in the download link before proceeding.
2. If you need to use the Fix Pack for EMD, delete the connector project in WebSphere Integration Developer, import the new RAR file, and apply the enterprise information system (EIS) specific dependency files.
   a. Open the Java build path for the SCA module and remove the Connector project that is selected on Projects tab.
   b. Open the dependency editor and remove the connector project.
   c. Delete the connector project from the workspace.
   d. Import the new RAR file. Add any dependency files from EIS specific application-specific information as needed.
   e. Open the Java build path for the SCA module and select the Connector project that is selected on the Projects tab.
   e. Open the dependency editor and add the connector project if it is not already present and select Deploy with Module.
3. If you need to update deployed applications on WebSphere Process Server, do the following:
   a. Select Update for the corresponding application on the WebSphere Process Server administrative console.
   b. Select Single Module with a relative path as name of the RAR file - CWYBC_JDBC.rar.
   c. Click Browse on the local file system to select the updated RAR file that has the changes.
   d. Select the default values in the remaining steps and click Finish. This will ensure that existing configurations, for example, are not changed and that only JAR files will be updated.


June 29th, 2007 6:00 PM
(C) 2007 IBM Corporation. Proprietary and Confidential. All Rights Reserved.