PK88548: CEI CHANGE OF DERBY PROVIDER IN V7.0 THROWING EXCEPTIONS

Fixes are available

APAR status

Closed as program error.

Error description

The issue is caused by Common Event Infrastructure (CEI)
changing the default setting of the Derby JDBC Provider that is
used.

In V7.0 Application Server added support for JDBC 4.0 by giving
an option to use a new JDBC Provider for Derby - "Derby JDBC
Provider 40". So it has two options:
- "Derby JDBC Provider 40" (for JDBC 4.0)
- "Derby JDBC Provider" (for JDBC 3.0)

Usually the end user gets to choose which provider type he
wants and in WebSphere Process Server and WebSphere Enterprise
Service Bus (ESB) products we do give this option for
configuring the components. Currently, the V6.2 code of
WebSphere Process Server and WebSphere ESB uses the JDBC 3.0
providers and depends on CEI also using the same provider.

However when we moved to V7.0 CEI changed the setting to JDBC
4.0 which is causing problems. We would like CEI to give an
option to select either 3.0 or 4.0 and should not force the
stack products to stick to one provider.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server V7.0 users *
*                  who configure Common Event Infrastructure   *
*                  with the Derby database.                    *
****************************************************************
* PROBLEM DESCRIPTION: The Common Event Infrastructure         *
*                      configuration with Derby database       *
*                      creates the JDBC provider based on      *
*                      JDBC 4.0 driver version                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The configuration process of Common Event Infrastructure with
Derby database creates the WebSphere Application Server
data source based on the JDBC 4.0 driver version (considered
as the default) and this represents a switch from the current
implementation based on the JDBC 3.0 driver implementation.
The deployEventService AdminTask and the
configEventServiceDerbyDB AdminTask should consider the JDBC
3.0 driver version as the default configuration.

Problem conclusion

The configuration process with Derby database has been changed
according to the below scenarios:
1.  deployEventService - The functionality is to deploy CEI
into selected target and configure it with Derby based on a DS
that uses 'Derby JDBC Provider (XA)'  - therefore 3.0 driver
version.
2. configEventServiceDerbyDB - for this AdminTask we added a
new optional parameter -jdbcDriverVersion  - with the
following possible/acceptable values 3.0 / 4.0 . The usage of
3.0 values does configure the JDBC provider based on the JDBC
3.0 driver version whereas using the 4.0 value will produce
the JDBC provider based on the JDBC 4.0 driver version.
The behavior is:
a. -jdbcDriverVersion not specified in the AdminTask  - The
configuration will be performed using 'Derby JDBC 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 'Derby JDBC
Provider (XA)', therefore 3.0 driver version.
d. -jdbcDriverVersion specified with the '4.0' value supplied
- The configuration will be performed using 'Derby JDBC
Provider 40 (XA)', therefore 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 above statements apply both to Derby Embedded and Derby
Network database versions.


The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.7.  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
PK88548
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-06-11
Closed date
2009-07-31
Last modified date
2009-07-31

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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PK88548: CEI CHANGE OF DERBY PROVIDER IN V7.0 THROWING EXCEPTIONS

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY

Document Information

Share your feedback

Need support?