analytics/configuration/icd/proxy/proxy-config.xml

<?xml version="1.0" encoding="UTF-8"?>
<!--
+========================================================================+
| IBM Confidential
| OCO Source Materials
| IBM Cognos Products: BUX
| (C) Copyright IBM Corp. 2010, 2011
|
| US Government Users Restricted Rights - Use, duplication or
| disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
+========================================================================+
-->
<!-- ************************************************************************************
Listed below are example rules that can be used to control the behavior of the AjaxProxy

If the context-path of the Web Application is /myapp, then the <proxy:mappings> would be
interpreted as the following:

Example #1:
<proxy:mapping contextpath="/http/*" />

The following request would map through the proxy:
       http://localhost/myapp/proxy/http/www.cnn.com

       would be the same as issuing a page request to http://www.cnn.com

       NOTE: The Ajax Proxy does not attempt to do URL rewriting on HTML pages.  In other words,
             the URI's contained in the page returned by http://www.cnn.com will not be modified
             to map through the proxy.

Example #2:
<proxy:mapping contextpath="/rss/money_latest.rss" url="http://rss.cnn.com" />

The following request would map through the proxy:
       http://localhost/myapp/proxy/rss/money_latest.rss

       would be the same as issuing a page request to http://rss.cnns.com/rss/money_latest.rss

Security Note:
The Ajax proxy should be configured to map to the specific service that you are trying to connect
too.  In the example configuration below, the <proxy:mapping contextpath> is shown to map to
http/* and https/*  Those mapping are intended for development and are generic enough to get you
up and running quickly, but they configure the proxy as a relay service to any http or https
endpoint - which is bad and should be removed in production.

The mappings should only contain the specific service you intended to connect with.  As an example,
the <proxy:mapping contextpath> for the url http://rss.news.yahoo.com will only map context paths
of /rss/tech.  The proxy will only allow connections to the intended service endpoint.


************************************************************************************************ -->
<proxy:proxy-rules  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:proxy="http://www.ibm.com/xmlns/prod/sw/ajax/proxy-config/1.0">

    <proxy:mapping contextpath="/http/*"/>
    <proxy:mapping contextpath="/https/*"/>


    <!-- *******************************************************************************************

    If required, the Ajax proxy can be configured to connect to a pass-thru proxy.
    A pass-thru proxy is often used as a border firewall before an application can
    access the network.  The Ajax proxy supports Basic authentication.

    passthru_host  (REQUIRED)                      : The hostname or IP address
                                                     of the pass-thru proxy
    passthru_port  (OPTIONAL Default is port 80)   : The port of the pass-thru proxy
    passthru_realm (OPTIONAL Default is any realm) : The security realm the Ajax
                                                     proxy will authenticate against.
    passthru_username (OPTIONAL)     : The username the Ajax proxy will use to authenticate
    passthru_password (OPTIONAL)     : The password the Ajax proxy will use to authenticate

    ************************************************************************************************ -->
    <!--
    <proxy:meta-data>
       <proxy:name>passthru_host</proxy:name>
       <proxy:value>127.0.0.1</proxy:value>
     </proxy:meta-data>
    <proxy:meta-data>
       <proxy:name>passthru_port</proxy:name>
       <proxy:value>81</proxy:value>
     </proxy:meta-data>
    <proxy:meta-data>
       <proxy:name>passthru_realm</proxy:name>
       <proxy:value>MyRealm</proxy:value>
     </proxy:meta-data>
    <proxy:meta-data>
       <proxy:name>passthru_username</proxy:name>
       <proxy:value>username</proxy:value>
     </proxy:meta-data>
    <proxy:meta-data>
       <proxy:name>passthru_password</proxy:name>
       <proxy:value>password</proxy:value>
    </proxy:meta-data>
    -->

</proxy:proxy-rules>