Fix (APAR): JR32830 Status: Fix Release: 6.2.0.1 Operating System: AIX,HP-UX,i5/OS,Linux,Solaris,Windows,z/OS Supersedes Fixes: CMVC Defect: 586017 Byte size of APAR: 46596 Date: 2009-06-09 Abstract: The Health monitor REST services contains the following defects: - Return incorrect status for the node agent when the node agent is stopped. - Does not return the list of data sou Description/symptom of problem: JR32830 resolves the following problem: ERROR DESCRIPTION: This APAR fixes the following issues with REST APIs: - The Health monitor REST API won't return correct info about the node agent status when the node agent is stopped. - Data sources in the support cluster of a Network Deployment environment are not being displayed in the module health widget. - System component is displayed as stopped status when 1 cluster node of a multiple nodes cluster is stopped. The correct status for the system component should be started. - Eliminate duplicate update requests in the module health REST API to improvement performance. LOCAL FIX: None PROBLEM SUMMARY USERS AFFECTED: Websphere Process Server v6.2.0.1 users. PROBLEM DESCRIPTION: The Health monitor REST services contains the following defects: - Return incorrect status for the node agent when the node agent is stopped. - Does not return the list of data sources in the support cluster of a Network Deployment environment. - Return incorrect status for the system components when only one cluster node of a multiple nodes cluster is stopped. RECOMMENDATION: None The Health monitor REST services contains the following defects: - Return incorrect status for the node agent when the node agent is stopped. - Does not return the list of data sources in the support cluster of a Network Deployment environment. - Return incorrect status for the system components when only one cluster node of a multiple nodes cluster is stopped. PROBLEM CONCLUSION: Applying this interim fix will resolve the issues reported in this APAR. Directions to apply fix: Download and follow Update Installer installation instructions. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 1) Copy the pak file to the directory maintenance in the UpdateInstaller directory 2) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 3) Run the UpdateInstaller and follow the prompts. 4) Restart WebSphere Process Server. Directions to remove fix: NOTE: FIXES MUST BE REMOVED IN THE REVERSE ORDER IN WHICH 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, then fix2 may be removed 1) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix. 3) Restart WebSphere Process Server. Directions to re-apply fix: 1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Run the UpdateInstaller and follow the instructions. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 3) Restart WebSphere Process Server. Additional Information: