eFix (APAR): PQ63508

Status: efix

For Release: WebSphere 4.0.2, 4.0.3

For Edition: WebSphere AE

For ContainerTypes: AEServer

For Operating System: All supported platforms for WebSphere AE

Supersedes eFixes: PQ58248 PQ60772

CMVC defect: PQ63508

Date: 07/30/02

Abstract: On console, appserver environment var overwritten when update other properties.

Description/symptom of problem: 

On console, appserver environment variable overwritten to null or other appserver's environment values
when update other appserver properties.

Example on how to reproduce problem with env var on other servers get   
changed when changed one server:                                      
0. WAS setup with 2 appservers A and B                                  
1. On ServerA General tab, change env var to {foo,bar}, click OK, click 
APPLY                                                                   
2. go to ServerB, DO NOT open Environment Editor on ServerB, go         
directly to JVM Settings tab, change java heap size, click APPLY        
3. go to ServerB General tab, open Environement Editor, whatever values 
B had are gone, values now {foo,bar}   


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 <jarfile name>

   If WebSphere is in a different directory than the default one then use:
   java -jar <jarfile name> -targetDir <dirName> 

   Use
   java -jar <jarfile name> -?
   to get a list of options.
   

6) Restart WebSphere

7) 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/<APAR#> 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/<APAR#>).

2) Shutdown WebSphere

3) Run the backup jar file with the following command:
   java -jar <backup_APAR#>

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:
------------------------------------------------------------------
This is a cumulative efix. In addition to the description above, applying
this efix solves the following problems:

(From PQ58248)
Abstract: Allow creating the multiple virtual hosts with the different names but the duplicate 
alias lists in Admin Console and also allow deploying multiple Enterprise applications 
with the duplicate context root and the duplicate virtual host in the Admin Console and WSCP.

Description/symptom of problem: 

1. When attempting to create the virtual hosts in the AdminConsole with the different names but 
the duplicate alias list in Admin Console, the user would get the error message "fail to create 
virtual hosts" and cannot proceed.  

2. When attempting to deploy the enterprise applications (web) with the duplicate context root 
"duplicate context root error" and cannot proceed the installation.


(From PQ56639)
Abstract: CAN NOT SET THE "CONNECTION CACHE MAXIMUM" FOR OBJECT REQUEST BROKER TO A VALUE HIGHER 
THAN 256 VIA THE ADMIN CONSOLE.

Description/symptom of problem: 

When attempting to set the "Connection cache maximum" or "Connection cache minimum" field in the 
Object Request Broker property sheet to a value higher than 256, the AE admin console will display 
an error dialog indicating that the maximum value for the field is 256 only.

(From PQ60772)

Abstract: The WSCP fails to validate the user/group names on role-user/group mapping when 
uses the LTPA auathentication. 

Description/symptom of problem: 

1. When using wscp, uses a short user or group name for role-user/group mapping, the install 
will successfully, but it will cause a 403 error (Authorization fails) when accessing the bean.
  
2. When using wscp, uses a full DN user or group name, application install failed.