PK74387: Meet-in-the-middle is not using the InitialDatabaseDefinition

Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• Meet-in-the-Middle does not use the InitialDatabaseDefinition
  introduced in Rational Application Developer v7.0.0.6 and
  therefore does not use the UI selected database vendor/version
  but rather the actual database vendor/version of the
  underlying database.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of WebSphere Application Server   *
  *                  Toolkit v6.1.1 and Rational Application     *
  *                  Developer v7.0                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: A CMP backend created with              *
  *                      Meet-in-the-middle does not use the     *
  *                      Database vendor/version that is         *
  *                      selected in the wizard page.            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The CMP backend construction will use the actual database
  vendor/version of the underlying database rather than the
  vendor/version selected in the UI when creating.  This can
  result in a CMP backend with a name that is different than
  what is expected (or supported) resulting in EJB Deploy code
  generation problems.
  

Problem conclusion

• The Meet-in-the-middle backend construction will now use the
  database vendor/version that is selected in the
  Meet-in-the-middle connection wizard.
  
  The fix for this APAR is currently targeted for inclusion in
  the WebSphere Application Server Toolkit fixpack 6.1.1.9. and
  Rational Application Developer fixpack 7.0.0.9.  Please refer
  to the following Recommended Updates page for WebSphere
  Application Server Toolkit delivery information:
  http://www.ibm.com/support/docview.wss?uid=swg27004980
  and the following Recommended Updates page for Rational
  Application Developer delivery information:
  http://www.ibm.com/support/docview.wss?uid=swg27007823
  

Temporary fix

Comments

APAR Information

• 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

  WEBAPP SERVER A

• Fixed component ID

  5724J0820

Applicable component levels

• R610 PSY

     UP