Table of Contents |
---|
After you activate the license, start WCS using the command:
...
If the server process is running and logs have no error, this means the WCS server is ready to work and you can start testing it.
Two ways to start WCS
Starting the server is performed with this command:
Code Block | ||||
---|---|---|---|---|
| ||||
service webcallserver start |
Besides, you can start the server using:
Code Block | ||||
---|---|---|---|---|
| ||||
cd /usr/local/FlashphonerWebCallServer/bin
./webcallserver start |
Environment variables and parameters of the start are set in the setenv.sh script. In this script you can se additional parameters for WCS Core and WCS Manager. Also, here you can set the parameter that prevent memory leaks on multi-CPU systems:
Code Block | ||||
---|---|---|---|---|
| ||||
MALLOC_ARENA_MAX=4 |
Technically, starting goes as follows: first, the WCS Manager process starts, then that process launches the child process, WCS Core.
Starting with stdout output
In some cases, for example, if the server won't start and does not produce any errors, you may need to start the server with direct logging to the 'stdout' console. Direct output to stdout cannot be used in production, because the server will be stopped if the console is closed or the SSH connection is lost. That is why we recommend using stdout output only for debug purposes.
To start the server in this mode, use the following command:
Code Block | ||||
---|---|---|---|---|
| ||||
cd /usr/local/FlashphonerWebCallServer/bin
./webcallserver start standalone |
In this case, logs of the root process, WCS Manager, are printed directly to the console, and the server will be stopped if you press Ctrl+C.
To configure output of logs of the child process, WCS Core, use the node.enable_stdout=true setting.
JVM parameters
Parameters are set in the setenv.sh file.
Here yoiu can add any specific startparameters using the following varaibles:
WCS_JAVA_OPTS - the list of options for WCS Core
WCS_MANAGER_OPTS - the list of options for WCS Manager
Even though, one process is a parent of the other one, these processes are completely independent, and options set for the parent do not influence the child process. For example, if both for the parent and the child processes the -Xmx512M option is set, each of the processes will be executed isolated and have 512 megabytes of heap memory.