Fixes are available
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for IBM i
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Windows
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for AIX
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for HP-UX
7.0.0.9: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Solaris
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Linux
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
PK96304; 7.0.0.7: unable to configure dataserver on cei
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
The Common Event Infrastructure (CEI) configuration administrative task does not support automatically configuring the DB2 DataServer driver based DataSource.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server V7.0 users * * who configure Common Event * * Infrastructure(CEI) with a DB2 database. * **************************************************************** * PROBLEM DESCRIPTION: Configuring the Common Event * * Infrastructure with a DB2 database * * does not support data source based on * * the IBM Data Server Driver for JDBC. * **************************************************************** * RECOMMENDATION: * **************************************************************** The configuration process of Common Event Infrastructure with DB2 database creates the WebSphere Application Server data source based on the DB2 Universal JDBC Driver Provider (XA) driver version (considered as the default). Common Event Infrastructure configuration supports the data source to be configured with a JDBC Provider using IBM Data Server Driver as well. If you need to base your data source on the IBM Data Server Driver for JDBC, you will be able to do so by using a manual procedure via the Administrative Console. The automatic configuration process for Common event Infrastructure should support this case as well.
Problem conclusion
The configuration process with DB2 database has been changed by adding to the configEventServiceDB2DB configuration Admin Task a new optional parameter -jdbcDriverVersion that will accept the following possible/acceptable values 3.0 / 4.0. The usage of 3.0 values does configure the JDBC provider based on the DB2 Universal JDBC Driver Provider (XA) driver version whereas using the 4.0 value will produce the JDBC provider based on the IBM Data Server Driver for JDBC version. The introduced behavior is: a. -jdbcDriverVersion not specified in the AdminTask - The configuration will be performed using 'DB2 Universal JDBC Driver Provider (XA)', therefore 3.0 driver version. b. -jdbcDriverVersion specified but no value supplied - Will raise an exception as -jdbcDriverVersion needs a parameter, then if the user go so far as to use the parameter but does NOT supply a value, we give an error stating like in the following example "CEIIN0739E No value was specified for the jdbcDriverVersion parameter. ¯ ½ c. -jdbcDriverVersion specified with the '3.0' value supplied - The configuration will be performed using ' DB2 Universal JDBC Driver Provider (XA)', therefore 3.0 driver version. d. -jdbcDriverVersion specified with the '4.0' value supplied - The configuration will be performed using 'DB2 Using IBM JCC Driver (XA)', therefore based on the provider that supports JDBC 4.0 specification using the IBM Data Server Driver for JDBC and SQLJ 4.0 driver version. e. -jdbcDriverVersion specified with a value OTHER than 3.0 or 4.0 - Will raise an exception like in the following example: "CEIIN0701E The parameter jdbcDriverVersion contains the value <wrong_value>, which is not valid. Valid values are: 3.0, 4.0." The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.9. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PK96304
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-09-16
Closed date
2009-11-04
Last modified date
2009-11-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800
Applicable component levels
R700 PSY
UP
Document Information
Modified date:
24 October 2021