PQ55386: UNABLE TO UPDATE CONTEXT ROOT, EVEN AFTER MAKING CHANGES TO THE APPLICATION.XML FILE.

APAR status
Closed as program error.

Error description
Context root is not editable in v4.01 from within the Console.
Therefore, you need to make changes within the application.xml
file.  According to the Infocenter, you should be able to regen
the plugin after making the change and it should update (hot
deployment).  However, it does not change and this is even after
stopping and restarting both the admin and application server.
The only way for the change to be accepted is to reinstall the
.ear file.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server for         *
*                 Multiplatforms users.                        *
****************************************************************
* PROBLEM DESCRIPTION: Users should be able to change the      *
*                      context root of a web module without    *
*                      having to delete and redeploy the       *
*                      web module.                             *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Currently there is no way to change the context root of a web
module.  The context root is persisted to the admin repository
at deploy time.  There is no way to change data once it has
been written to the database.

The only way to change the context root is by using the
following steps:
1.  Stop the web module's containing enterprise application.
2.  Remove the enterprise application.
3.  Modify the context root of the web module in the
Application Assembly Tool.
4.  Redeploy the resulting EAR file.
5.  Regenerate the webserver plugin file.
6.  Start the enterprise application

With this code change, the new process used to change the
context root of a web module is:
1.  Modify the context root of the web module in the
application.xml file.
2.  Regenerate the webserver plugin file.
3.  Stop and Start the enterprise application.
Problem conclusion
Modified the way the plugin-cfg.xml version of the context root
is compared to the persisted context root.  If the two are
different, the plugin generator will use the context root in
application.xml and it will also persist this new context root
to the database.
Temporary fix Comments
APAR information
APAR number PQ55386
Reported component name WEBSPHERE AES N
Reported component ID 5630A2301
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2001-12-03
Closed date 2002-01-31
Last modified date 2002-01-31

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
ENGINE          

Fix information
Fixed component name WEBSPHERE AES N
Fixed component ID 5630A2301

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ55386
IBM Group: Software Group
Modified date: Jan 31, 2002