13 August 2001

Product: WebSphere Advanced Server, version 3.5.3, 3.5.4

APAR PQ51387 E-fix Documentation

Problem Description:

     JNDI clients in WebSphere Advanced Server, version 3.5, previous to
     version 3.5.5, cannot use WebSphere Advanced Server, version 4.0,
     name servers.  This e-fix supercedes e-fix PQ48255, which caused
     admin server start-up failure with LTPA security enabled.

Contents of this e-fix:

     PQ51387.ujc.jar:

          Contains a revision to WebSphere's JNDI CosNaming plug-in
          implementation.  The revision includes changes to some files
          contained in the WebSphere file, ujc.jar, plus some new files
          added to ujc.jar.  This revision allows JNDI clients running in
          a WebSphere 3.5.3 or 3.5.4 environment to access WebSphere 4.0
          name servers.

     PQ51387.ns.jar:

          Contains an update to a file which resides in the WebSphere file,
          ns.jar.

     PQ51387.ibmwebas.jar:

          Contains an update to a file which resides in the WebSphere file,
          ibmwebas.jar.

     README.TXT

          This text file.

How to apply fix: 

     You must refresh ujc.jar, ns.jar, and ibmwebas.jar with some new and
     updated class files.  Listed below are the steps to update ujc.jar,
     ns.jar, and ibmwebas.jar:

     1) Stop the Admin Server and all application servers.

     2) Make sure the jar command can be found with your PATH setting.  If the
        jar command is not found when you type "jar" from the command line, add
        it to your PATH as follows:

              UNIX: . $WAS_HOME/bin/setupCmdLine.sh
                    PATH=$JAVA_HOME/sh:$JAVA_HOME/bin:$PATH
                    export PATH
              WIN:  %WAS_HOME%\bin\setupCmdLine.bat
                    set PATH=%JAVA_HOME%\bin;%PATH%

              where $WAS_HOME (%WAS_HOME%) is the WebSphere AppServer
              directory.

     3) Refresh ujc.jar:

        a) Save a copy of the original version of ujc.jar, which is found
           in the directory $WAS_HOME/lib, where $WAS_HOME is the WebSphere
           AppServer directory.

        b) Create a temporary directory, e.g., /tmp/PQ51387/ujc
   
        c) Copy PQ51387.ujc.jar to the temporary directory.

        d) Make the temporary directory your current directory.

        e) Extract the contents of PQ51387.ujc.jar into the temporary
           directory, e.g.,

           jar xvf PQ51387.ujc.jar

        f) Update ujc.jar with the class file extracted from PQ51387.ujc.jar,
           e.g.,

           UNIX: jar uvf $WAS_HOME/lib/ujc.jar com/*
           WIN:  jar uvf %WAS_HOME%\lib\ujc.jar com/*

           where $WAS_HOME (%WAS_HOME%) is the WebSphere AppServer directory.

     4) Refresh ns.jar:

        a) Save a copy of the original version of ns.jar, which is found
           in the directory $WAS_HOME/lib, where $WAS_HOME is the WebSphere
           AppServer directory.

        b) Create a temporary directory, e.g., /tmp/PQ51387/ns
   
        c) Copy PQ51387.ns.jar to the temporary directory.

        d) Make the temporary directory your current directory.

        e) Extract the contents of PQ51387.ns.jar into the temporary directory,
           e.g.,

           jar xvf PQ51387.ns.jar

        f) Update ns.jar with the class file extracted from PQ51387.ns.jar,
           e.g.,

           UNIX: jar uvf $WAS_HOME/lib/ns.jar com/*
           WIN:  jar uvf %WAS_HOME%\lib\ns.jar com/*

           where $WAS_HOME (%WAS_HOME%) is the WebSphere AppServer directory.

     5) Refresh ibmwebas.jar:

        a) Save a copy of the original version of ibmwebas.jar, which is found
           in the directory $WAS_HOME/lib, where $WAS_HOME is the WebSphere
           AppServer directory.

        b) Create a temporary directory, e.g., /tmp/PQ51387/ibmwebas
   
        c) Copy PQ51387.ibmwebas.jar to the temporary directory.

        d) Make the temporary directory your current directory.

        e) Extract the contents of PQ51387.ibmwebas.jar into the temporary
           directory, e.g.,

           jar xvf PQ51387.ibmwebas.jar

        f) Update ibmwebas.jar with the class file extracted from
           PQ51387.ibmwebas.jar, e.g.,

           UNIX: jar uvf $WAS_HOME/lib/ibmwebas.jar com/*
           WIN:  jar uvf %WAS_HOME%\lib\ibmwebas.jar com/*

           where $WAS_HOME (%WAS_HOME%) is the WebSphere AppServer directory.


     6) Restart the Admin Server and application servers.

        To verify that the fix has been applied correctly, turn tracing on
        (com.ibm.ejs.ns.jndi=all=enabled), run an application which performs
        a JNDI operation, and look for the string,

           CNInitialContextFactory.java, naming, ASV35, ver. 1.11

        in the trace output.  For an application server, this string should
        appear in the trace output after simply starting the server.