Application specific proxy configurations

In addition to using the global proxy configuration of the portal, we can also define application specific proxy configurations.

To define an application specific proxy configuration, ensure the following:

• The application, for example a portlet application, needs to register the proxy servlet in its Web deployment descriptors file WEB-INF/web.xml. For an example refer to the topic about Using the AJAX proxy in portlets.

• Place a proxy-config.xml file that represents the application specific configuration in the WEB-INF directory of the portlet WAR file.

Application specific configurations take precedence over the global proxy configuration. This means that if a portlet provides its own configuration file, the proxy ignores the global configuration and uses the application specific configuration instead. To update an application specific configuration, you need to redeploy the portlet by a Web module update after you modifyied the proxy-config.xml file.

Benefits of application specific proxy configurations versus the global proxy configuration:

Benefits of application specific proxy configurations:

Use an application specific configuration can be beneficial if a portlet needs to load content from servers that must not be accessible across the board by all deployed applications.

Benefits of the global proxy configuration:

In large deployments with many deployed portlets using only the global proxy configuration creates less administration overhead. In such configurations application specific configurations can create more administration overhead: A security administrator needs to maintain multiple proxy-config.xml files spread across different WAR and EAR files. To enforce the global proxy configuration, administrators can specify the following configuration setting in the portal Config Service:

proxy.enforce.global.config = true # default: false

If true, the proxy ignores all proxy-config.xml files inside portlets. To change the setting of this property, use the WAS admin console.

Parent: AJAX proxy configuration
Related reference:
Use the AJAX proxy in portlets