Fix (APAR): JR26563 Status: Fix Release: 6.0.2.1 Operating System: AIX,HP-UX,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 6599 Date: 2007-06-11 Abstract: The Stand alone profile of a portal Server cannot be federated to 602 WPS/WESB DMGR because of the new intervention of WPS code in 602. This causes the portal server to fail during Description/symptom of problem: JR26563 resolves the following problem: ERROR DESCRIPTION: Because of the changes made in 602 where we support the federation of a WPS standalone profile to WPS Dmgr the portal standalone profile cannot be federated. The plan for 602 was to support only the WPS/WESB standalone profile. However the request was to add this support to help in portal setup scenarios. LOCAL FIX: None PROBLEM SUMMARY USERS AFFECTED: WebSphere Process Server 6.0.2.x Users PROBLEM DESCRIPTION: The Stand alone profile of a portal Server cannot be federated to 602 WPS/WESB DMGR because of the new intervention of WPS code in 602. This causes the portal server to fail during federation. RECOMMENDATION: None Federation of Websphere Portal Stand alone profile fails in 602.x release. This is a problem as it was not planned as a part of the 602x stream to support this feature. PROBLEM CONCLUSION: JR26528+JR26070 for WPS 6021 JR26528+JR26537+JR26070 Should be applied for WESB 6021. This fix only addresses the federation or addnode option during profile augmentation but there was another Portal problem that will need to be addressed if needed. THe other issue is with starting of Portal Node. 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: