...
- bin - WCS executables
- client - WCS JavaScript API 1.0, usage examples and stress-tests
- client2 - WCS JavaScript API 2.0 and usage examples
- conf - configuration files
- lib - required libraries
- tools - tools to debug WCS
- web - WCS web interface static pages
Silent mode installation
Sometimes, WCS can be installed in silent mode if automatic deployment system like Ansible is used to deploy a number of typical instances
Code Block |
---|
|
./install.sh -silent |
In this case:
- IP addresses detection does not work (flashphoner.properties file and other settings are supposed to be overwritten by automatic deployment system)
- webcallserver.service is configured to start from root
Installation to a different Java versions
JDK 12 or 14
The following settings should be removed from wcs-core.properties file
Code Block |
---|
|
-XX:+UseConcMarkSweepGC
-XX:+PrintGCDateStamps
-XX:+PrintGCDetails |
The following setting
Code Block |
---|
|
-Xloggc:/usr/local/FlashphonerWebCallServer/logs/gc-core- |
should be replaced by
Code Block |
---|
|
-Xlog:gc*:/usr/local/FlashphonerWebCallServer/logs/gc-core-:time |
JDK 15
In addition to setting changes made for JDK 12 or 14, the following settings should be removed from wcs-core.properties file
Code Block |
---|
|
-XX:+UseCMSInitiatingOccupancyOnly
-XX:CMSInitiatingOccupancyFraction=70 |
JDK 16
In addition to setting changes made for JDK 12, 14, 15, the following settings should be added to wcs-core.properties file
Code Block |
---|
|
--illegal-access=permit |
JDK 17
In addition to setting changes made for JDK 12, 14, 15, 16, the following settings should be removed from wcs-core.properties file
Code Block |
---|
|
--illegal-access=permit |
and the following settings should be added
Code Block |
---|
|
--add-exports java.base/sun.security.provider=ALL-UNNAMED
--add-opens java.base/java.lang=ALL-UNNAMED |
Acquiring a license and activation
...
For example, a test server on Amazon EC2 has the external IP address of: 54.189.212.111, and the network interface address is: 172.30.21.25. If your server is behind NAT in regard to browser clients, write down or copy these IP addresses. You will need them later, when you will configure the server.
Automatic and semi-automatic IP addresses detection
Since build 5.2.921, WCS tries to automatically detect server IP addressess on startup if they are not set, or server is starting in cloud environment supporting AWS API or Google Cloud API endpoints. If IP addresses cannot be detected on startup, it may be done manually using the following command
Code Block |
---|
|
cd /usr/local/FlashphonerWebCallServer/bin
sudo ./webcallserver set-ip |
This command:
- tries to detect IP addresses automatically;
- if this cannot be done, asks user for additional data
- writes results to flashphoner.properties file
It is recommended to use this command if there are some problems with IP addresses detection behind NAT.