|
|
This chapter summarizes Oracle WebCenter user interface customization techniques, most of which do not require special programming skills.
The purpose of this chapter is to help you scope the effort of implementing the user interface for your deployment.
This chapter includes the following sections:
Experience Definitions determine many aspects of the user interface for broad groups of users. Experience Definitions control your start page when you log in, the features available to you, the appearance of your navigation, and what mandatory links are shown in your navigation.
You can create a number of Experience Definitions for different audiences, including unauthenticated or guest users.
For information on configuring Experience Definitions, refer to the Administrator Guide for Oracle WebCenter Interaction.
You may want to change the look and content of a page in ways that CSS changes do not allow. Adaptive page layouts allow you to change the look and feel of the portal user interface using adaptive tags in standard XHTML.
For details on Adaptive Layouts, see the Oracle WebCenter Interaction UI Customization Guide.
Portal navigation is customizable; in fact, the portal ships with eight different navigation options out of the box. Navigation controls everything outside the center of the page, not including the header and footer. To change the navigation presented to a user, edit the Navigation Options in the Experience Definition editor.
Navigations are pluggable; that is, you can develop new navigations using programming languages like C++, Visual Basic .NET, Java, or by simply defining them in XML.
Although navigations are associated with Experience Definitions, each navigation can be very dynamic, displaying a completely different look for each page type, each user, or any other settings you like. For example, the support center navigation shows completely different HTML when you are on a support center community, even though it is all done within a single pluggable navigation view. The support center navigation is downloadable from the Oracle Technology Network at http://www.oracle.com/technology/index.html.
If you are happy with the layout of your existing portal and simply want to change things such as fonts, colors, logos, and images, you can override all those settings by changing your style sheet. Oracle WebCenter supports localization of style sheets into many languages, the easiest way to modify a style sheet for a multi-language portal is to use the Style Sheet Mill, which takes values from template files and uses them to generate style sheets in multiple languages using localized text from our translation files.
For details about the Style Sheet Mill, see the Oracle Technology Network at http://www.oracle.com/technology/index.html.
You can apply different headers and footers to different Experience Definitions and communities. The headers and footer set for the Experience Definition are applied to the entire interface, except for communities that have their own custom headers and footers.
Oracle-BEA AquaLogic Interaction Publisher provides three branding portlet templates that enable you to customize the look and feel of Experience Definitions and communities:
You can create and configure branding portlets from these portlet templates using the Portlet Editor and Oracle-BEA AquaLogic Interaction Publisher’s Configure Portlet Wizard. You can create and customize these branding portlets for your communities and Experience Definitions.
You can also customize the way a header or footer appears in a particular community by using the Community Preferences page from the Community Editor.
For details, see the Administrator Guide for AquaLogic Interaction Publisher.
Sometimes you want to add new functionality rather than modify existing functionality. Oracle WebCenter Interaction has a large number of event categories you can hook into, each with several different event types. For example, you might change the post login behavior: for users who had not yet filled in their user profiles, you could have them redirected to the user profile form. To accomplish this, you would need to implement not only a PEI, but a custom activity space, model, view, and controller for any special landing pages you wanted to write from scratch. You could also use Dynamic Discovery to override a view class for an existing page.
For details on PEIs, see the Oracle Technology Network at http://www.oracle.com/technology/index.html.
You might want to precisely control the exact look of the center of the page, as well. For example, you might want to control how portlets are rendered on the page. The file MyPortalContentView renders portlets into columns based on your page layout style. You might want to redesign that page center so that the portlets are arranged in rows instead of columns. For this, you would need to override the default view with your own, using dynamic discovery, also outlined in the development documentation on the Oracle Technology Network at http://www.oracle.com/technology/index.html.
A more forward-compatible approach involves extending ActivitySpaces, by creating new ActivitySpaces and views that extend existing ones and directing PEIs and other links to those new spaces. Then, as Oracle WebCenter Interaction improves existing activity space components, your code will benefit.
|