APAR Number:		PQ68756

Status:			eFix

Release:		4.0.5,4.0.4

Operating System:		NA

Supersedes eFixes:		

CMVC Defect:		PQ68756

Byte size of APAR:		863582

Date:		Mon Dec 16 13:09:37 EST 2002

Abstract:		WEBSPHERE AES DOES NOT ALLOW A USER TO DEFINE THE FILENAME OR   LOCATION FOR THE PLUGIN-CFG.XML WHEN GENERATED FROM THE CONSOLE.

Description/symptom of problem:		Customer is using several server-cfg.xml files for development and each developer is deploying applications.  When they use the regenerate plugin option from the console, it always writes to the default plugin-cfg.xml file.  The customer has used the command line option GenPluginCfg.bat -outputFile, but does not see this as a solution, since they are encouraging their developers to use the admin console.
Local Fix: 
Using the command line option:
GenPluginCfg -configFile server-cfg.xml -outputFile c:\temp
.
This will write the plugin-cfg.xml file to the c:\temp directory


Directions to apply efix:		
1) Create temporary 'efix' directory to store the jar file:
 				AIX: /tmp/WebSphere/efix
   Solaris/Linux: /tmp/WebSphere/efix
 		  Windows: c:	empWebSphereefix

2) Copy jar file to the directory

3) Shutdown WebSphere

4) Run the jar file with the following command answering questions/prompts as they appear:
   java -jar <jarfile name>

5) Restart WebSphere

6) The temp directory may be removed but the jar file should be saved.  Do not remove
	any files created and stored in the <WASHOME>/WebSphere/AppServer/efix/<efix> directories.
   These files are required if an efix is to be removed.


Directions to remove 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/<efix#>).

2) Shutdown WebSphere

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

4) Restart WebSphere


Directions to re-apply 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.

Additional Information:		To use this fix, add the pathMap entry 'PLUGIN_CFG_ROOT' inside of the server-cfg.xml file.
*** snippet of server-cfg.xml *******
    <pathMap xmi:id='PathMap_1'>
      <entries xmi:id='PathMapEntry_1' symbolicName='APP_INSTALL_ROOT' path='${WAS_ROOT}/installedApps' description='The filesystem path to the directory which will contain installed enterprise applications.'/>
      <entries xmi:id='PathMapEntry_2' symbolicName='LOG_ROOT' path='${WAS_ROOT}/logs' description='The filesystem path to the directory which will contain server log files.'/>
      <entries xmi:id='PathMapEntry_3' symbolicName='TRANLOG_ROOT' path='${WAS_ROOT}/tranlog' description='The filesystem path to the directory which will transaction log files.'/>
      <entries xmi:id='PathMapEntry_4' symbolicName='PRODUCT_INSTALL_ROOT' path='${WAS_ROOT}' description='The filesystem path to the product installation directory'/>
      <entries xmi:id='PathMapEntry_5' symbolicName='WAS_ROOT' path='C:\WebSphere\AppServer40_aes' description='The filesystem path to the product installation directory'/>
      <entries xmi:id='PathMapEntry_6' symbolicName='JAVA_HOME' path='C:\WebSphere\AppServer40_aes\java' description='The filesystem path to the product java home directory'/>
      <entries xmi:id='PathMapEntry_7' symbolicName='PLUGIN_CFG_ROOT' path='C:\temp' description='The filesystem path to write the plugin-cfg.xml'/>
    </pathMap>