Fix (APAR):  PK23354

Status:  Fix

Release:  6.0.2.7,6.0.2.5

Operating System:  AIX,HP-UX,Linux,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  362643

Byte size of APAR:  28648

Date: 2006-04-13

Abstract:  A looseApp is one which is run with assets in the RAD workspace and if the JspBatchCompiler is used to compile such a looseApp an error was seen that the enterprise application is 

Description/symptom of problem:  
PK23354 resolves the following problem:

ERROR DESCRIPTION:                                              
When you try to run the JSPBatchCompiler against an application 
that is                                                         
inside the WebSphere Commerce development environment you end up
with                                                            
the following  exception.                                       
Exception:                                                      
D:\temp\profile\bin>JspBatchCompiler.bat -enterpriseapp.name    
TestEAR                                                         
JSPG0159I: Server name not supplied; using default: server1     
JSPG0160I: Compiling all webmodules                             
JSPG0153I: Initializing server...                               
JSPG0165I: Reading config file...                               
No web modules found for Enterprise Application TestEAR         
java.lang.reflect.InvocationTargetException                     
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native  
Method)                                                         

LOCAL FIX:                                                      

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Application Server users who use
JspBatchCompiler to compile an enterprise
application that is deployed from
Rational Application Developer(RAD).These
applications are run with assets in the
RAD workspace.

PROBLEM DESCRIPTION:
A looseApp is one which is run with
assets in the RAD workspace and if
the JspBatchCompiler is used to
compile such a looseApp an error was
seen that the enterprise application is
not found.

RECOMMENDATION:
None

Code modifications have been done in JspBatchCompiler code to
enhance the compilation of JSPs in looseApp.

PROBLEM CONCLUSION:                                             
The JspBatchCompiler was not initially coded to compile         
looseApps and the batch compiler code has been modified to      
address looseapps.                                              
The official release is expected to be available in fixpack     
6.0.2.11.                                                       
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
__ Application Server (Express or BASE)
__ Network Deployment (ND)
__ WebSphere Business Integration Server Foundation (WBISF)
__ Edge Components
__ Developer
__ Extended Deployment (XD)

Install Fix to:
Method:
__ Application Server Nodes
__ 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 <was_root>/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 PKxxxxx.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 (PKxxxxx.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 (PKxxxxx.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: