PQ55839: EFIXINSTALLER FAILS WHEN WEBSPHERE BASE NOT INSTALLED | |||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||
APAR status Closed as program error. Error description Example of an error message in extractor.log: 001/11/20 19:05:39 Error 128 -- Unable to determine container ty pe... errors were noted, functionality may be compromised. 2001/11/20 19:05:39 2001/11/20 19:05:39 Please view the activity log for details. 2001/11/20 19:09:21 Error 128 -- Unable to determine container t ype...Local fix Remove the packaged libarary file from jar and manually copy to local filesystem.Problem summary **************************************************************** * USERS AFFECTED: WebSphere 4.01 Application Server, Single * * and Advanced server users who are trying to * * apply an eFix on a machine that does not * * have the full WebSphere App Server installed * * on it. (ie: A machine that has a remote web * * server). * **************************************************************** * PROBLEM DESCRIPTION: If using a web server on a separate * * machine than WebSphere and the user * * tries to install an eFix, it will fail * * because it can not find the product.xml * * that comes with the full install of * * WebSphere. * **************************************************************** * RECOMMENDATION: * **************************************************************** When trying to install an eFix on a machine that does not have WebSphere installed on it will fail because the eFix Installer can not find the product.xml that normally comes with WebSphere. For example, A user has two machines...one contains WebSphere and the other contains the web server. When configuring the web server to use WebSphere plugin, you run the install on the web server machine and only install the plugin. This will create a WebSphere directory that will only contain the plugin file, plugin-cfg.xml, and some other files. However, it does not put a product.xml file in the directory. Therefore, when eFix installer is run to install a fix on the plugin file, it will fail because it can not find the product.xml file.Problem conclusion This problem was fixed by the eFix installer carrying a product.xml file with it when it installs the eFix. If it can not find product.xml then it will drop one down so it can install the eFix and update the product.xml file.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
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ55839
IBM Group: Software Group
Modified date: Dec 14, 2001
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.