PQ66193: MODIFICATION OF DEFAULT DATA SOURCE BY WSCP IS NOT REFLECTED IN REPOSITORY OR ADMIN CONSOLE.

 Fixes are available

4.0.5: WebSphere Application Server Version 4.0 Fix Pack 5 (Version 4.0.5)
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
Module modify command to modify the JndiName for the
DefaultResourceRef results in a change that is reflected in the
results of a subsequent Module show command in wscp. However,
the export of the config values to an XML file does not show the
change and the admin console does not show the change.
Local fix
There is no local fix. Customer has been given a test fix that
worked. Need formal fix for the customer.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of wscp.  *
****************************************************************
* PROBLEM DESCRIPTION: In wscp, using the "Module modify"      *
*                      command to modify the JNDIName for      *
*                      the DefaultResourceRef results in a     *
*                      change that is reflected in the         *
*                      results of a subsequent "Module show"   *
*                      commands in wscp.  However, this        *
*                      change is not reflected in the          *
*                      information displayed by the admin      *
*                      console or the output of XMLConfig.     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Internally, wscp was not fully updating the repository
when the JNDI name of the Default DataSource was changed.
XMLConfig and admin console were doing this correctly.  One
of the curious properties of this problem was that if JNDI
name was changed by XMLConfig or admin console, then the name
was seen correctly by wscp but if wscp changed the name, then
only wscp would see changed name.  This was due to incomplete
repository update being done by wscp in this case.
Problem conclusion
Implemented wscp handling of JNDI name change to more closely
model that of admin console and XMLConfig.
Temporary fix
given the fix to test.
Comments
APAR information
APAR number PQ66193
Reported component name WEBSPHERE AE SO
Reported component ID 5630A2202
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-09-13
Closed date 2002-10-18
Last modified date 2002-10-18

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 SO
Fixed component ID 5630A2202

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 #: PQ66193
IBM Group: Software Group
Modified date: Oct 18, 2002