IBM WebSphere Adapter for JDBC, version 7.0.1.1 IF01 notes

This document contains the following sections:

Enhancements and fixes

New and modified connector properties

Upgrade notes

This table lists the fixes in 7.0.1.1 IF01 Fixes # CR APAR Title Details 1 100685 JR35739,JR35591 Standalone adapter failed to work in a sequence of local global transaction. Symptom: Firstly run local transaction, secondly run global transaction PI file and then run local transaction PI file, there's some transaction related errors happen. Resolution: With this fix, the sequence of local global transaction can work well. 2 03847 JR40904 Implicit conversion from VARCHAR to NUMERIC not supported in Sybase Database Symptom: Updating/Deleting the Event id field of Event table causes conversion exceptions Resolution: Event Id field of the Event Table should be addressed by BigDecimal rather than a String in the Adapter. BigDecimal is the standard Java type for JDBC type mapping w.r.t Numeric types This table lists the fixes in 7.0.1.1 Fixes # CR APAR Title Details 1 93532 Replace XSMode SPI of XSMetaData with SDOUtil.getMaxLength method. Symptom: Resolution: 2 100345 Remove the WAS private API call in adapter code(transaction relate code). Symptom: Resolution: 3 100383 When "assuredOnceDelivery" is false and there is a event delivery failure, the status of the event is "0" and not changed to "-1". Symptom: When "assuredOnceDelivery" is false and there is a event delivery failure, the status of the event is "0" and not changed to "-1" and the event will be polled infinitely. Resolution: When "assuredOnceDelivery" is false and there is a event delivery failure, the status of the event becomes "-1" successfully.

This table lists new and modified connector properties # Version Added or Modified Property Location There is no new connector property introduced/modified for this version of fix pack.

To upgrade to the fix pack version 7.0.1.1, 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 Interim Fix 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.    f. 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. Stop the deployed application.    b. Select Update for the corresponding application on the WebSphere Process Server administrative console.    c. Select Replace or add a single file with a relative path as name of the RAR file - CWYBC_JDBC.rar.    d. Click Browse on the local file system to select the updated RAR file that has the changes.    e. 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.    f. Start the application again.

October 27th, 2011 6:00 PM

(C) 2009 IBM Corporation. Proprietary and Confidential. All Rights Reserved.