Fix (APAR): PK54111 Status: Fix Release: 6.1 Operating System: AIX,HP-UX,Linux,Solaris,Windows,z/OS Supersedes Fixes: CMVC Defect: PK54111 Byte size of APAR: 8795 Date: 2007-10-10 Abstract: False operational alerts are being displayed in regards to agents for unmanaged nodes being down. Description/symptom of problem: PK54111 resolves the following problem: ERROR DESCRIPTION: ON AIX V5.3, with ND V6.1.0.11 installed and XD V6.1.0, operation alerts are issued indicating that the defaultcoregroup is in an unstable state. Also nodeagents are reported as not running when in fact the nodeagents are running. APAR PK48624 which supercedes PK47074 has been applied and did not resolve the problem. LOCAL FIX: PROBLEM SUMMARY USERS AFFECTED: All users of WebSphere Application Server also running WebSphere Extended Deployment Operations Optimization Version 6.1 All users of WebSphere Extended Deployment Operations Optimization Version 6.1 using the runtime operations operational alerts. PROBLEM DESCRIPTION: False operational alerts are being displayed in regards to agents for unmanaged nodes being down. RECOMMENDATION: None The false operational alerts are being displayed because the code incorrectly assumes that unmanaged nodes have agents. Since no agent can be found for an unmanaged node the code assumes that the agent is down. PROBLEM CONCLUSION: The code was fixed to no longer assume unmanaged nodes have agents and the fix was made available for the 6.1 release. The fix will be included in Service Pack 6.1.0.1 for WebSphere Extended Deployment Operations Optmization. Directions to apply fix: Install Fix to: __ 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. Also, you should be logged in with the same authority level when unpacking a fix, fix pack or refresh pack. DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX. The Fix Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 The Update Installer for V5.0 does not have a maintenance directory. It uses fixpacks and fixes as the location of the unpacked files. Customers must 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. 1) Copy 6.1.0.0-WS-WXDOP-IFPK54111.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.0-WS-WXDOP-IFPK54111.pak file which was copied in the maintenance directory). The V5.0 and V5.1 fix packs and fixes are unpacked as .jar files and should be unpacked into fixpacks or fixes 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. NOTE: 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.0-WS-WXDOP-IFPK54111.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: