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

Configuring portal behavior

This topic provides information about configuring the portal.

• Set the language of the portal
  Put your short description here; used for first paragraph and abstract.
• Changing object IDs to human readable names
  Put your short description here; used for first paragraph and abstract.
• Set what users see when they log in to the portal
  Put your short description here; used for first paragraph and abstract.
• Set the search engine the opens when users select Find
  Put your short description here; used for first paragraph and abstract.
• Configuring user session persistance
  Put your short description here; used for first paragraph and abstract.
• Set how to handle portlets that the user is not authorizes to view
  Put your short description here; used for first paragraph and abstract.
• Configuring portlet filtering
  Put your short description here; used for first paragraph and abstract.
• Keeping filter mappings consistent with servlet mappings
  Put your short description here; used for first paragraph and abstract.
• 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.
• Delayed cleanup of deleted portal pages
  This section describes the cleanup service for portal pages and their dependent resources.
• 
  This topic describes how you delete orphaned data in the database. To do this, you use the SLCheckerTool.