PQ76809: WSCP wipes out old values of fields in a datasource that are not passed in the command to modify the datasource password. | |||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Using WSCP to modify DataSource with multiple fields, it is required that all fields are passed in the command even though the user is only interested in changing one. If not, all other fields (except the required fields) are wiped out. The change would be: Default behavior: Using WSCP to modify DataSource properties with multiple fields (eg,custom properties), fields passed in the command will be modified, all other fields (both required and optional) will retain their old values. Optional behavior: Using WSCP to modify DataSource properties with multiple fields (eg, custom properties), fields passed in the command will be modified, all other fields that are not passed in the modify command will have their values wipted out. This is the original behavior and is provided for backward compatiblity. Customer needs to modify wscp property file (e.g. .wscprc) and add the following property: com.ibm.ejs.sm.wscp.notRetainOptionalFields=trueLocal fix There are two workaround: 1. Pass all field values of the object in the wscp command. 2. Update the password using the WebSphere Admin Console.Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server 4.0 users of * * WSCP to modify a DataSource password. * **************************************************************** * PROBLEM DESCRIPTION: When using WSCP to modify a DataSource * * password, the password is modified * * successfully, however, all other * * optional fields are cleared out. * **************************************************************** * RECOMMENDATION: * **************************************************************** When using WSCP to modify a DataSource with multiple fields, it is required that all fields are passed in the command even though the user is only interested in changing one. If not, all of the other fields (except the required fields) are cleared out.Problem conclusion The WSCP datasource modify behaviour was changed to retain the optional field value(s) by default. The details of the behavior changes is outlined below: Default behavior: Using WSCP to modify DataSource properties with multiple fields (for example, custom properties), the fields passed in the command will be modified, all the other fields (both required and optional) will retain their old values. Optional behavior: Using WSCP to modify DataSource properties with multiple fields (for example, custom properties), the fields passed in the command will be modified, all other fields that are not passed in the modify command will have their values cleared out. This is the original behavior and is provided for backward compatiblity. User need to modify the WSCP property file (for example .wscprc) and add the following property, in order to enable this behavior: com.ibm.ejs.sm.wscp.notRetainOptionalFields=trueTemporary fix The test fix is now on PQ99999 site, available for testing.Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
SRLS
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ76809
IBM Group: Software Group
Modified date: Aug 25, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.