PQ67047: ATTEMPT TO MODIFY VIRTUAL HOST WITH WSCP PRODUCES INCOMPLETE RESULTS.

 Fixes are available

4.0.6: WebSphere Application Server Version 4.0 Fix Pack 6
System Management Component Cumulative Fix for 4.0.2/4.0.3/4.0.4 /4.0.5



APAR status
Closed as program error.

Error description
Virtual host created with wscp
1) Does NOT appear in admin console or in XMLConfig export.
2) Does appear in config plugin file regenerated.
3) Produces error when app server is started
4) Is detected by admin console as existing when attempt is made
to add
same virtual host from admin console after first adding it in
wscp
.
I was able to reproduce the problem in WAS v4.0.2.
I had the default_server as part of a server group.
I had all of the symptoms the customer described except that I
could
start the default_server without error.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server 4.0.5 and       *
*                 earlier users of WSCP to modify Virtual      *
*                 Host binding on Module.  Problem reported    *
*                 on 4.0.4.                                    *
****************************************************************
* PROBLEM DESCRIPTION: When modifying Virtual Host             *
*                      attribute information on Module with    *
*                      WSCP,  the changes are not reflected    *
*                      on console nor xmlconfig.               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The following WSCP command example was used to modify
Virtual Host attribute on Module:
wscp> Module  modify
{/EnterpriseApp:sampleApp/Module:sample_web_module} -attribute
{{ModuleBindingsConfig
{WebAppBindings {{VirtualHostName new_vh}}}}}

The command runs without any error and the subsequent
GenPluginCfg.sh recreated the plugin-cfg file with the correct
vhost references. A Module show also reflected the change in
its output.  However, the admin console and XMLConfig output
still showed the old virtual host.
Problem conclusion
This APAR fixed the problem that use WSCP to modify Virtual
Host information on a Module does not get updated on the
ModuleBinding in the repository.
Temporary fix
customer is testing the supplied test eFix, waiting for status
Comments
APAR information
APAR number PQ67047
Reported component name WEBSPHERE AE AI
Reported component ID 5630A2200
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-10-09
Closed date 2002-11-05
Last modified date 2002-11-05

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
WSCP          

SRLS

Fix information
Fixed component name WEBSPHERE AE AI
Fixed component ID 5630A2200

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 #: PQ67047
IBM Group: Software Group
Modified date: Nov 5, 2002