Fix (APAR): PM16072 Status: Fix Release: 6.1 Operating System: AIX, Windows, Linux, Solaris, HP-UX Supersedes Fixes: CMVC Defect: PM16072 Byte size of APAR: 6.1.0.0-WS-WASJavaSDK-AixPPC32-IFPM16072.pak 64,544,227 6.1.0.0-WS-WASJavaSDK-AixPPC64-IFPM16072.pak 64,999,799 6.1.0.0-WS-WASJavaSDK-HpuxIA64-IFPM16072.pak 73,343,658 6.1.0.0-WS-WASJavaSDK-HpuxPaRISC-IFPM16072.pak 55,713,588 6.1.0.0-WS-WASJavaSDK-LinuxPPC32-IFPM16072.pak 70,561,814 6.1.0.0-WS-WASJavaSDK-LinuxPPC64-IFPM16072.pak 68,711,510 6.1.0.0-WS-WASJavaSDK-LinuxS390-IFPM16072.pak 64,100,266 6.1.0.0-WS-WASJavaSDK-LinuxS39064-IFPM16072.pak 64,111,758 6.1.0.0-WS-WASJavaSDK-LinuxX32-IFPM16072.pak 62,453,858 6.1.0.0-WS-WASJavaSDK-LinuxX64-IFPM16072.pak 64,292,927 6.1.0.0-WS-WASJavaSDK-SolarisSparc-IFPM16072.pak 54,123,530 6.1.0.0-WS-WASJavaSDK-SolarisSparc64-IFPM16072.pak 64,513,951 6.1.0.0-WS-WASJavaSDK-SolarisX64-IFPM16072.pak 54,192,130 6.1.0.0-WS-WASJavaSDK-WinX32-IFPM16072.pak 75,186,208 6.1.0.0-WS-WASJavaSDK-WinX64-IFPM16072.pak 70,108,286 Abstract: SHIP SDK BUILD FOR JAVA 5 SR11 FP2 ERROR DESCRIPTION: This WSAS apar will be used to provide a SDK build of Java 5 SR11 FP2 LOCAL FIX: None PROBLEM SUMMARY: USERS AFFECTED: IBM WebSphere Application Server Version 6.1 users PROBLEM DESCRIPTION: SHIP SDK BUILD FOR JAVA 5 SR11 FP2 RECOMMENDATION: Apply this apar to upgrade your SDK to SR11 FP2 PROBLEM CONCLUSION: Applying this fix will upgrade your SDK to SR11 FP2 Directions to apply fix: Use the latest Update Installer to install this Apar: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 Fix applies to Editions: IBM WebSphere Application Server V6.1.0.x _x_ Application Server (Express or BASE) _x_ Network Deployment (ND) _x_ WebSphere Business Integration Server Foundation (WBISF) _x_ Edge Components _x_ Developer _x_ Extended Deployment (XD) Install Fix to: Method: __ Application Server Nodes __ 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. * Use the latest 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 .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 (.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 (.pak file name). 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: