PQ77233: Changes in virtual-host mimetable properties using wscp does not get reflected in xmlconfig full export.

 A fix is available

4.0.7: WebSphere Application Server Version 4.0 Fix Pack 7



APAR status
Closed as program error.

Error description
Problem:When trying to change the mime table property of virtual
host using wscp ,it appears like command is successful and also
it did not throw any exceptions . Show command at wscp command
prompt shows modified values ,but full xml export from the
console has no values for all the properties of virtual-host,
it shows bank under virtualhost tag.

wscp> VirtualHost show /VirtualHost:default_host/ -attribute
{MimeTable}
{MimeTable {{application/vnd.lotus-wordpro {[lwp,
sam]}}{application/x-troff-me [me]}{text/tab-separated-values
[tsv]}{image/x-portable-anymap
[pnm]}{application/vnd.lotus-screencam [
scm]}{text/x-ssi-html {[htmls, shtml]}}{application/xml
. . . .
. . . .
wscp> VirtualHost modify /VirtualHost:default_host/ -attribute
{{MimeTable {{application/vnd.lotus-wordpro
{[lwp,sam]}}{image/newType
{[new1,new2]}}}}}

wscp> VirtualHost show /VirtualHost:default_host/ -attribute
{MimeTable}
{MimeTable {{application/vnd.lotus-wordpro
[lwp,sam]}{image/newType
[new1,new2]}}}

But there is no values exists under vaitual-host tag in full xml
export .
Local fix
No WorkAround available.

Suggestion:When dealing with much nested information, as with
the MimeTable, the adminconsole is really a better tool for this
all around, and is very seldom used for this by customers.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server 4.0 users of    *
*                 the WSCP MimeTable attributes of the         *
*                 VirtualHosts.                                *
****************************************************************
* PROBLEM DESCRIPTION: In WSCP, the MimeTable is not being     *
*                      modified properly.                      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When a modification is done to the MimeTable, it is being stored
as a String as opposed to a Vector. The Admin Console is storing
and reading these attributes as Vectors. Therfore, when WSCP
modifies the MimeTable, the MimeTable will subsequently show
up as blank in the Admin Console.
Problem conclusion
The DefaultScriptCmdHandler class was modified to store the WSCP
MimeTable information as a Vector.  A new method
( parseSubAttributes ) was added to this class, which parses the
WSCP date into a Vector before pushing it to the repository.
This is consistant with the way that the Admin Console handles
the MimeTable information.
Temporary fix
Fix is available on 
PQ99999.  When a modify is done on the
mimetable, it is being stored as a string as opposed to a
vector. The admin console is storing and reading these
attributes as vectors. Therfore when wscp modifies the mime
table, the mimetable will subsequently show up as blank in the
admin console.  This fix solves that problem by also storing
the wscp mimeTable information as a vector.
Comments
APAR information
APAR number PQ77233
Reported component name WEBSPHERE AE AI
Reported component ID 5630A2200
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2003-08-06
Closed date 2003-08-28
Last modified date 2003-08-28

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

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 #: PQ77233
IBM Group: Software Group
Modified date: Aug 28, 2003