Configuring the AJAX proxy for the Chat Rooms widget

The AJAX proxy allows HTTP and HTTPS requests to be made across domains. Since the IBM® Sametime® Advanced Server resides on its own server, not on the IBM Connections server, HTTP and HTTPS requests are made through the AJAX proxy.

About this task

The WebSphere® Application Server contains a modifiable proxy configuration file, proxy-config.tpl. For instructions about modifying the file, see this procedure: Configuring the AJAX proxy.

Procedure

In the proxy-config.tpl file, located on the computer hosting the IBM Connections server, modify the url value according to your own configuration.

Note: The proxy must allow the actions, cookies, and headers as shown in the text below.

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

<proxy:policy url="<protocol>://<sametime_advanced_domain>:<port_number>/*" acf="none">
  <proxy:actions> 
  <proxy:method>GET</proxy:method>
  <proxy:method>HEAD</proxy:method>
  <proxy:method>POST</proxy:method>
  <proxy:method>PUT</proxy:method>
  <proxy:method>DELETE</proxy:method>
</proxy:actions>
<proxy:cookies>
  <proxy:cookie>LtpaToken</proxy:cookie>
  <proxy:cookie>LtpaToken2</proxy:cookie>
  <proxy:cookie>JSESSIONID</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>If-.*</proxy:header>
  <proxy:header>Pragma</proxy:header>
  <proxy:header>Cache-Control</proxy:header>
  <proxy:header>X-Update-Nonce</proxy:header>
  <proxy:header>WWW-Authenticate.*</proxy:header>
  <proxy:header>Access.*</proxy:header>
 </proxy:headers>
 </proxy:policy> {code}

Use this format for the url value:

protocol://sametime_advanced_domain:port_number/*

For example,

http://myAdvancedServer.ibm.com:9080/*

https://myAdvancedServer.ibm.com:9443/*

Note: If you have set up the Chat Rooms widget in Connections, and error code 403 is returned, check the AJAX proxy settings to ensure they are correct. For more information, see Troubleshooting.