PY00233 ======= Problem 1 Description: Portlet theme policies are not recognized with XHTML devices that have the css.multiclass.support attribute set to none. If the style rule name is not unique to the portlet policy (ie, there is a rule named "title" in both the portlet and aggregator policy), then the style rule from the global theme is picked up and not the rule from the portlet policy. If the style rule name is unique, the style is not picked up by the browser. Problem 1 Solution: Produce a CSS for the portlet theme that is recognizable by the device. Problem 2 Description: Space characters " " are not honored by MCS when placed in a Problem 2 Solution: space encodings will be honored. Note, if several 's are next to each other, MCS will only generate one space in the device dependent markup. Affected Users: Mobile users Pre-Requisite(s): WebSphere Everyplace Mobile Portal Version: 5.0 WebSphere Everyplace Mobile Portal Fixes: None WebSphere Portal Fixes: None Installation: NOTE: YOU MUST FIRST DOWNLOAD THE WEBSPHERE PORTAL UPDATE INSTALLER TOOL FOR VERSION 5.0.x 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. DO NOT restart WebSphere Portal until you completed the following MCS database: The following changes are necessary for the database repository in relation to the work for displaying Accesskeys in menus in xhtml 1 new table has been added VMREPLACEDPROPERTIES. Table VMMENUPROPERTIES requires 3 new columns added. On your DB2 or Oracle database server, configure the MCS database. The following instructions illustrate how to configure the MCS database using DB2: . Log on to DB2 instance user . Make sure the db2 server is started: db2start . Connect to the mcs database: db2 connect to mcs user using . If your database server is on the same server as WebSphere Portal, go to the /repository/db2 directory: cd /repository/db2 Otherwise, transfer the /repository/db2/add_tables.sql file from your WebSphere Portal server to a directory on your database server. Go to the directory containing the create_tables.sql file. . Add the MCS tables: db2 -tf add_table.sql . Alter the MCS tables: db2 -tf update_table.sql The following instructions show how to configure the MCS database using Oracle: * Login to the Oracle user. (NOTE: Users in Oracle are equivalent to database instances in DB2.) * Make sure ORACLE_HOME and ORACLE_SID are set properly: echo $ORACLE_HOME --> If it does not return any thing then do steps 1 and 2. Otherwise skip those two steps. 1. ORACLE_HOME=/OraHome1 (e.g. /export/home/oracle/OraHome1 or /space/oracle/OraHome1) 2. export ORACLE_HOME echo $ORACLE_SID --> If it does not return "mcs" then do steps 3 and 4. Otherwise skip those two steps. 3. ORACLE_SID=mcs 4. export ORACLE_SID * If your database server is on the same server as WebSphere Portal, go to the /repository/sql92 directory: cd /repository/sql92 Otherwise, transfer the /repository/sql92/create_tables.sql file from your WebSphere Portal server to a directory on your database server. Go to the directory containing the create_tables.sql file. * Start SQL*Plus (the Oracle Sql command line tool), and type the following commands to log in: sqlplus Press Enter Enter user-name: Enter password: SQL> connect Enter user-name: Enter password: Connected. * Update the MCS tables: SQL> start add_table.sql SQL> start update_table.sql * exit sqlplus: exit 6. Restart WebSphere Portal. 7. The temporary directory may be removed. 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.