You can use various JSPs and theme policies to customize the look and feel of the portlet.
For devices that support changing various style attributes (such as text color, background color, font weight, and justification), the XDIME aggregator provides a theme policy named wp_styles_locale.mthm (where locale is the locale suffix supported by the theme). For smartphones, the theme policy is named wp_smt_style_locale.mthm. The wp_styles theme associates various attributes with named style rules. New style rules can be added to provide a wider variety of type styles from which to choose.
The WebSphere® Portal logo () shown in most views of the XDIME aggregator can be replaced by creating an image policy and referring to the new policy. The WebSphere Portal logo image policy is called /wp/logo.mimg. For most navigation views, the logo is defined within a shared JSP in MPATheme.war/themes/xdime/mpatheme/common/Header.jsp. For the PDA navigation view, the logo is defined within a special JSP in MPATheme.war/themes/xdime/mpatheme/pdaview/Banner.jsp. If you create an image policy, both header.jsp and banner.jsp must be updated.
The XDIME aggregator also provides default image policies for log in, log out, and forgot password. All image policies can be modified to use different images. Or you can create new policies for those functions and update the JSPs to use the new policies.
With the XDIME aggregator, you can display images with the navigation links in the list or tree view, with the navigation links in the icon view, and with portlet titles in the PDA view. The image policy used to display an image is configured by setting an extended property using the Manage Mobile Pages portlet. If no image is specified, the aggregator can be configured to display a default image for a page, portlet, or URL. The default images specified are different for different views. The image policy used for the default image is specified in the mwp.properties file.
The style of the markup in a portlet is determined by ControlDefault.jsp (for treeview, iconview, pdaview, and wmlview), and ControlSmartPhone.jsp (for smartphone view).
Control.jsp automatically includes either ControlDefault.jsp or ControlSmartphone.jsp depending on the view selected.
The style and location of the portlet controls are specified by the Multi-Channel Server layout policy used in ControlDefault.jsp or ControlSmartphone.jsp and the MCS theme policy used by the aggregator.