Name: PK34220
=============
 
Summary:
   Unable to load class: com.ibm.task.api._HumanTaskManagerHome_Stub
 
Problem Description:
   In case the Portal will be used with a remote process server, the library 
   definition for the 
   BPELib was not made neither was the library mapped to the Process Portlet. 
   This resulted in a non working Portlet.
   
[11/1/06 16:26:44:885 CST] 000000a5 ServletWrappe E   SRVE0014E: Uncaught service() exception root cause /themes/html/IBM/Default.jsp: Unable to load class: com.ibm.task.api._HumanTaskManagerHome_Stub
[11/1/06 16:26:44:891 CST] 000000a5 DispatcherSer E com.ibm.wps.services.dispatcher.DispatcherServiceImpl handleRequest EJPFD0004E: The dispatcher call resulted in an error.
java.lang.ClassCastException: Unable to load class: com.ibm.task.api._HumanTaskManagerHome_Stubat com.ibm.rmi.javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:371)
 
Problem Solution:
   The action action-setup-process-integration was extended to create the 
   missing library BPELib and map it to the portlet. Since the library 
   definition holds node specific path information, the definition has to have 
   node scope. Thus the action action-setup-process-integration has to be 
   executed on each cluster node. 
   
 
Failing Module(s):
   Engine: Portal Configuration
 
Affected Users:
   All Users
 
Version Information:
    Portal Version(s): 6.0.0.0
     Pre-Requisite(s): 
      Co-Requisite(s): ---
 
Platform Specific:
   This fix applies to all platforms.
 
Installation:
   NOTE:  YOU MUST FIRST DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX.
          The Portal Update Installer can be downloaded from the following link:
          http://www.ibm.com/software/genservers/portal/support
 
   1. Create temporary "fix" directory to store the jar file.
   2. Copy jar file to this directory.
   3. Shutdown WebSphere Portal.
   4. Follow the fix installation instructions that are packaged with
      the Portal Update Installer on how to install the fix.
   5. Restart WebSphere Portal.
   6. The temporary directory may be removed.
 
Un-Installation:
   NOTE:  FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED.  DO NOT REMOVE
          A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.
          YOU MAY REAPPLY ANY REMOVED FIX.
 
   1. Shutdown WebSphere Portal.
   2. Follow the instructions that are packaged with the
      Portal Update Installer on how to uninstall the fix.
   3. Restart WebSphere Portal.