When you deploy an IBM
® Proxy Server and a Sametime
Meeting Server on the same machine using the same server host name, conflicts with cookies that are used by each server can occur. If you install both servers on the same machine, then configure the Sametime
Proxy Server with a host alias as a different host name.
About this task
If you deploy the Sametime
Proxy Server and the Sametime
Meeting Server on one machine, and both servers have the same host name, users cannot stay connected to instant meetings initiated by the Sametime
Proxy web client. Users can start instant meetings, but eventually they are disconnected. This error occurs because Websphere sets the JSESSIONID cookie whenever an application is started, and the JSESSIONID cookie is being overwritten because the Sametime
Proxy Server and the Sametime
Meeting Server share a hostname. Due to the matching host names, the WebSphere
® JSESSIONID is not recognizing them as separate applications. You can work around this by providing the Sametime
Proxy Server with a host alias with a hostname different from the Sametime
Meeting Server host name.
An example of a host alias is stproxy
. For more information on host alias settings, see "Host alias settings" in the WebSphere
Application Server information center:
Parent topic: Installing a Sametime Meeting Server
Previous topic: Clustering Sametime Meeting Servers
Next topic: Preparing the Sametime Meeting server for users
Configuring Sametime servers to support browser-based audio-visual conferencing
- Install the Sametime Meeting Server and the Sametime Proxy Server on the same computer.
- Change the host name of the Sametime Proxy Server using a host alias:
- Log in to the Integrated Solutions Console on the Sametime Proxy Server.
- Click Environment -> Virtual Hosts -> default_host -> Host Aliases.
- Configure the host aliases of the Virtual Host, default_host, of the Sametime Proxy Server so that their host names do not match either the host name of the Sametime Meeting Server or the wild card character, '*' (asterisk).
The new host name alias must refer to the IP address at the DNS level, so that the machines will be able to ping the Web server by using the host name. Update the host name of all of the host alias entries to the host name that the Sametime
Proxy Server or Sametime
Meeting Server will use. Use the same host name for all aliases.
- Click the host name link associated with each port.
- Enter the fully qualified host name for the Sametime Proxy Server. It must not be the same host name assigned to the Sametime Meeting Server.
- Click Apply, and then click Save.
- Restart the Sametime Proxy Server.
- Change the host name for all Sametime Proxy Server nodes in the cell.
- On the deployment manager, log in to the Integrated Solutions Console.
- Click Servers -> Server Types -> WebSphere application servers.
- Click StProxyServer to open the Proxy Server configuration page.
- Under Communications, click Ports.
- Change all proxy host names to the new host name you specified in the previous step.
- Click System administration -> Nodes.
- Select the Proxy Server node and click Full Resynchronize.
- Restart the Proxy Server.
- Update the Meeting Server configuration to use the Proxy Server’s new host name in the URL you entered for the meetingroomcenter.stProxyAddress configuration key.
- If you deployed the Sametime Web audio-visual plugin, update the URL with the new host name.
- Log in to the Sametime System Console.
- Click Sametime System Console -> Sametime Servers -> Sametime Proxy Servers.
- In the Proxy Servers list, click the server with the configuration that you want to change.
- Specify the URL with the new host name where the plugin will be hosted.