i-fix Name: {PK31312}


Problem Summary:Template instantiation fails when editing cmty roles and roles created but not mapped

Detail:  For the manageroles.war admin portlet.  Role X displays to the user in the dropdown as if it is mapped.
The problem is, although Role X is displayed it is not actually mapped. 
Role X will not get mapped until the OK button is selected. 


Installation Steps:
{Must take into account any specific things to take into account for clustered environments

Example:
   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. Ensure the pre-requisite fix(es) are installed.
   5. Follow the fix installation instructions that are packaged with
      the Portal Update Installer on how to install a fix.
      NOTE: You must also ensure all pre-requisite fix(es) are installed.
      If you do not, the Portal Update Installer will fail and will list
      the missing pre-requisite fix(es).
   6. Restart WebSphere Portal.        
   7. Note that the <PortalServer>/shared/app/admin.jar was updated.
      And note that this iFix provided new war file(s):
   
      <PortalServer>/installableApps/Xxxxxxxxxxx.war

   8. To install the admin portlets listed above,    

      -- start portal server
      -- logon as wpsadmin 
      -- click on Administration
      -- click on Portlets
      -- click on Manage Applications
      -- update the existing Xxxxxxxx.war with the new one in the installableApps directory

 (Note: Include the followng lines in the readme for WP5.1.x only)
Refer to Clustering->”Performing Upgrades in a 24x7 cluster” section for additional information on applying interim fixes in clustered environments while maintaining continuous availability of your Portal.}


Un-Installation Steps:
{Example:
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 a fix.
   3. Restart WebSphere Portal.

(Note: Include the followng lines in the readme for WP5.1.x only) 
Refer to Clustering->”Performing Upgrades in a 24x7 cluster” section for additional information on applying interim fixes in clustered environments while maintaining continuous availability of your Portal.}