Fix (APAR):  JR25740

Status:  Fix

Release:  6.0.2

Operating System:  AIX,HP-UX,Linux,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  5839

Date: 2007-02-04

Abstract:  After upgrade to WPS 6.0.2.0 from WPS 6.0.1 by updateinstaller, if customers set up ND environment and use federate or syncNode operations, customers will meet the the problem "jav

Description/symptom of problem:  
 
JR25740 resolves the following problem:

ERROR DESCRIPTION:                                              
syncNode broken after updating BPC 6.0.1 to BPC 6.0.2           
                                                                
Scenario:                                                       
=========                                                       
1. Install BPC 6.0.1                                            
2. Create a dmgr profile                                        
3. Create a custom profile and federate it                      
4. Create an app server and confgure BPC on it                  
5. Update the installation to BPC 6.0.2 (requires the fix for   
387024)                                                         
6. Start the dmgr                                               
7. run 'syncNode localhost -profileName Custom01'               
                                                                
Symptom:                                                        
========                                                        
I get this exception:                                           
ADMU0116I: Tool information is being logged in file             
                                                                
D:\WebSphere\AppServer6012\profiles\Custom01\logs\syncNode.log  
ADMU0128I: Starting tool with the Custom01 profile              
ADMU0401I: Begin syncNode operation for node viennaNode03 with  
Deployment                                                      
           Manager localhost: 8879                              
Internal WPS code problem.  The class wps.extension.checker     
cannot be loaded                                                

LOCAL FIX:                                                      
None.                                                           

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server 6.0.2.0 users

PROBLEM DESCRIPTION:
After upgrade to WPS 6.0.2.0 from WPS
6.0.1 by updateinstaller, if customers
set up ND environment and use federate
or syncNode operations, customers will
meet the the problem "java.lang.
ClassNotFoundException:com.ibm.ws.
management.tools.WBIExtensionChecker"


RECOMMENDATION:
None

When customers upgrade from WPS 6.0.1 to WPS 6.0.2.0 using
updateinstaller to apply the FixPack, customers may meet the
problem:

The class wps.extension.checker cannot be loaded java.lang.
ClassNotFoundException: com.ibm.ws.management.tools.
WBIExtensionChecker

at java.net.URLClassLoader.findClass(URLClassLoader.java
(Compiled Code))

at com.ibm.ws.bootstrap.ExtClassLoader.findClass(ExtClassLoader.

java(Compiled Code))

at java.lang.ClassLoader.loadClass(ClassLoader.java
(Compiled Code))

at java.lang.ClassLoader.loadClass(ClassLoader.java
(Compiled Code))

at java.lang.Class.forName1(Native Method)

at java.lang.Class.forName(Class.java(Compiled Code))

at com.ibm.ws.management.tools.DefaultWPSExtensionChecker.
getImplementation(DefaultWPSExtensionChecker.java:177)

at com.ibm.ws.management.tools.DefaultWPSExtensionChecker.
checkExtension(DefaultWPSExtensionChecker.java:113)

at com.ibm.ws.management.tools.AbstractNodeConfigUtility.
checkProductExtensions(AbstractNodeConfigUtility.java:684)

PROBLEM CONCLUSION:                                             
After upgrade to WPS 6.0.2.0, install the iFix before set up ND 
environment. The problem can be resolved.                       


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: