Setting up the proxy configuration in WebSphere Portal

The following steps describe how to configure the WebSphere® Portal Ajax Proxy prior to integrating the Leap Portlet with WebSphere Portal .

Ensure the SSO is configured between Leap and WebSphere Portal before completing the following steps.

Note: The instructions contain information for both WebSphere Portal 8.0 and 8.5.x.

To use a Leap application in WebSphere Portal , you must configure the WebSphere Portal Ajax Proxy to allow communication between the web browser and Leap.

Prepare the proxy file: Make a copy of the proxy-config.xml file. Copying the file allows you to revert to the original version if an error occurs after modifications are made.

The proxy-config.xml file is located in the wp.proxy.config.war file. The wp.proxy.config.war file is located in the AJAX Proxy Configuration.ear file. The complete file path for the proxy configuration is: wp_profile/config/cells/applications/AJAX Proxy Configuration.ear/deployments/AJAX Proxy Configuration/wp.proxy.config.war/WEB-INF/proxy-config.xml.
1. In the copy of the proxy-config.xml file, add the contents of proxy-config-Portal-x.xml file.
  
  The proxy-config-Portal-x.xml file is located in the Leap installation directory: install directory/deploy/portlet/proxy-config-Portal-x.xml, where x represents your version of WebSphere Portal .
  
  For WebSphere_Portal 8.0.x, you must change the policy URL from “{$formsexperiencebuilder_url_policy}” to the location of your Leap server. Ensure you have “/*” after the server name. For example: <policy url="http://server:port/apps/*" acf="none">.
  
  For WebSphere_Portal 8.5.x, you must change the policy URL from “{$formsexperiencebuilder_url_policy}” to the location of your Leap server. Ensure you have “/*” after the server name. For example: <policy url="http://server:port/apps/*">.
2. In the meta data section, add the following information:
```
<meta-data>
	      <name>forward-http-errors</name>
      <value>true</value>
</meta-data>
```
Configure the proxy: Use the modified copy of the proxy-config.xml file configure the proxy. You will need your WebSphere Portal , and WebSphere Application Server administrative passwords. Open a command prompt and enter the following command:
- On Windows™: wp_profile\ConfigEngine\ConfigEngine.bat -DWasPassword=<wasAdminPass> -DPortalAdminPwd=<portalAdminPass> checkin-wp-proxy-config -DProxyConfigFileName=<Path to proxy-config.xml file>
- On Linux™: wp_profile/ConfigEngine/ConfigEngine.sh -DWasPassword=<wasAdminPass> -DPortalAdminPwd=<portalAdminPass> checkin-wp-proxy-config -DProxyConfigFileName=<Path to proxy-config.xml file>
Note: If your Path to proxy-config.xml file contains spaces, you must enclose the path with quotation marks. For example: -DProxyConfigFileName="<Path to proxy-config.xml file>".

Note: If you are deploying on a cluster, make the following changes on your deployment manager and your application server nodes and ensure you synchronize your application server nodes after you complete the changes.

Edit a copy of the proxy-config.xml file.
Copy the edited file to the same location on all your nodes and your deployment manager. For example, copy the file to /wp_profile/proxy-config.xml.
Run checkin-wp-proxy-config on all nodes, and your deployment manager.
Trigger a synchronization.

Restart the WebSphere Portal server.

For more information on the HTTP proxy for AJAX applications, see WebSphere Portal documentation.
For more information on global AJAX proxy configuration settings, see WebSphere Portal documentation.