PK07859: ORIGINAL EAR FILE GETS DELETED DURING DEPLOY FROM ADMINISTRATIVECONSOLE

 Fixes are available

5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for AIX
5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for HP-UX
5.1.1.19: WebSphere Application Server V5.1.1 Cumulative Fix 19 for Linux
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for AIX
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for AIX
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for HP-UX
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for Solaris
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for Windows
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for Linux
5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for Linux
5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for Solaris
5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for Windows
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Solaris
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Windows
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for Solaris
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Windows
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for AIX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for AIX
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for Linux
5.1.1.19: WebSphere Application Server V5.1.1 Cumulative Fix 19 for AIX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Windows
5.1.1.19: WebSphere Application Server V5.1.1 Cumulative Fix 19 for Windows
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for HP-UX
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for Solaris
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Solaris
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for Windows
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for Solaris
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for AIX
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for AIX
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for Linux
5.1.1.7: WebSphere Application Server Version 5.1.1 Cumulative Fix 7
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for HP-UX
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for AIX
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for Windows
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for HP-UX
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for AIX
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for AIX
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Linux
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for HP-UX
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Linux
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for HP-UX
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for Linux
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for HP-UX
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for Windows
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Solaris
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Windows
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for AIX
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for Windows
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for Solaris
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for Solaris
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for Linux
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for Windows
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for HP-UX
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for AIX
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for Windows
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for Solaris
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for Windows
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for AIX
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for Linux
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for HP-UX
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for Solaris
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for Solaris
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for AIX
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for Windows
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for HP-UX
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for Solaris
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for Solaris
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for Linux
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for AIX
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for Linux
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for Windows
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for Windows
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for Linux
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for HP-UX
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for HP-UX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Linux
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for HP-UX
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Linux
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Solaris
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for AIX
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for HP-UX
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for HP-UX
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for Linux
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for Linux
5.1.1.19: WebSphere Application Server V5.1.1 Cumulative Fix 19 for HP-UX



APAR status
Closed as program error.

Error description
Following a specific procedure the original EAR being deployed
will be deleted. This only happens when using these specific
steps:
  1. Log on to the Administrative Console
  2. Click Applications
  3. Click Install New Application
  4. Select "server path" option and click browse
  5. Select the node name
  6. Navigate the path to the ear file and press ok.
  7. The path that is shown gets changed to a location that is
     unexpected. This is because the "server path" option
     assumes the node exists on another system. The
     Administrative Console processing copies the file to the
     local deployment manager and alters the path displayed to
     be a temporary location.
  8. Instead of clicking Next as expected click Browse again.
  9. Select the deployment manager
 10. Navigate the path again to the ear file and press OK.
 11. Click next all the way to the end of the application
     deployment.
 12. The EAR file is removed from the original location.
The reason for this is that when you choose "server Path" and
the node name and browse to the EAR file and click OK, the EAR
will be copied to  <WAS_INSTALL>\DeploymentManager\config\temp
and a flag will be set to delete that temp ear in config\temp.
When Next is selected the EAR is copied to the workspace and the
EAR in config\temp is deleted and the delete flag is removed.
But, instead of clicking Next in this scenario we clicked
Browse again and selected the Deployment Manager. The delete
flag is not normally set in this case but is it already set
from the step above and the path is pointing to the original
EAR file not the one in config\temp. So at the end of deployment
the original EAR file is deleted.
The plan for the fix is to not delete any EAR files when the
Deployment Manager is selected.
Local fix
The best way to work around this problem is to either
 1. Select "Local Path" is the EAR file in one the local
    system, or
 2. Select "Server Path" and the Node and continue the
    deployment process by clicking next, or
 3. Select "Server Path" and the Deployment Manager and continue
    the deployment process by clicking next.

SEARCH KEYWORDS: Deploy deployment nodeagent install enterprise
application WAR JAR webpshere WAS WSAS adminconsole
administrative console consoles erase delete remove destroy
source
Problem summary
****************************************************************
* USERS AFFECTED: Webphere Application server users who        *
*                 use the administrative console to install    *
*                 applications and use the Server path         *
*                 to browse to "Node name" first and select    *
*                 one EAR. Then instead of continuing with     *
*                 the installation press Next in "Preparing    *
*                 for the application installation" page.      *
****************************************************************
* PROBLEM DESCRIPTION: When installing a application from the  *
*                      administrative console and using        *
*                      ServerPath if you browse to "Node name" *
*                      first and select one EAR, then          *
*                      instead of continuing with the          *
*                      installation by pressing Next in        *
*                      "Preparing for the application          *
*                      installation" page if you browse again  *
*                      to "deployment manager" and select      *
*                      some other EAR then press Next in       *
*                      "Preparing for the application          *
*                      installation" page then that source     *
*                      EAR is deleted.                         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
1)You browse to "server path" -> "any node name and not Dmgr"
  and selects the EAR and says ok.
2) instead of pressing "next" if you browse again to "Deployment
   manager" node and select some other EAR.
3) press Next in the "Preparing for the application
   installation" page then that source EAR is deleted.

When you browse to "server path" -> "any node name and not Dmgr"
and select the EAR and say ok. Then the EAR will be copied to
<WAS_INSTALL>\DeploymentManager\config\temp and also a flag
will be set to delete that temp ear in config\temp in
UploadController.java.

Once you press the "Next" button soon after that, we have code
to copy the EAR to the workspace and delete the EAR in
config\temp in UplaodAction.java. And the delete flag is unset
here.
After clicking "next" we have the EAR copied to the workspace
and we delete the EAR and unset the flag.

The installation proceeds after that using the workspace.

But what happens in step 2 is:
instead of pressing "next" we are browsing again to "Deployment
manager" node and selecting some other EAR. In this case we are
not setting any delete flag as the EAR is not copied to
config\temp. But the delete flag is already set from the
previous Browse and we have not unset it as we have not
clicked "next." So we have the delete flag set even for the
second browse and this path will be pointing to the original
EAR. And so it deletes the original EAR.
Problem conclusion
Cod changes have been made to handle the issue. But there is
one limitation on this fix. The limitation is that with this
code change we will not be able to delete the Temp EAR from
the config/temp directory. But only in the above senario. In
all other cases the temp EAR will be deleted.

So with above code change we can avoid deleting the source EAR
with this Scenario but we can not avoid leaving the temp EAR in
Config/temp in this case .

The fix for this APAR is currently targeted for inclusion in
fixpack 5.0.2.14 and 5.1.1.7.
Please refer to the Recommended Updates page for delivery
information:

http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix Comments
APAR information
APAR number PK07859
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 10A
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2005-06-23
Closed date 2005-08-22
Last modified date 2005-11-07

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
WEBUI          

Publications Referenced

Fix information
Fixed component name WAS BASE 5.0
Fixed component ID 5630A3600

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00P PSY    UP
R00S PSY    UP
R00W PSY    UP
R103 PSY    UP
R10A PSY    UP
R10H PSY    UP
R10I PSY    UP
R10P PSY    UP
R10S PSY    UP
R10W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 10A
Software edition:
Reference #: PK07859
IBM Group: Software Group
Modified date: Nov 7, 2005