Usage Note 16983: Deploying WebSphere applications using server path will delete file
There is an IBM Websphere 5.1.1.2 issue that will affect any solution
which deploy web applications such as SAS Marketing Automation and the
Portal.
Deploying a new application using the WebSphere Application Server (WAS)
Admin Console may cause the ear/war file to be deleted from that server
location. This only occurs when the "Server path" field is used to
specify the location of the ear/war file to install. If you use local
files for deployment, the file will not be deleted.
To avoid this problem, you can perform one of the following:
(A) When using the admin console to install applications, if possible,
use the "Local path" instead of the "Server path". In order to use
"Local path", the ear/war file must reside on the machine that has the
browser running the admin console.
(B) Backup all your ear/war files to another directory other than the
one you specify in the "Server path" location. When the file is deleted
via the deployment, you will have a backup copy to restore.
(C) If you already installed using the "Server path", then the ear/war
files were removed by WAS. WAS also saves the ear/war files that it
installed in the WAS directory structure. WAS may have renamed and/or
repackaged the application but you can still get the original war file.
For example, if you install SASPreferences.war, you can get to the war
file via the following WAS directory:
WAS_HOME\config\cells\machinename\applications\SASPreferences.war.ear
In this directory, there is a file called SASPreferences.war.ear. WAS
makes everything an ear file but you will find your SASPreferences.war
file within this ear file.
This problem is described at the IBM support site at:
http://www-1.ibm.com/support/docview.wss? rs=180&uid=swg1PQ95017 and we
have seen the problem with WAS Base anytime "Server path" is used to
specify the location of the ear/war file to install.
Operating System and Release Information
| SAS System | SAS Marketing Automation-Server | Microsoft Windows Server 2003 Standard Edition | 4.3 | | | |
| Microsoft Windows XP Professional | 4.3 | | | |
| Microsoft Windows Server 2003 Enterprise Edition | 4.3 | | | |
| Microsoft Windows Server 2003 Datacenter Edition | 4.3 | | | |
| Microsoft Windows 2000 Server | 4.3 | | | |
| Microsoft Windows 2000 Datacenter Server | 4.3 | | | |
| Microsoft Windows 2000 Professional | 4.3 | | | |
| AIX | 4.3 | | | |
| 64-bit Enabled AIX | 4.3 | | | |
| HP-UX IPF | 4.3 | | | |
| 64-bit Enabled Solaris | 4.3 | | | |
| Microsoft Windows 2000 Advanced Server | 4.3 | | | |
| Solaris | 4.3 | | | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
| Type: | Usage Note |
| Priority: | alert |
| Topic: | System Administration ==> Installation
|
| Date Modified: | 2006-01-31 14:23:50 |
| Date Created: | 2006-01-31 14:23:50 |