Frequently Asked Questions | Oct 7, 2024 - 06:34pm |
|
|
Frequently Asked Questions Operational Questions Chat
Chat in a Distributed Server Environment
Rate This FAQ
(Not yet rated)
|
Created On: 1 Feb 2001 8:42 am Last Edited: 10 Jun 2009 2:43 pm |
Question |
|
|
Setting up chat when operating in a distributed server environment (master/slave mode) is not immediately obvious. |
Answer |
This requires the use of fanout servers. Your Sysop Documentation for Chat, as well as your "Guide" provides details on fanout servers. For this setup, you do not need to install seperate fanout servers (your slave(s) operate as fanouts), but if additional fanouts are needed, the instructions remain the same.
Each master and slave has its own chat settings, these settings are not shared. So setting up common chat area for a master and multiple slaves is just like setting up a shared chat environment for multiple separate web crossing servers.
There must be exactly one control room. There can be any number of webx conference servers talking to the control room, and there can be any number of fanout servers that actually connect to the client chat applets.
The control room can be in either the master or any slave, or can be a totally separate chat-only server.
To configure so that the master is the control room and a fanout server, and the slave is just a webx conference connected to the control room, do the following:
- On the master
- click on the chat services link.
- click on the detailed chat services link in the first paragraph (if not already in detailed mode)
- enter the master's ip as the control room ip
- in the "This server" section, enter the master's IP address, and check the box to provide chat services from this webx server
- in the "Control room" section, check the box that this server is the control room, and enter the ip address of the slave in the "List of other Web Crossing server IP addresses". You can leave the fanout IPs blank, since the fanout will also be the master
- in the Fanout section, check that this server is a fanout server. Make sure that the max number of client connections is a reasonable number, like 512.
- click the "set chat services" button and make sure the master is serving chat rooms. Also on the Master you need to set a full URL to the Java Chat Client instead of the standard /Images/WBChat it could be: http://domain.for.the.master/Images/WBChat
- On the slave(s)
- click on the chat services link
- click on the detailed chat services link in the first paragraph (if not already in detailed mode)
- enter the master's ip as the control room ip
- in the "This server" section, enter the slave's IP address, and check the box to provide chat services from this webx server
- in the "Control room" section, do not check the button to make this a control room
- in the "Fanout" section, do not check the button to make this a fanout serve
- click the "set chat services" button and make sure the slave is serving chat rooms with the same users as the master.
|
|
|
|
|