Fix (APAR): PI55775 Status: Fix Release: 8.5 Operating System: AIX, Linux, Solaris, Windows, z/OS Abstract: Ship Java 7.1 SR 3 FP30 for WSAS V8.5.5.2 and higher ERROR DESCRIPTION: Ship Java 7.1 SR 3 FP30 for WSAS V8.5.5.2 and higher LOCAL FIX: None PROBLEM SUMMARY: Ship Java 7.1 SR 3 FP30 for WSAS V8.5.5.2 and higher USERS AFFECTED: IBM WebSphere Application Server Version 8.5 users PROBLEM DESCRIPTION: Ship Java 7.1 SR 3 FP30 for WSAS V8.5.5.2 and higher RECOMMENDATION: Apply this fix to upgrade your SDK to this version. PROBLEM CONCLUSION: Applying this fix will upgrade your SDK. Directions to apply fix: Fix applies to Editions: IBM WebSphere Application Server V8.5.0.x _x_ Application Server (Express or BASE) _x_ Network Deployment (ND) ___ WebSphere Business Integration Server Foundation (WBISF) ___ Edge Components ___ Developer ___ Extended Deployment (XD) Install Fix to all WebSphere installations unless special instructions are included below. Special Instructions: None NOTE: The user must: * Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V1.4.3 or newer of the Installation Manager. Certain iFixes may require a newer version of the Installation Manager and the Installation Manager will inform you during the installation process if a newer version is required. The IBM Information Center can provide details, if needed, on the use of the Installation Manager to apply the iFixes. http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp. Shutdown WebSphere Application Server before applying the iFixes. Restart WebSphere Application Server after applying the iFixes. Directions to remove fix: The IBM Information Center can provide details, if needed, on the use of the Installation Manager to remove the iFixes. http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp. Shutdown WebSphere Application Server before removing the iFixes. Restart WebSphere Application Server after removing the iFixes. Directions to re-apply fix: 1) Shutdown WebSphere Application Server. 2) Follow the Fix instructions to apply the fix. 3) Restart WebSphere Application Server.