PQ54484: CANNOT INSTALL ENTERPRISE APPLICATION FROM ANY ADMINSERVER | |||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||
APAR status Closed as suggestion for future release. Error description Node 1 - admin client is connected to the admin server here Node 2 - an ear resides here, installing application here. * node 1 and node 2 are part the same WAS configuration (share repository) . Unless node1 and node2 are physically the same machine, this will not work. . The install of the ear file will go through without error and the application shows in the topology, but there is no expanded ear directory under installedApps on the node in which both the file was on and was installed on. . Spoke with Jason McGee, Michael Morton, Michael Frankel. (with or thru Ken Ueno) All believe this is designed to work and is a bug since it does not. . Spoke with Ajay Apte in Austin. He believes this is functioning as designed. That if the machine the admin client is connected to, the machine the ear file resides on, and the machine to which the application will be installed are not the same actual machine, it will not work. This contradicts the architects expected behavior. . SVT team is working on a correcting this in the next release. This APAR is for the current 4.01 release.Local fix Workaround: The workaround is to simply connect the adminclient to the admin server on the machine in which the application is going to be installed and use the file on that physically resides on that machine (or move it to that machine prior to install)Problem summary Problem conclusion Temporary fix Comments An agreement was reached to change code in a future release to allow the admin client to browse on any node for an ear file and not just the one that the admin client is connected to. That ear file can be configured on any node(s) in the network (configured = everything except delivered and expanded). However, the ear file will only be expanded if the source ear file is on the node to which the admin client is connected. The messages on the final panel of the app install wizard should describe the necessary steps to complete the installation. . It is expected that a complete distributed application management feature, including app file transfer and remote installation, will be completed in a future release.
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 #: PQ54484
IBM Group: Software Group
Modified date: Nov 16, 2001
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.