When you want all of your portal to reflect your enterprise's trademark look and feel, you can use the
uiwizset.sql script to customize the colors and fonts of the Oracle Portal design-time dialogs, such as the Add Item and Add Portlet screens. The script modifies Oracle Portal user interface style preferences and saves the modifications to the preference store in the Oracle Portal schema.
You will find the
uiwizset.sql script at the following location:
The script contains default values for dialog colors and fonts. Before you alter the script, back it up to allow for returning dialogs to their default style values.
The script also contains an explanation for each entry. These will guide you further toward successful use of the script. This appendix includes a few notes to assist with script editing:
When a style requires a color, use hexadecimal values to specify your color choice. For example:
p_font_color => '#FFFFFF'
All styles requiring fonts reference the constant
DEFAULT_FONT defined near the beginning of the script. Each parameter
p_font_name references this constant. Enter a string of font choices, separated by commas. Each user's browser will pick the first font on the list that is available on the user's own system.
If you plan to change each
p_font_name parameter individually, enter a font string in the same format you would use for the constant. For example:
p_font_name => 'Arial, Helvetica, Geneva, sans-serif'
When a style requires a font size, specify a numerical value and a unit of measurement. For measurement, use one of the following standard Web font measurement units:
px fixed unit (pixels, though relative to the viewer's monitor)
pt fixed unit (points)
em relative unit (relative to the font size of the last specified font)
ex relative unit (relative to the "X" size of the last specified font)
% relative unit (relative to the font size of the last specified font)
p_font_size => '16pt'
Use any text editor to edit
uiwizset.sql to reflect your font and color preferences. Then run the script, for example, in SQL Plus, against the Oracle Portal schema.
Because the style sheet is expiry-based cached, you must wait 24 hours for the cache to expire automatically and your changes to display. If you are testing your design on a pre-production version of your portal, you can take the following steps to display applied script changes immediately:
With the following steps, the cache is being cleared. When cache is cleared, the performance of the portal may be impacted. If performance is a concern, the following steps should be performed during off-peak hours.
Clear the Portal Cache on each midtier used to access your portal:
Navigate to the portal cache directory.
The default path is
Perform a recursive delete of all the files under this directory.
For example, on UNIX platforms, issue the following command:
rm -rf plsql/sys/*
Ensure that you are in the correct directory before issuing this command. Do not delete the
cache directory. For more information, see Oracle Fusion Middleware Administrator's Guide for Oracle Portal.
Clear all Web Caches that are used to access your portal. For information on clearing Web Cache, see Oracle Fusion Middleware Administrator's Guide for Oracle Web Cache
If, after clearing these caches, the changes do not display in your browser, reload the browser page. To reload, click your browser's Refresh button, or Reload current page button, or whichever variation of this button your browser uses.