Status:	     This is a efix 

For Release: WebSphere 4.0, 4.0.1

For Edition: WebSphere AE

For ContainerTypes: AEServer

For Operating System: ALL

Supersedes eFixes:  NONE

CMVC defect: PQ55060

Byte size of APAR: 849K

Date: 11/27/01

Abstract: XMLConfig is not creating application server with  unique transport port is, when nothing is specified..

Description/Symptom of problem :  When applicatication server is created using XMLConfig and the input	xml file  does not contain  webcontainer port information,  XMLConfig fails to assign unique port number to the newly created application server, the port assigned is always 9080.

Fix :  The  ApplicationServerConfig code  change to fix the problem.

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>

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:
------------------------------------------------------------------