Fix (APAR): JR32756 Status: Fix Release: 6.2.0.1 Operating System: AIX,HP-UX,i5/OS,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 11900 Date: 2009-04-24 Abstract: One of the migration script due to incorrect conditional check , it skipped commondb.properties file creation required for augmentation and some updates of WAS variables. Description/symptom of problem: JR32756 resolves the following problem: ERROR DESCRIPTION: During post migration, common database migration is skiped because of which commonDB.properties file not being created in WebSphere Process Server v.6.2.0.1. During runtime, inccorect properties and WAS variables might cause exceptions in administrative console while validating datasource. LOCAL FIX: None PROBLEM SUMMARY USERS AFFECTED: WebSphere Enterprise Service Bus v6.0.2.1 users who migrate and then augment to WebSphere Process Server PROBLEM DESCRIPTION: One of the migration script due to incorrect conditional check , it skipped commondb.properties file creation required for augmentation and some updates of WAS variables. RECOMMENDATION: None Code is checking incorrect variable to see whether profile is valid, results always false , hence migration actions are skipped. PROBLEM CONCLUSION: Code is modified to check correct variable to determine profileType for next migration actions. Apply iFix before migration to resolve the problem. 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: