PQ55183: XMLCONFIG THAT UPDATES VIRTUAL HOST BINDINGS IN ENTERPRISE APP WEB MODULES ARE NOT GENERATED TO PLUGIN CORRECTLY | |||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||
APAR status Closed as unreproducible. Error description When using XMLConfig to create an enterprise application whose web modules bind to virtual hosts other than default_host, the resulting plugin configuration file generated following the create shows default_host for the virtual host bindings on all web modules. The problem may be recreated by doing the following: . 1. Install WAS 4.0.1 with the default sample configuration. 2. Export the sample Enterprise Application to an XML file, and modify it so that it will create the EA if that XML is imported. 3. Remove the sample EA from the configuration using the administrative console. 4. Using the admin console, reate two new virtual hosts. These are in addition to default_host. 5. Modify the XML web module bindings for default_app and examples to use the two new virtual hosts created in step 4. That is, the first new vhost for default_app and the second new vhost for examples. 6. Use xmlconfig to import the modified XML file that creates an EA. 7. Verify that the application was created and that virtual host names for the web modules have been set as defined in the XML file. 8. Using the admin console, generate the web server plugin on the node. 9. Check the generated plugin configuration file to see that it still shows vhost default_host for both default_app and examples web modules.Local fix WSCP may provide a programmatic workaround.Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server 4.01 users of * * XMLConfig. * **************************************************************** * PROBLEM DESCRIPTION: XMLConfig generates incorrect * * plugin.cfg file while installing an * * ear file. * **************************************************************** * RECOMMENDATION: * **************************************************************** This is already fixed in 4.0.2 and is working in the latest WAS 402 build. It is not possible to build an efix of this at 4.0.1 level, since changes are done to few beans / interfaces and these dependent files are also used by other components and hence affects their functionality. Hence it is not possible to build an efix for this at 4.0.1 level.Problem conclusion Temporary fix Comments This is already fixed in 4.0.2 and is working in the latest WAS 402 build. It is not possible to build an efix of this at 4.0.1 level, since changes are done to few beans / interfaces and these dependent files are also used by other components and hence affects their functionality. Hence it is not possible to build an efix for this at 4.0.1 level.
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ55183
IBM Group: Software Group
Modified date: Nov 30, 2001
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.