Required entries for the proxy-config.xml file to configure widgets to work with WebSphere Portal

IBM BPM, V8.0.1, All platforms > Install IBM BPM > IBM BPM Advanced for z/OS: Process Server > Configure IBM BPM Advanced for z/OS: Process Server > Configure components > Configure additional components > Configure Process Portal > Configure the Business Space component for Process Portal > Configure widgets to work with WebSphere Portal
Required entries for the proxy-config.xml file to configure widgets to work with WebSphere Portal

Use the examples of required entries for the proxy-config.xml file to configure the Ajax proxy on the WebSphere Portal server. To allow remote URLs to your product server from the WebSphere Portal server, configure the Ajax proxy.

The following XML snippet shows the proxy policy required for business process management products. This must be set for all remote URLs that you intend to open with the WebSphere Portal proxy, for example, the Business Space server and your business process management server. Replace <REMOTE_BPM_URL> with the remote URL that needs to be opened with the WebSphere Portal proxy.
Tip: The socket-timeout value is set to 10 seconds by default. Business Space uses a proxy component to connect to your Representational State Transfer (REST) services. If REST services are not responsive, change the socket-timeout value to an appropriate value for your situation, for example 30 seconds. See Changing the timeout settings for the Business Space Ajax proxy.
If you have multiple remote servers or URLs that need to be allowed with the proxy for the WebSphere Portal server, customize the proxy configuration by using dynamic policy entries. The proxy policy will differ from one deployment to the other. Refer to WebSphere Portal documentation for different ways to configure the WebSphere Portal server proxy.
The proxy-config.xml is located at WebSphere_Portal_INSTALL_ROOT\base\wp.proxy.config\installableApps\wp.proxy.config.ear\wp.proxy.config.war\WEB-INF.
The updated proxy-config.xml must be reviewed and approved by your WebSphere Portal administrators before being checked into WebSphere Portal.
The following example is for use with WebSphere Portal V7.0.0.2 Cumulative Fix Pack 12 or later:


<proxy:policy url="<REMOTE_BPM_URL>" acf="none">
<proxy:actions>
<proxy:method>GET</proxy:method>
<proxy:method>HEAD</proxy:method>
<proxy:method>POST</proxy:method>
<proxy:method>DELETE</proxy:method>
<proxy:method>PUT</proxy:method>

</proxy:actions>
<proxy:cookies>
<proxy:cookie>LtpaToken</proxy:cookie>
<proxy:cookie>LtpaToken2</proxy:cookie>
<proxy:cookie>JSESSIONID</proxy:cookie>
<proxy:cookie>CRN</proxy:cookie>
<proxy:cookie>caf</proxy:cookie>
<proxy:cookie>cam_passport</proxy:cookie>
<proxy:cookie>cc_session</proxy:cookie>
<proxy:cookie>userCapabilities</proxy:cookie>
<proxy:cookie>usersessionid</proxy:cookie>
</proxy:cookies>
<proxy:headers>
<proxy:header>User-Agent</proxy:header>
<proxy:header>Accept*</proxy:header>
<proxy:header>Content*</proxy:header>
<proxy:header>Authorization*</proxy:header>
<proxy:header>X-Method-Override</proxy:header>
<proxy:header>Set-Cookie</proxy:header>
<proxy:header>If-Modified-Since</proxy:header>
<proxy:header>If-None-Match</proxy:header>
<proxy:header>X-Server</proxy:header>
<proxy:header>X-Update-Nonce</proxy:header>
<proxy:header>X-Requested-With</proxy:header>
<proxy:header>com.ibm.lotus.openajax.virtualhost</proxy:header>
<proxy:header>com.ibm.lotus.openajax.virtualport</proxy:header>
<proxy:header>Slug</proxy:header>
<proxy:header>SOAPAction</proxy:header>
</proxy:headers>
</proxy:policy>

<proxy:meta-data>
<proxy:name>forward-http-errors</proxy:name>
<proxy:value>true</proxy:value>
</proxy:meta-data>
<proxy:meta-data>
<proxy:name>socket-timeout</proxy:name>
<proxy:value>30000</proxy:value>
</proxy:meta-data> 
Configure widgets to work with WebSphere Portal

Related tasks:
Configure widgets to work with WebSphere Portal