Fix (APAR): JR31369 Status: Fix Release: 6.0.2.5 Operating System: AIX,HP-UX,i5/OS,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: JR31369 Byte size of APAR: 6862 Date: 2008-12-18 Abstract: When Websphere Process Server user upgrate to version 6.0.2.5, there is script missing. And this will block the upgrate of the persistentLkMgr.ear. Description/symptom of problem: JR31369 resolves the following problem: ERROR DESCRIPTION:? WBI installer does not set "wbi.install.root" and as soon as wsadmin is invoked from ${profile_name}/bin, persistentLkMgrAppUpgrade.jacl could not work correctly. The following error message is shown: The persistentLkMgr application was not installed on any server or cluster. LOCAL FIX:? N/A PROBLEM SUMMARY:? USERS AFFECTED: WebSphere Process Server V6.0.2.5 users PROBLEM DESCRIPTION: When Websphere Process Server user upgrate to version 6.0.2.5, there is script missing. And this will block the upgrate of the persistentLkMgr.ear. RECOMMENDATION: For WebSphere Process Server 6.0.2.x users, after they upgrate to 6.0.2.5, they need to use the according ifix to upgrate the persistentLkMgr.ear Websphere Process Server 6.0.2.x users need manually execute a script to upgrate persistentLkMgr.ear to make Eventsequencing related function upgrate. However this script is not exist because the output group is not added in component.xml, so build team not pickup the script. Also, the script it self has problem, as if the persistentLkMgr.ear is not found, the uninstall process will also be execute which is not logically. PROBLEM CONCLUSION:? The script for ungrate the persistentLkMgr.ear is modified to include that if persistentLkMgr.ear not found, then uninstall process will not be executed. And also component.xml and build.xml is modified to make sure the script will apear in future releases. Applying this interim fix will resolve the issue. 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: