Fix (APAR):  PM91417

Status:  Fix

Release:  8.0.0.7,8.0.0.6,8.0.0.5

Operating System:  AIX,HP-UX,IBM i,Linux,Solaris,Windows,z/OS

Supersedes Fixes:  PM94981

CMVC Defect:  xxxxxx

Byte size of APAR:  918921

Date: 2014-01-07

Abstract:  provide option for backwards compatibility for earexpander

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

ERROR DESCRIPTION:                                              
An option is necessary to provide backwards compatibility       
for having the EARExpander command line utility extract files   
from JAR files in all locations, not just in JavaEE active      
locations.                                                      

LOCAL FIX:                                                      
n.a                                                             

PROBLEM SUMMARY

USERS AFFECTED:
 All users of IBM WebSphere Application
Server

PROBLEM DESCRIPTION:
Partial application updates will not
update JARs in non-active Java
EE locations.

RECOMMENDATION:
None

Applications deployed to the WebSphere Application Server by
default only expand archives in active Java EE locations.  For
example, JARS in a WAR's WEB-INF/lib directory are active.
JARs in other locations within a WAR are not active.
Because JARs not in active locations are not expanded, partial
application updates are not applied to these JARs.  (Whole JAR
replacements are applied to these JARs.)
For example, the file "SampleScript.js" having the following
packaging structure is not updated:
SampleEAR.ear/
SampleWAR.war/
WEB-INF/SampleDir/NestedSampleDir/
SampleJar.jar/
SampleScript.js
Expansion is performed by internal processing steps, including
deployment steps, and including expansions performed by the
earExpander script.

PROBLEM CONCLUSION:                                             
A custom property has been introduced which enables expansion of
all archives, even those outside of active Java EE locations:   
                                                                
org.eclipse.jst.j2ee.commonarchivecore.openAllArchives=true     
                                                                
By default, the custom property value is false. Setting the     
value true will revert the fix introduced by PM42643, and       
set the server to expand all archives. This should be done      
sparingly since setting the server to expand archives outside   
of active Java EE locations provides the best performance, and  
avoids any problems caused by non-valid archives. For example,  
simple corruption of an archive file, or use of multi-byte      
characters for entries in a archive file.                       
                                                                
To enable expansion of non-standard archives during deployment, 
set the property on the processes involved with the deployment, 
that is, on the Application Server process, and, if a Deployment
Manager is being used, on the Deployment Manager process.       
                                                                
To enable expansion by the earExpander script, set the property 
as a Java Custom property by editing the earExpander script.    
                                                                
The property is not applied to JARs within JARs.  JARs within   
JARs will still not be expanded, even with the property set to  
true.                                                           
                                                                
Note that all JARs in EAR files are active and all JARs in RAR  
files are active.  The processing of JARs in EAR files and      
JARs in RAR files is not affected by the custom property.       
                                                                
                                                                
The fix for this APAR is currently targeted for inclusion in    
fix packs 7.0.0.31, 8.0.0.8, and 8.5.5.2.  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:  Fix applies to Editions:
Release 8.0
_X_ Application Server (Express or BASE)
_X_ Network Deployment (ND)
__ Edge Components
__ Developer

Install Fix to all WebSphere installations unless special instructions are included below.

Special Instructions: None

NOTE:
The user must:
* Logged in with the same authority level when unpacking a fix, fix pack or refresh pack.
* Be at V1.4.3 or newer of the Installation Manager. Certain iFixes may require a newer version of the Installation Manager and the Installation Manager will inform you during the installation process if a newer version is required.

The IBM Information Center can provide details, if needed, on the use of the Installation Manager to apply the iFixes.
http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp.  Shutdown WebSphere Application Server before applying the iFixes.  Restart WebSphere Application Server after applying the iFixes.

Directions to remove fix:  

The IBM Information Center can provide details, if needed, on the use of the Installation Manager to remove the iFixes.
http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp.  Shutdown WebSphere Application Server before removing the iFixes.  Restart WebSphere Application Server after removing the iFixes.

Directions to re-apply fix:  
1) Shutdown WebSphere Application Server.

2) Follow the Fix instructions to apply the fix.

3) Restart WebSphere Application Server.



Additional Information: