Fixes are available
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
wsadmin>$AdminApp help export WASX7151I: Method: export Arguments: application name, filename, options Description: Exports the application specified by "application name" to the file specified by "filename" using the options specified by "options". Method: export Arguments: application name, filename Description: Exports the application specified by "application name" to the file specified by "filename." It's a bit unusual to have enter required filename as empty string. We check for null filename but never check for empty string filename. We can safe guard this to prevent the problem by issue an error message when a filename empty string is used in export app.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V7.0 and V8.0 * **************************************************************** * PROBLEM DESCRIPTION: The wsadmin AdminApp export command * * should throw an exception when the * * "filename" parameter is empty. * **************************************************************** * RECOMMENDATION: * **************************************************************** The behavior is different between UNIX and Windows operating system platforms. On UNIX, the contents of the profile root directory are archived into a file which has as a name the profile with a file extension of "zip". The zip contains the exported application, but the previous contents of the profile directory are lost. For example, A zip file with the name $WAS_HOME/profiles/myProfile/myProfile.zip is created, and the previous contents of $WAS_HOME/profiles/myProfile are lost. On Windows operating systems, the export command fails with the following exception: wsadmin>AdminApp.export('DefaultApplication', '') WASX7015E: Exception running command: "AdminApp.export('DefaultApplication', '')"; exception information: com.ibm.websphere.management.exception.AdminException org.eclipse.jst.j2ee.commonarchivecore.internal.exception.SaveFa ilureException: org.eclipse.jst.j2ee .commonarchivecore.internal.exception.SaveFailureException: IWAE0017E Unable to replace original archive: C:\WAS\nn1119.13\profiles\AppSrv01\bin
Problem conclusion
The wsadmin AdminApp export command will throw an exception when the "filename" parameter is empty. The problem has been corrected. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.21 and 8.0.0.2. 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
PM44243
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-07-22
Closed date
2011-09-29
Last modified date
2011-09-29
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800
Applicable component levels
R700 PSY
UP
R800 PSY
UP
Document Information
Modified date:
27 October 2021