PQ65145: PTF 3 AND 4 CHECKS FOR THE J2C.JAR FILE IN THE WRONG LOCATION CAUSING THE J2C NOT TO UPDATE.

 A fix is available

4.0.5: WebSphere Application Server Version 4.0 Fix Pack 5 (Version 4.0.5)



APAR status
Closed as documentation error.

Error description
The PTF silent install fails to update / install the Connector
Architecture (J2C) because it is looking in the wrong
directory for the j2c.jar file.

The installer displays the following message on a silent
install:
=========================================================
Testing for update of the J2C Connector Architecture.
The Connector Architecture (J2C) jar file is not present:
"F:\WebSphereAE\AppServer\java\lib\j2c.jar"

The Connector Architecture (J2C) installation has not been
forced by the environment ('FORCEJ2C').
Silent Mode: Skipping update of Connector Architecture (J2C)
=========================================================
Local fix Problem summary
****************************************************************
* USERS AFFECTED: Users installing FixPak 3 or FixPak 4 of     *
*                 WebSphere Application Server Advance Edition *
*                 on any platform.                             *
****************************************************************
* PROBLEM DESCRIPTION: The PTF 3 and PTF 4 installer does not  *
*                      install the J2C update during a silent  *
*                      install.                                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
During an install of PTF 3 or PTF 4 of WebSphere Application
Server AE the J2C update will not occur on a silent install
because the installer is looking in the wrong directory
for the j2c.jar file.  The installer is looking in the
JDK_UPDATE_HOME/lib directory when it should be looking in the
WAS_UPDATE_HOME/lib directory.  This will not allow the J2C
update to occur.
The interactive install also looks in the wrong directory
however the user is prompted if they want to install the J2C
update.  If they choose 'Yes' then the J2C update will install
properly in the WAS_UPDATE_HOME/lib directory.
Problem conclusion
The interactive installation of FixPak 3 and 4 will still
install the J2C update, however the logs that are displayed will
be wrong.  The installer will display that it could not find the
j2c.jar file but then it will ask the user if they want to
install the Connection Architecture for WebSphere.  If the user
chooses 'Yes' then the J2C will be installed properly under the
WAS_UPDATE_HOME/lib directory.
On silent installs, the user must set the FORCEJ2C system
variable to 'true' or use the -Connector command line option in
order to force the install of J2C.
The syntax for the command line should look like this:
Unix:
./install.sh -silent -Connector

Windows:
install.bat -silent -Connector
Temporary fix Comments
APAR information
APAR number PQ65145
Reported component name WEBSPHERE AE AI
Reported component ID 5630A2200
Reported release 400
Status CLOSED DOC
PE NoPE
HIPER NoHIPER
Submitted date 2002-08-09
Closed date 2002-08-09
Last modified date 2002-09-10

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

SRLS

Fix information

Applicable component levels


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ65145
IBM Group: Software Group
Modified date: Sep 10, 2002