eFix (APAR): pq58724

For Release: WebSphere 4.0.2

For Edition: WebSphere AE, AEs

For AffectedComponents: AE_admin_server, AE_server, Server, Server_Common, J2EEClient, JTCClient

CMVC defect: 117813 

Byte size of APAR: 1,060k

Date: 03/11/2002

Abstract: Naming Exception on startup of AE (And AEs within WSAD)

Description/symptom of problem: 
Upon migrating to 4.0.2, and making no modifications to the user
workspace/configuration, none of the EJB projects would startup in the server.  
Further investigation showed the user was trying to
use the default datasource that was configured in the server
for their EJB module/beans - hence they did not want to bind a
datasource JNDI name to each individual module. If the module
is explicitly bound with a datasource JNDI name, the server
will start successfully.  


APPLYING THE EFIX:
***************************************************************************
NOTE FOR USERS APPLYING THIS EFIX ON AE (AES does not require this other eFix):
 
      - Before applying this eFix on AE, you must FIRST apply efix PQ57046 BUT DO NOT 
	RUN THE TCL SCRIPT YET (run it after applying eFix PQ58724)
      - Then apply this (PQ58724) eFix by following the instruction below
      - Run the tcl scrip (as described in step 7 below)
***************************************************************************


Directions to apply efix:

1) Create temporary "efix" directory to store the zip/tar file:
             AIX: /tmp/WebSphere/efix
   Solaris/Linux: /tmp/WebSphere/efix
         Windows: c:\temp\WebSphere\efix

2) Copy zip/tar file to the directory

3) Unzip/untar the file

4) Shutdown WebSphere

5) Run the jar file with the following command answering questions/prompts as they appear:
   java -jar PQ58724_eFix.jar

6) Restart WebSphere

7) ***** AE ONLY *****
   (AES does not require this step)
   
   Use WSCP to execute the tcl script which was created into the <WASHOME>/WebSphere/AppServer/bin 
   directory; this will rebind all DataSources, which 1) fixes existing DataSources to not 
   store the JNDI name as the DataSource name, and 2) forces all DataSources to be converted 
   to the 4.0.2 version.
   
   For example:
   wscp -f rebind_datasources.tcl
   *******************

8) The temp directory may be removed but the zip/tar file should be saved.  Do not remove 
   any files created and stored in the <WASHOME>/WebSphere/AppServer/efix/PQ58724 directories.
   These files are required if an efix is to be removed.



Directions to remove an efix:

NOTE:  EFIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED.  DO NOT REMOVE AN EFIX UNLESS
       ALL EFIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.  YOU MAY REAPPLY ANY REMOVED EFIX.

Example:  If your system has efix1, efix2, and efix3 applied in that order and efix2 is to be
          removed, efix3 must be removed first, efix2 removed, and efix3 re-applied.


1) Change directory to the efix location (<WASHOME>/WebSphere/AppServer/efix/PQ58724).

2) Shutdown WebSphere

3) Run the backup jar file with the following command:
   java -jar backup_PQ58724.jar

4) Restart WebSphere



Directions to re-apply an efix:

Follow the instructions for applying an efix.  If the backup files still exist (from the 
previous efix application), you will be prompted to overwrite.  Answer "yes" at the overwrite 
prompts.


Trouble shooting
--------------------------------------------------------------------------------------
o  If an efix complains about the container type and you are sure it should match, contact
   WebSphere L2 Support for assistance with the -SkipContainerCheck option to the efix jar.

o  If the efix complains about the version of XML parser, move the file 
   $WASROOT/jre/lib/ext/xerces.jar to a temporary location (such as c:\temp), load the efix 
   and move the file back to it's original location.



Additional Information:
------------------------------------------------------------------