PQ77215: WSINSTANCE WRITES TO ORIGINAL WAS INSTALL CAUSING PERMISSION PROBLEMS | |||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||
APAR status Closed as program error. Error description When wsinstance is run, it allows the user to specify the target directory for creation of the WAS instance. The user (in our ca developer) needs to have write access to the target directory an is not a problem. The problem occurs because when wsinstance is it also writes to two directories containing the real WAS instal Let's say the real WAS install is in /opt/WebSphere/Appserver. When wsinstance is run it write to the /opt/WebSphere/AppServer/bin/wsinstance directory and to the file /opt/WebSphere/AppServer/properties/wsinstance.config.Local fix Give all users of wsinstance's full permissions to the original WAS install directory.Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server 5.0 users of * * wsinstance . * **************************************************************** * PROBLEM DESCRIPTION: When using wsinstance, it will write to * * the original WebSphere installation * * directory, which will cause permission * * problems. * **************************************************************** * RECOMMENDATION: * **************************************************************** When wsinstance is run, it allows the user to specify the target directory for creation of the WebSphere instance. This is not a problem if the user has write access to the target directory. The problem occurs when wsinstance writes to two directories containing the original WebSphere installation. For example, if the orinal WebSphere installation is in: /opt/WebSphere/Appserver. When wsinstance is run it writes to the /opt/WebSphere/AppServer/bin/wsinstance directory and to the file /opt/WebSphere/AppServer/properties/wsinstance.config.Problem conclusion The code was modified so the wsinstance creation tool will not attempt to write to a non-writable WebSphere installation location, thus allowing non-root users to create wsinstances. A " -readOnly " command line parameter was added to force this functionality. If write access to the WebSphere installation is not possible during the wsinstance creation, the registration of the new instance is not possible, and fix pack updates will not be applied to the unregistered instances.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
Publications Referenced
|
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 00S
Software edition:
Reference #: PQ77215
IBM Group: Software Group
Modified date: Sep 16, 2003
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.