PQ60657: EAR FILE NOT EXPANDED AFTER INSTALL WITH REMOTE ADMIN CONSOLE | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description When using a remote admin console to install an Ear file that is local to the adminserver the adminclient is connecting to, the final screen informs the user that the file is local to the install node and will be expanded in the installedApps direc tory. This however does not occur. The application is visible in the console, but will not run properly because the code has not been expanded into the installedApps directory. The error "CNTR0020E" appears when trying to start or access info on the i nstalled application. Customer receives feedback that the instal l was successful, without being told that the EARexpander has to be ran against the EAR file before the application is fully installed. This is a false positive.Local fix Manually expand the ear file in the installedApps directory.Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server users running * * 4.0.2 or later with a multi-node environment * * (where multiple nodes share the same remote * * repository) wishing to install enterprise * * Applications via a remotely connected * * console * **************************************************************** * PROBLEM DESCRIPTION: In a multi-node environment, when * * using a remote admin console to install * * an Ear file that is local to the * * adminserver the adminclient is * * connecting to, the final screen informs * * the user that the file is local to the * * install node and will be expanded in * * the installedApps directory. This * * however does not occur, EAR does * * not expand and no directory is created. * **************************************************************** * RECOMMENDATION: * **************************************************************** In multi-node environment, EAR fails to expand when installed through a remote admin console. The installation appears to succeed, the application is visible in the console, but will not run properly because the code has not been expanded into the installedApps directory. The error "CNTR0020E" appears when trying to start or access info on the installed application. User receives feedback that the install was successful, without being told that the EARexpander has to be run against the EAR file before the application is fully installed. This is a false positive.Problem conclusion The current requirements for expanding an EAR file on a particular system are: 1. EAR file to install exists on intended node 2. Admin server servicing the request to expand the EAR file is running on same node 3. Node on which EAR file is expanded is same as for #1 and #2 above. With this fix, expanding the EAR file will be determined only by: - node on which EAR file resides and node on which EAR file is to be expanded are the same, node on which admin server is running will not be a factor! As a result, the user can have a local console connect to a local adminserver and install EAR on remote nodes in the multi-node cluster without needing to manually expand the EAR. The console has been modified to correctly display the proper message. If EAR file resides on a node other than the one intended to install on, user will need to manually expand the EAR on the intended node. This is the expected behavior of WebSphere. A console provides message to inform user.Temporary fix posted test eFix PQ60657 on wasdoc0, await customer feedbackComments
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 #: PQ60657
IBM Group: Software Group
Modified date: Jul 16, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.