The new modularized theme allows customers to customize bootstrap parameters, such as djConfig and ibmCfg, for their custom Portal 7.0.0.2 themes.

Create a custom version of the dynamic content as a new war file and a custom version of the static content by creating a folder in the filestore. No further customization was performed so far. An xml access script was also created that can be used to register the themes and skins that are part of ...

Modern websites and browsers enable incredible new capabilities that can greatly enhance your user's web experiences. However, these capabilities are not without cost in terms of large page sizes and more process in the browser when each page is rendered. These capabilities are worth it when you ...

Create a custom version of the dynamic content as a new ear file and a custom version of the static content by creating a folder in the filestore. For more information about copying a theme for customization, see Copying the theme. No further customization was performed so far. Also, an xml access ...

You must adapt the scripts that register the custom theme and skins that are moved from the filestore.

A list of Dojo classes that are provided by each version 1.6 Dojo metamodule.

You must adapt the list of required runtime configuration changes for your theme.

Restart your portal server and test the new custom ear file on your test server to verify that it deploys successfully.

Add static content for the custom theme you created based on one of the portal readyuse themes.

You can change the profile for a specific page to define the modules loaded.

You can change the profile for the theme or a specific page to define the modules loaded.

You can change the profile for the theme or a specific page to define the modules loaded.

The process of assigning a device class to one of the supported clients in WebSphere Portal. Usually, when a certain device class needs to be supported, the first step is to create client definitions for each of the devices that belong to this class. Then, you create a device class and assign the ...

You can manually assign a device class to a client.

IBM® WebSphere Portal offers a filtering feature for portlet capabilities based on the existing client side capabilities.

To enable device support, which represents your static page for different device classes, bundle the static markup files that are deviceclassspecific into a compressed file.

Device classes are used in IBM® WebSphere Portal as an abstraction for common properties for the device of a client. For instance, tablet computers can be grouped into a device class tablets, since they share a form factor and possibly other traits such as touch interface, or additional hardware ...

Set the following properties in the Wp ConfigService Resource Environment Provider to enable or disable the various capability filters.

You can create and delete device classes using the XML configuration interface.

This example creates a client that matches devices sending iPhone in the user agent. The device class smartphone is also assigned to the client.

JavaScript content includes module resources defined by js files used by the theme.

Static resources include the markup defined by html, css and js files used by the theme. There are also .json files that are used to define menu options, module definitions, and module profiles.

Dynamic content includes resources defined by jsp files used by the theme.

The IBM® WebSphere Portal 7.0.0.2 theme contains three types of files: JavaScript, dynamic content (JSPs) and static resources.

You can scope layouts so that only certain ones show up in your custom theme. The IBM® WebSphere Portal 7.0.0.2 theme included with the portal uses this technique.