The AJAX proxy allows HTTP and HTTPS requests to be made
across domains. Since the IBM® Sametime® Meeting 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 which hosts 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.
{code:}
<proxy:policy url="https***/*" 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:headers>
<proxy:header>X-ST-CSRF-Token/proxy:header>
<proxy:header>User-Agent/proxy:header>
</proxy:headers>
<proxy:cookies>
<proxy:cookie>LtpaToken/proxy:cookie>
<proxy:cookie>LtpaToken2/proxy:cookie>
<proxy:cookie>JSESSIONID/proxy:cookie>
<! ;/proxy:cookies>
</proxy:policy> {code}
Use this format for the url
value:
protocol://sametime_meetings_domain:port_number/*
For
example,
http://myMeetingsServer.ibm.com:9080/* or
https://myMeetingsServer.ibm.com:9443/*
Note: If
you have set up the widget in Connections, and error code 403 is returned,
check the AJAX proxy settings to ensure they are correct. For more
information, see Troubleshooting.
- Update proxy-policy.dynamic as follows to enable the AJAX
proxy to permit communication with the Meeting Server API. You need
to sync the nodes but you do not need to restart, just wait for 30
seconds or so and refresh your page.
allow(".*", ".*", "http\\:\\/\\/meetings\\.example\\.co\\.uk\\/.*");
allow(".*", ".*", "https\\:\\/\\/meetings\\.example\\.ac\\.uk\\/.*");
- Synchronize the nodes, wait one minute and then refresh
the web page.