i-fix Name: PK34865


Problem Summary: 
Default theme not always set properly when creating a new virtual portal.
Also, theme doesn't seem to be properly applied to the new portal.


Detailed Problem Description:
This problem has been seen under the following conditions.
Create a new virtual portal and specify a theme other then the default theme AS 
the new virtual portal's default theme. When finished creating the new virtual
portal immediately edit it. The new virtual portal's default theme will be the 
original default theme and NOT the theme that was selected as the default when
creating the virtual portal.


Problem Analysis:
The incorrect user ID was used to modify the default theme setting. The current 
user ID should have been used. Also, the xnlaccess script should be executed
prior to setting the default theme. Finally, in addition to setting the default
theme in the context root of the virtual portal, the theme for My Portal
must also be set to the new default to override its initial WebSphere setting.


Failing Module: ManageVirtualPortals.war


Problem Solution:
Used the current user ID as input to the command to change the default theme
for the virtual portal, etc. See problem description.


Affected Users:
Customers who create virtual portals and use different default themes for them.


Requisites: None

Platform Specific: No

Fix pack: 5.1.0.5

Installation Steps:

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 this iFix provided new war file(s):
   
      <PortalServer>/installableApps/ManageVirtualPortals.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 ManageVirtualPortals.war with the new one in the installableApps directory

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:
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.
   4. Update the existing ManageVirtualPortals.war with the original (previous) one in the 
      installableApps directory

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.