PK47445: DURING DEPLOYMENT DEFAULT CONNECTION FACTORY OPTION IS NOT RECOG NIZED

Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
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
PK79521; 6.0.2.21: filenotfoundexception during install of PK47445

APAR status

• Closed as program error.

Error description

• Enterprise Java Beans deploy via module update does not update
  the connection factory.
  Hence Enterprise Java Beans 2.0 modules containinug 1.x beans
  will throw Java Naming and Directory Interface errors.
  For example,
  WebSphere Commerce includes Enterprise Java Beans 2.0 modules
  that contains 1.x beans.
  
  This Enterprise Java Beans module has a Container Managed
  Persistence Connection Factory defined and works fine in
  Rational Application Developer but not in WebSphere Application
  Server.
  Example ibm-ejb-jar-bnd.xmi looks like:
  <defaultCMPConnectionFactory
  xmi:id="CMPConnectionFactoryBinding_1069893248765"
  jndiName="jdbc/WebSphere Commerce DB2 DataSource xxxxxxx"
  resAuth="Per_Connection_Factory"/>
  
  Enterprise Java Beans module is deployed into WebSphere
  Application Server using
  
  $AdminApp update wc modulefile {-operation update -contents
  D:/WebSphereCommerceServerExtensionsData.jar -contenturi
  WebSphereCommerceServerExtensionsData.jar
  -defaultbinding.datasource.jndi "jdbc/WebSphere Commerce DB2
  DataSource demo" -defaultbinding.cf.jndi "jdbc/WebSphere
  Commerce DB2 DataSource demo" -defaultbinding.cf.resauth
  Per_Connection_Factory -usedefaultbindings }
  
  During the deployment, specify both
  defaultbinding.datasource.jndi and defaultbinding.cf.jndi as
  shown above. When the application is started and the new
  Enterprise Java Bean is used, it will throw a Java Naming and
  Directory Interface error "Datasource xxxx could not be
  found..."  This is because only the default datasource is
  updated but not the connection factory.
  
  Since the original connection factory is only correct within the
  Rational Application Developer environment, it will throw the
  Java Naming and Directory Interface error when running inside
  the WebSphere Application Server environment.
  
  This fix is required to properly update the connection factory
  or remove the value from the binding file so that it is not used
  during runtime.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server users of   *
  *                  versions 6.0.2 and 6.1.                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: During application deployment or        *
  *                      update, "defaultCMPConnectionFactory"   *
  *                      binding is ignored.                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  During application deployment or update, the
  "defaultCMPConnectionFactory" binding specified through the
  option "-defaultbinding.cf.jndi" (wsadmin - AdminApp option)
  is ignored, if all the Container Managed Persistence (CMP) beans
  are of version 1.x.
  
  The 2.x version of Enterprise Java Beans modules allows you to
  define a default connection factory, even if all the CMP beans
  are of version 1.x. The AdminApp commands' option
  "-defaultbinding.cf.jndi" is to specify a new or override the
  existing value of default connection factory. But, if all the
  CMPs beans are 1.x version, application deployment ignores the
  value specified with option "-defaultbinding.cf.jndi".
  

Problem conclusion

• The fix will recognize the value specified with the option
  "-defaultbinding.cf.jndi", if the Enterprise Java Beans module
  version is 2.x,though the bean versions are 1.x
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 6.0.2.23 and 6.1.0.13.
  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 is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• ADMIN
  

Fix information

• Fixed component name

  WEBSPH APP SERV

• Fixed component ID

  5724J0800

Applicable component levels

• R60A PSY

     UP

• R60H PSY

     UP

• R60I PSY

     UP

• R60S PSY

     UP

• R60W PSY

     UP

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP