Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows

---

 

Portal configuration

This topic provides information about configuring the portal.

• Global Settings
  You can use the Global Settings portlet to configure some settings which apply throughout the portal.

• Portal service configuration
  IBM^® WebSphere^® Portal Express comprises a framework of services to accommodate the different scenarios that portals of today need to address. You can configure some of these services.

• Persistent session state (session hibernation)
  With the persistent session state feature, portal users can resume and continue a previously interrupted working session at the same state where they left the session. When the user logs out or the session times out, the portal stores the current navigational state into the database. The administrator can give users the option to resume the navigational state of their last session when logging in again. When the user chooses to resume the last session, the navigational state stored previously is restored, and the user can continue working where the user stopped before.

• Configuring dynamic fragment cache
  This topic refers you to information for configuring dynamic fragment cache for use with WebSphere Portal Express. Dynamic fragment cache (also known as servlet caching) is a component of WebSphere Application Server that provides content caching. You configure and enable dynamic fragment cache by using the administrative console of WebSphere Application Server.

• Portlet filters
  This section provides information on portlet filters in WebSphere Portal Express. A portlet filter enables the administrator of a portal to intercept and modify the output of a portlet before it is aggregated to the entire portal page. Thus it is possible to support different languages and markups other than those for which the portlet was originally designed. Portlet filters are also used for adding additional information to the portlet output (for example, a copyright statement), deleting unimportant or restricted content, and for parsing destructive JavaScript.

• HTTP proxy configuration
  Some portlets use IBM WebSphere Portal Express resources to support HTTP proxy. Loading and caching remote URLs (such as RSS streams or HTML files) is done in the portal by the service URLManager. If you specify an HTTP proxy in the configuration of the service, all remote requests are loaded using this HTTP proxy. This feature enables servers behind a firewall with no direct access to the Internet to load external data, such as news or stock information.

• URL Mapping
  URL Mapping allows portal administrators to create constant user friendly URLs and map them to portal pages. As administrators create the URLs, they can define human readable names for them. These can be remembered and are therefore more user friendly.

• Unique names
  The portal uses object IDs to identify portal resources unambiguously even between different portals. They consist of an extended alphanumeric string which may be difficult to remember. Administrators can use the Custom Unique Names portlet to assign unique names, or human readable names, to portal resources. They can select names which are easy to remember.

 

Parent topic:

Administering

 

Related tasks
Changing the portal URI

---