Verifying a Sametime Meeting Server cluster

IBM® Sametime® Meeting Server clusters consist of a minimum of two Sametime Meeting Servers and one or more WebSphere® Proxy Servers and are typically fronted by an intelligent load balancer.

About this task

Use this procedure to check through the configuration and validate that each component in the system is functioning.

Procedure

Validate each Meeting Server in the meeting cluster by accessing the server directly with HTTP using the WC_defaulthost port.
1. From a web browser, navigate to the Meeting Room Center by entering this URL:
  http://serverhostname.domain.com:port/stmeetings
2. Replace serverhostname.domain.com with your meeting room server name.
3. Replace port with the port defined in the WC_defaulthost field.
  For example, enter http://meetingserver1.domain.com:9080/stmeetings
4. Repeat steps 1a through 1c for each Meeting Server in the meeting cluster.
Validate each WebSphere Proxy Server in the Meeting Server cluster by accessing the server directly using the Proxy_http_address port:
1. From a web browser, navigate to the Meeting Room Center by entering this URL: http://serverhostname.domain.com:port/stmeetings
2. Replace serverhostname.domain.com with your WebSphere Proxy Server name.
3. Replace port with the port defined in the Proxy_http_address field.
  Note: It is not necessary to specify the port if using standard http / https ports 80 or 443.
  For example, http://proxyserver1.domain.com/stmeetings
4. Repeat steps 2a through 2c for each WebSphere Proxy Server used with the Meeting Server cluster.
Validate the cluster using the Meeting Server load balancer and port. Complete these steps:
1. From a web browser, navigate to the Meeting Room Center by entering this URL: http://meetingloadbalancer.domain.com:port/stmeetings
2. Replace port with the configured ports on the load balancer.
  Note: Note: It is not necessary to specify the port if you are using standard http / https ports 80 or 443.
Confirm that each individual server in the cluster is functioning correctly by completing these steps:
1. Stop all Meeting Servers and WebSphere Proxy Servers used with the Meeting Server cluster.
2. Start the first WebSphere Proxy Server and the first Meeting Server in the cluster.
3. From a web browser, navigate to the Meeting Room Center.
  1. If you are using a load balancer, the URL will is http://meetingloadbalancer.domain.com:port/stmeetings.
  2. If you are using a single WebSphere Proxy Server to front the cluster, the URL is http://proxyserver1.domain.com:port/stmeetings
4. Ensure the Meeting Server is functioning correctly by completing these steps:
  1. Log in to Sametime Meetings.
  2. Create a room if one is not available.
  3. Join a room and test the meeting functions.
When the first Meeting Room is functioning correctly, you can continue to the secondary nodes by completing these steps:
1. Start the second Meeting Server.
2. When the second Meeting Server is running, stop the first Meeting Server. The first WebSphere Proxy Server is still running. You are now using the second Meeting Server.
3. From a web browser, navigate to the Meeting Room Center as follows:
  1. If you are using a load balancer, the URL is http://meetingloadbalancer.domain.com:port/stmeetings
  2. If you are using a single WebSphere Proxy Server to front your cluster, the URL is http://proxyserver1.domain.com:port/stmeetings
4. Ensure the Meeting Server is functioning correctly by completing these steps:
  1. Log in to Sametime Meetings.
  2. Create a room if one is not available.
  3. Join a room and test the meeting functions.
If there are additional Meeting Servers in the cluster, continue with the above process until all Meeting Servers in the cluster have been tested while the first WebSphere Proxy Server is running.
Repeat the above process using the second WebSphere Proxy Server (assuming the WebSphere Proxy Servers are used in your configuration).
1. Stop all Meeting Servers and WebSphere Proxy Servers used with the Meeting Server cluster.
2. Start the second WebSphere Proxy Server and the first Meeting Server in the cluster.
3. From a web browser, navigate to the Meeting Room Center as follows:
  1. If you are using a load balancer, the URL is http://meetingloadbalancer.domain.com:port/stmeetings
4. Ensure the Meeting Server is functioning correctly by completing these steps:
  1. Log in to the Sametime Meetings.
  2. Join a room and test the meeting functions.
5. Start the second Meeting Server.
6. When the second Meeting Server is running, stop the first Meeting Server. The second WebSphere Proxy Server is still running. You are now using the second Meeting Server.
7. Ensure the second Meeting Server is functioning correctly.
8. If there are additional Meeting Servers, continue with the above process until all Meeting Servers in the cluster have been tested while the second WebSphere Proxy Server is running.
Repeat the process until each WebSphere Proxy Server and each Meeting Server have been tested.
Verify routing from multiple WebSphere Proxy Servers (if WebSphere Proxy Servers are used in your configuration).
1. Start all Meeting Servers and WebSphere Proxy Servers used with the Meeting Server cluster.
2. Have one test user connect to a particular meeting room via the first WebSphere Proxy Server http://proxyserver1.domain.com:port/stmeetings
3. Have a second test user connect to the same meeting room via the second WebSphere Proxy Server http://proxyserver2.domain.com:port/stmeetings
4. Navigate to the same meeting room via the two WebSphere Proxy Servers and validate the meeting functions.
With individual server validation complete, continue with functional meeting testing with all servers running in the cluster. Be aware that when servers are clustered, multiple users are only guaranteed to access the same meeting room if they are routed via the WebSphere Proxy Server.