Fix (APAR): PK56653 Status: Fix Release: 6.1.0.13 Operating System: AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux zSeries,OS/400,Solaris,Windows Supersedes Fixes: CMVC Defect: 469399.1 Byte size of APAR: 250112 Date: 2007-11-29 Abstract: Error messages are received when deploying applications, reporting the EAR file contents cannot be found. The sample error messages are: IWAE0006E Archive is not a valid EJB JAR F Description/symptom of problem: PK56653 resolves the following problem: ERROR DESCRIPTION: This D-APAR covers several problems encountered while performing application updates from the Rational Application Developer (RAD) to the IBM WebSphere Application Server in the EJB 3.0 feature pack. A NullPointerException occurs when updating EAR50 (which has no deployment descriptor using RAD 7.5 ), using AppClient14, and using the EJB3.0 IBM WebSphere Application Serve feature pack. For example: WSCL0013I: Initializing the J2EE Application Client Environment. WSCL0100E: Exception received: java.lang.NullPointerException at com.ibm.ws.client.applicationclient. ApplicationClientMetaData.noApplXmlPatch (ApplicationClientMetaData.java:1342) at com.ibm.ws.client.applicationclient. ApplicationClientMetaData. (ApplicationClientMetaData.java:405) at com.ibm.ws.client.applicationclient.ClientContainer. (ClientContainer.java:241) at com.ibm.ws.client.applicationclient.launchClient. createContainerAndLaunchApp(launchClient.java:721) at com.ibm.ws.client.applicationclient.launchClient. main(launchClient.java:478) at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at com.ibm.wsspi.bootstrap.WSLauncher.launchMain (WSLauncher.java:183) LOCAL FIX: PROBLEM SUMMARY USERS AFFECTED: Users who deploy applications via Rational Application Developer to the WebSphere Application Server version 6.1 with the EJB 3.0 Feature Pack PROBLEM DESCRIPTION: Error messages are received when deploying applications, reporting the EAR file contents cannot be found. The sample error messages are: IWAE0006E Archive is not a valid EJB JAR File because the deployment descriptor can not be found (case sensitive): META-INF/ejb-jar.xml RECOMMENDATION: None This cause of the problem is that the applications metadata and binary locations were not being set correctly. PROBLEM CONCLUSION: The code has been updated to address the problem. The fix for this APAR is currently targeted for inclusion in fixpack 6.1.0.15. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 Directions to apply fix: Fix applies to Editions: Release 6.0 _X_ Application Server (Express or BASE) _X_ Network Deployment (ND) Install Fix to: Method: _X_ Application Server Nodes _X_ Deployment Manager Nodes _X_ Both NOTE: The user must: * Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V6.0.2.2 or newer of the Update Installer. This can be checked by reviewing the level of the Update Installer in file /updateinstaller/version.txt. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 For detailed instructions to Extract the Update Installer see the following Technote: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21205400 1) Copy 6.1.0.13-WS-WASEJB3-IFPK56653.pak file directly to the maintenance directory 2) Shutdown WebSphere Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to. 3) Launch Update Installer 4) Enter the installation location of the WebSphere product you want to update. 5) Select the "Install maintenance package" operation. 6) Enter the file name of the maintenance package to install (6.1.0.13-WS-WASEJB3-IFPK56653.pak file which was copied in the maintenance directory). 7) Install the maintenance package. 8) Restart WebSphere Directions to remove fix: NOTE: * The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED * DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED * YOU MAY REAPPLY ANY REMOVED FIX Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied. 1) Shutdown WebSphere Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against. 2) Start Update Installer 3) Enter the installation location of the WebSphere product you want to remove the fix. 4) Select "Uninstall maintenance package" operation. 5) Enter the file name of the maintenance package to uninstall (6.1.0.13-WS-WASEJB3-IFPK56653.pak). 6) UnInstall maintenance package. 7) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere. 2) Follow the Fix instructions to apply the fix. 3) Restart WebSphere Additional Information: