User created WebSphere Application Server variables are not working in the security.xml file
 Technote (troubleshooting)
 
Problem(Abstract)
Users can not create IBM® WebSphere® Application Server Variables and use these in the security.xml file. Why?
 
Cause
The security.xml only accepts the following WebSphere Application Server variables:
${WAS_INSTALL_ROOT}, ${USER_INSTALL_ROOT}, ${WAS_TEMP_DIR},${WAS_PROPS_DIR},${APPINSTALL_ROOT}, and ${WAS_ETC_DIR}
 
Resolving the problem
We do not recommend changing any of the WebSphere Application Server Variables that can be used in security.xml. But if a variable is needed for the configuration inside the security.xml file, we can only change the APPINSTALL_ROOT or WAS_TEMP_DIR variables.

If you change the APPINSTALL_ROOT, all enterprise applications installed need to change the default install path (this uses the APPINSTALL_ROOT variable), otherwise all EAR files will be expanded to this location.

If you change the WAS_TEMP_DIR, all compiled jsp files will be stored in this new directory. This cannot be changed, but WebSphere Application Server will work if we can read/write in the new directory.

 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Security
Operating system(s): AIX
Software version: 6.0
Software edition:
Reference #: 1207251
IBM Group: Software Group
Modified date: May 23, 2005