Fix (APAR): JR25932 Status: Fix Release: 6.0.2 Operating System: AIX,HP-UX,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: JR25932 Byte size of APAR: 7190 Date: 2007-03-13 Abstract: For WPS version 6.0.2, when the nodeagent and the Deployment Manager share the same filsesystem, the syncNode utility is not able to determine the name of the node to synchronize w Description/symptom of problem: JR25932 resolves the following problem: ERROR DESCRIPTION: The synchNode command in certain topologies for WebSphere Process Server 6.0.2 fails. THe result of running NodeSync is as follows: ADMU0111E: Program exiting with error: com.ibm.websphere.management.exception.ConfigDataNotFoundExcepti on: ADMG0001E: Configuration data cells/testwastmp5aNetwork/nodes/testwastmp5aManager|node.xml is not found in document cells/testwastmp5aNetwork/nodes/testwastmp5aManager/node.xml. - This problem does NOT occur with a topology that simulates a distributed cell i.e. DMGR install managing a separate nodeagent install (even if both are on the same machine). - This problem occurs with a topology more common to a test environment where both cell manager and managed node reside in the same install filesystem. - I have verified this problem occurs only for 602 and does not occur with 601. - The problem started in 602 with the introduction of the WPSVersionChecker.class in the following callstack: 71469 debug: callstack is: java.lang.Exception at com.ibm.wbiserver.nd.checker.WPSVersionChecker.checkVersion(WPSV ersionCh ecker.java:137) at com.ibm.wbiserver.nd.checker.WPSExtensionChecker.checkExtension( WPSExten sionChecker.java:134) at com.ibm.ws.management.tools.DefaultWPSExtensionChecker.checkExte nsion(De faultWPSExtensionChecker.java:115) at com.ibm.ws.management.tools.AbstractNodeConfigUtility.checkProdu ctExtens ions(AbstractNodeConfigUtility.java:684) at com.ibm.ws.management.tools.NodeSyncUtility.runTool(NodeSyncUtil ity.java :136) at com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.j ava:226) at com.ibm.ws.management.tools.NodeSyncUtility.main(NodeSyncUtility .java:55 ) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor Impl.jav a:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor Impl.jav a:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod Accessor Impl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:219) at java.lang.Thread.run(Thread.java:568) LOCAL FIX: A test fix/interim fix will be made available PROBLEM SUMMARY USERS AFFECTED: WebSphere Process Server 6.0.2 users PROBLEM DESCRIPTION: For WPS version 6.0.2, when the nodeagent and the Deployment Manager share the same filsesystem, the syncNode utility is not able to determine the name of the node to synchronize with the Deployment Manager. The problem occurs because the WPSVersionChecker logic for returning the node name is incorrect. RECOMMENDATION: None The WPSVersionChecker class has been modified to correctly determine the name of the node. This enables the syncNode utility to find the name of the nodeagent in order to synchronize the nodeagent with the Deployment Manager. PROBLEM CONCLUSION: Directions to apply fix: Before applying the iFix ensure that WebSphere Process Server 6.0.1 is installed on the system. Also 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 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. 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 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: