Fix (APAR): PK41097 Status: Fix Release: 6.1.0.7,6.1.0.5 Operating System: AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux Red Hat - pSeries,Linux zSeries,OS/390,OS/400,Solaris,Windows,z/OS Supersedes Fixes: CMVC Defect: 425164 Byte size of APAR: 48014 Date: 2007-03-23 Abstract: IBM WebSphere Application Server EJB Container should allow for the expansion of the CMP Connection Factor JNDI Name. Description/symptom of problem: PK41097 resolves the following problem: ERROR DESCRIPTION: When a use sets a variable as part of the Container Managed Persistence (CMP) Connection Factory Java Naming and Directory Interface (JNDI) name, there is a potential that the variable may not get expanded by WebSphere Enterprise Java Beans (EJB) Container. If the variable isn't expanded, the CMP Connection Factory will be bound by the wrong JNDI name, thus not allowing it to be looked up in naming as the user had expected. LOCAL FIX: PROBLEM SUMMARY USERS AFFECTED: Users of WebSphere Application Server version 6.1 who use variables in their CMP Connection Factory JNDI Name. PROBLEM DESCRIPTION: IBM WebSphere Application Server EJB Container should allow for the expansion of the CMP Connection Factor JNDI Name. RECOMMENDATION: None WebSphere Application Server EJB Container should allow for the expansion of the CMP Connection Factor JNDI Name when a user's JNDI name contains a user defined WebSphere Application Server variable. Current code does not expand variables in the CMP Connection Factory JNDI Name. An application may want to have the ability to allows for variable expansion of their CMP Connection Factory JNDI Name. This APAR will provide a custom property to enable or disable this behaviour. PROBLEM CONCLUSION: Support for the expansion of variables used in a CMP Connection Factory JNDI Name has been added by the addition of a new EJB Container Custom Property: "com.ibm.websphere.ejbcontainer.expandCMPCFJNDIName", and can take the values of "true" or "false". This EJB Container property is set as a JVM System Property as follows: 1) In the Administrative Console, select Servers 2) Select Application Servers 3) Select the server you want to configure 4) Select Java and Process Management 5) Select Definition 6) Select Java Virtual Machine 7) Select Custom Properties. 8) Select the New box. 9) In the Name entry field, type com.ibm.websphere.ejbcontainer.expandCMPCFJNDIName. In the Value entry field, type true or false. If the value is "true" then the EJB Container will expand a variable when found in the CMP Connection Factory JNDI Name. If the value is "false", which is the default, then the EJB Container will not expand a variable. The default value of the System Property is equal to a setting of "false", which would be the behaviour prior to the APAR. The fix for this APAR is currently targeted for inclusion in fixpack 6.1.0.9. Please refer to the recommended updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 Directions to apply fix: NOTE: Choose the: 1) Release the fix applies to 2) The Editions that apply 3) Delete the Editions & Methods that do not apply and this Note Fix applies to Editions: Release 6.0 _X_ Application Server (Express or BASE) _X_ Network Deployment (ND) Install Fix to: Method: __ Application Server Nodes _X_ Deployment Manager Nodes __ Both NOTE: The user must: * Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V6.0.2.2 or newer of the Update Installer. This can be checked by reviewing the level of the Update Installer in file /updateinstaller/version.txt. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 For detailed instructions to Extract the Update Installer see the following Technote: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21205400 1) Copy 6.1.0.7-WS-WAS-IFPK41097.pak file directly to the maintenance directory 2) Shutdown WebSphere Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to. 3) Launch Update Installer 4) Enter the installation location of the WebSphere product you want to update. 5) Select the "Install maintenance package" operation. 6) Enter the file name of the maintenance package to install (6.1.0.7-WS-WAS-IFPK41097.pak file which was copied in the maintenance directory). 7) Install the maintenance package. 8) Restart WebSphere Directions to remove fix: NOTE: * The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED * DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED * YOU MAY REAPPLY ANY REMOVED FIX Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied. 1) Shutdown WebSphere Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against. 2) Start Update Installer 3) Enter the installation location of the WebSphere product you want to remove the fix. 4) Select "Uninstall maintenance package" operation. 5) Enter the file name of the maintenance package to uninstall (6.1.0.7-WS-WAS-IFPK41097.pak). 6) UnInstall maintenance package. 7) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere. 2) Follow the Fix instructions to apply the fix. 3) Restart WebSphere. Additional Information: