MENU
Groupware that integrates business chat, web conferencing, schedules, document management, workflow, and attendance | Chat&Messenger for web conferencing
  1. Home
  2. How to use
  3. On-premise CAMServer
  4. CAMServer Redundancy and load balancing

CAMServer Redundancy and load balancing

On-premise CAMServer
TOC

Redundancy and load balancing

In CAMServer's Ultimate plan,Very easy in on-premise environmentWeb and Video servers can be made redundant and load-balanced.

This allows service to continue even if one server goes down, and also allows large user groups to distribute processing and provide service without degrading performance.

  • Redundant and load balancing configuration supports Windows / Linux.
  • The desktop version for LAN is not subject to redundancy and load balancing.
  • Consider the following guidelines for redundant and load-balanced configurations.
    • Hardware and network resources (CPU load, memory usage, and web conferencing traffic) exceeded the upper limit of 50% after production.
    • Focus on system availability and have a standby system in case server downtime is not tolerated.
    • The number of concurrent Web conferencing conferences cannot be achieved simply by increasing the number of CAMServer nodes. Consideration of network configuration is also necessary to ensure that all conferences are not relayed through the same VPN or center router.

Redundancy and load balancing configuration

Small-start configuration, Load Balancer configuration, and other configurations can be made to best suit your company's requirements and costs.

Small start configuration

Small start 1:.

CAMServer1 uses a highly durable Disk with RAID configuration, and DB/File is also referenced from CAMServer2.

Small Start 2:.

DB/Files should be located on external storage with full backup, and both CAMServer1 and CAMServer2 should be in active configuration.

Client

Small start configuration accesses CAMServer The users need to be aware of this, for example, by separating the "standby system" into different departments or by making the standby system a standby system.

Also,Web App Version described below. cam.clusterHosts Automatic failover is possible when a connection is made by detecting the

Web Server

Distributed configuration CAMServer But real-time communication is possible. For example,CAMServer1 The Client is connected to theCAMServer2 Chat and web conferencing are possible with another Client connected to the

Video Server

Load balancing is performed based on the number of active conferences and the number of participating users on each Video server. If the load on the main Video server exceeds a certain level, it is distributed to the Next node sequentially.

Storage

The DB and attached files are placed on a shared disk such as a NAS. This is described below. cam.serverDatePath The settings can be configured in the

Load Balancer Configuration

Load Balancer

CAMServer front end. Load Balancer Load balancing is also possible by deploying In this case, session affinity should be used to prioritize the load balancing algorithm, and accesses from the same Client should be allocated to the same node.

Redundancy and load balancing settings

Settings common to each distributed server

To make the CAMServer redundant and load-balanced, install a CAMServer on each of the distributed servers,CAMServer/cam.ini Add the following entry to the file

cam.clusterHosts=camserver1;camserver2
cam.clusterHostsDesc=camserver1 is the main server and camserver2 is the standby server.
cam.serverDatePath=\\disk\CAMServer\data
cam.enabledSingleProcessingHost=camserver1

cam.clusterHosts

cam.clusterHosts is the hostname of each of the distributed servers. ; The hostname is delimited and enumerated with Host names are listed from the client side using the https://ホスト名/ The user must be able to access the site via the

Set the following for active-standby and active-active configurations.

  • In active and standby configurations, all CAMServers will have the active side's hostname first. 
    cam.clusterHosts=camserver1;camserver2
  • If you have separate CAMServers for each department in an active-active configuration, you can use each CAMServer with its own hostname at the top of the list. 
    CAMServer1
cam.clusterHosts=camserver1;camserver2

CAMServer2
cam.clusterHosts=camserver2;camserver1
The enumeration order is affected when selecting the initial connection server and Video server at startup.

cam.clusterHostsDesc

cam.clusterHostsDesc can change the comments in the description field of the distributed server.

cam.serverDatePath

cam.serverDatePath specifies the DB, the location where uploaded attachments are stored. specifies a shared disk, such as a NAS, that can be accessed from distributed servers.
If there is no shared disk, a sub CAMServer can be used as the main CAMServer's CAMServer/config Storage can also be shared by specifying a folder.

cam.enabledSingleProcessingHost

cam.enabledSingleProcessingHost should be the hostname of the first server enumerated in cam.clusterHosts. For processes that can only run on a single host, such as batch processing, set this parameter to determine whether the host is defined in cam.enabledSingleProcessingHost before executing the process.

Set only sub servers

cam.disableLANNetwork=true The second and subsequent sub- CAMServers should be configured to do this.

cam.disableLANNetwork=true

On-premise CAMServer
TOC