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: service webcallserver start
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.
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.
Parameters are set in the setenv.sh file.