Fix (APAR): PM55654 Status: Fix Release: 7.0.0.2,7.0.0.1,7.0 Operating System: AIX,HP-UX,IBM i,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: PM55654 Byte size of APAR: 206513 Date: 2012-05-01 Abstract: After visiting the Dynamic Clusters page, the WebSphere Variables page always displayed only one variable Description/symptom of problem: PM55654 resolves the following problem: ERROR DESCRIPTION:? When moving from any of the dynamic cluster admin console pages (dynamic cluster > dynamic_cluster_name pages) to the WebSphere variables page, the only varibles displayed are the Node=null,Server=dynamic_cluster_name variables. LOCAL FIX:? Leave the WebSphere variables page for a page other than the dynamic cluster pages and return. The correct WebSphere variables page will be displayed. PROBLEM SUMMARY:? USERS AFFECTED: All users of WebSphere Virtual Enterprise V7.0, 7.0.0.1, and 7.0.0.2 PROBLEM DESCRIPTION: After visiting the Dynamic Clusters page, the WebSphere Variables page always displayed only one variable RECOMMENDATION: None In DisplayDynamicClusterDetailAction class, VariableSubstitutionEntryCollectionForm was saved in the http session but was not registered with the webui.core framework so the form would be removed upon leaving the page. PROBLEM CONCLUSION:? The code was updated to register the saved collection form with the webui.core so that it would be removed when leaving the dynamic clusters page. Directions to apply fix: Fix applies to Editions: Release 8.0 __ Application Server (BASE) X_ Network Deployment (ND) Install Fix to all WebSphere Virtual Enterprise installations. 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. Additional Information: