Global proxy configuration

Global proxy configuration

The portal also provides a global proxy configuration. By default it applies to all applications that use the AJAX proxy.
Alternatively, applications can also provide their own proxy configuration. For details refer to the following topic about application specific proxy configurations.
The global proxy configuration of the portal is located in a separate enterprise application that is deployed during the portal installation. The corresponding enterprise application archive is named AJAX Proxy Configuration.ear.
The file proxy-config.xml that represents the global configuration is located in the WAR file wp.config.proxy.war. That file is part of the EAR file and located in the WEB-INF directory.

Customize the global proxy configuration by using the AJAX proxy configuration.ear

To update the global proxy configuration, redeploy the enterprise application archive that contains the modified proxy-config.xml file and restart it.
You do not need to restart the entire portal server.

Customize the global proxy configuration by using dynamic policy entries

Additional to updating the AJAX proxy configuration enterprise application, you can also customize the effective global AJAX proxy configuration by using the portal WP ConfigService Resource Environment Provider (REP). You do this by matching the values in the WP ConfigService REP with so called dynamic policy entries in the global proxy configuration file. For details about how to do this refer to the topics about the Portal configuration properties and Setting service configuration properties.
A dynamic policy entry differs from a non-dynamic policy entry in that it uses replacement variables instead of URL patterns in the policy element url attribute. A policy element url attribute is considered to be a replacement variable definition if the attribute value starts with the string {$ and ends with the string }.
For example, a policy entry url attribute value of {$my.custom.url.target} defines a dynamic policy replacement variable named my.custom.url.target. You can specify the individual attribute values that you want to be used for replacing the url replacement variable by using corresponding entries in the WP ConfigService REP. The matching is done based on the following custom property naming scheme:
wp.proxy.config.urlreplacement.variable_name.suffix
wp.proxy.config.urlreplacement

This prefix identifies the property to define a dynamic policy replacement value.

variable_name

This variable identifies the target dynamic policy element in the global proxy configuration file.

suffix

This suffix represents a string of your choice that makes the key unique within all replacement keys that refer to the same dynamic policy replacement variable, if there is more than one.

Example: The default global proxy-config.xml file contains the following dynamic policy entry:
<proxy:policy url="{$default_policy}" acf="none">
   <proxy:actions>
      <proxy:method>GET</proxy:method>
      <proxy:method>HEAD</proxy:method>
   </proxy:actions>
</proxy:policy>
To attach this policy to outbound requests to URLs that match one of the URL patterns http://www.some.server.com/* or http://some.other.server.com/*, you can add the following two custom properties to the WP ConfigService resource environment provider:
wp.proxy.config.urlreplacement.default_policy.1=http://www.some.server.com/* wp.proxy.config.urlreplacement.default_policy.2=http://some.other.server.com/*
Default global proxy configuration
The default global proxy configuration file allows plain HTTP GET requests to the following URL patterns:

http://www-03.ibm.com/*
http://www.redbooks.ibm.com/*

Furthermore, there are two dynamic policies defined in the default global proxy configuration file:

default_policy

This policy allows plain HTTP GET and HEAD requests.

default_ltpa_policy

This policy allows authenticated HTTP GET and HEAD requests within the WebSphere LTPA token based single sign-on domain.

Parent topic:
AJAX proxy configuration

Related tasks

Set service configuration properties

Related reference

Portal configuration services