HTTP proxy configuration
Some portlets use WebSphere Portal 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.
The WP PortletServiceRegistryService in the WAS console is used for configuring WebSphere Portal for HTTP proxy. For more information, refer to Content Access Service > Portal configuration services and Content Access Service > Proxy protocol and port settings at http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1/topic/com.ibm.wp.ent.doc_v615/admin/srvcfgref.html#srvcfgref__cont_acc_srvc.
Parent
Configure portal behavior
Overview of configuration services