PQ68634: PROBLEM VIEWING DATA SOURCE PROPERTIES FROM REMOTE ADMIN CONSOLEWEBSPHERE APPLICATION SERVER 4.0.X | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description In WebSphere Application Server 4.0.x, the administrative console may be launched from a remote machine (other than the one on which the admin server is installed). It is not necessary to perform a full WebSphere installation on the remote machine; only the admin console, developer tools, and JDK must be installed from the installation CD. However, if this is done, the properties of data sources are not shown correctly. When creating a new data source from the remote console, no custom properties appear. However, a new custom property can be added. For a data source that already exists, the red asterisk that should appear next to required custom properties does not appear.Local fix To bypass problem, the cm.jar file must be copied from the WebSphere/AppServer/lib directory of the WebSphere server to the WebSphere/AppServer/lib directory of the remote console machine. After doing this, the data source properties will be shown correctly.Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server 4.0 Advanced * * Edition users that have a console-only * * installation. * **************************************************************** * PROBLEM DESCRIPTION: On a console-only installation the * * data source properties are not * * displayed properly. * **************************************************************** * RECOMMENDATION: * **************************************************************** The properties of data sources are not shown correctly. When creating a new data source from the remote console, no custom properties appear. However, a new custom property can be added. For a data source that already exists, the red asterisk that should appear next to required custom properties does not appear.Problem conclusion On a console-only installation the cm.jar file is missing from the <WebSphere root>/lib directory. The console is looking certain files that reside in the cm.jar file, which is not installed on a console-only installation. The PTF installation was modified to install the cm.jar file on a console-only install.Temporary fix 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 #: PQ68634
IBM Group: Software Group
Modified date: Jan 30, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.