Settings file wcs-manager.properties
Main manager options are in /usr/local/FlashphonerWebCallServer/conf/wcs-manager.properties file.
JDBC URL of the database
Class of the database driver
SQL dialect used
Should the required tables be created in the database upon the first run
create - create tables
validate - do not create tables, validate integrity
update - do not create tables, update the scheme
Automatically create and fill the database upon start:
create - create
validate - do not create, validate integrity
update - do not create, update the scheme
create-drop - create, drop tables in the end of the session
Table naming strategy in the database
Database dialect used
Show SQL queries to the database.
The HTTP port, WCS Manager will respond to incoming HTTP requests to.
SSL certificate store
Password to the SSL certificate store
dev - if this profile is enabled, WCS Manager will listen for HTTP port and will not require authentication.
production - if this profile is enabled, WCS Manager will listen for HTTPS port and will require Basic-authentication from incoming HTTPS connections.
The profile can be redefined upon server startup as well as other settings. See the Startup options section.
Local WCS Core port WCS Manager will connect using the RMI interface to for data exchange.
Name under which WCS Core is registered in the RMI register
Host the RMI request is addressed to.
Accept self-signed certificated from the Web server when accessing the Web server via HTTPS/REST.
Filters out unnecessary commands
Show the banner
Enable logging of WCS Server to logs/server_stdout.log. /Can be used for debugging.
Sets interval for the garbage collector for the RMI client, in milliseconds. This setting allows you to turn off forced execution of the garbage collector to increase performance of the server
Sets interval for the garbage collector for the RMI server, in milliseconds. This setting allows you to turn off forced execution of the garbage collector to increase performance of the server
Record stream statistics to the database
Session timeout, in minutes
Location and prefix of the log file of the garbage collector. The name is constructed as /usr/local/FlashphonerWebCallServer/logs/gc-manager-YYYY-MM-DD_HH-MM.log
|Port number to redirect REST API queries from server.port
|Port number to redirect REST API queries from manager.https_port
Settings file log4j.properties
This file defines logging settings for WCS Manager. By default, logs of WCS Manager are recorded to flashphoner_manager.log. See the Logging section for advanced settings and logging control.
This file is packed into wcs_manager-1.0.jar file. Use Midnight Commander to change settings - just 'enter' into wcs_manager-1.0.jar file, open log4j.properties file, edit and save changes. Restart WCS for changes to take effect.
Configuring WCS Manager database
Creating a database
By default, WCS Manager uses the embedded H2 database that is created and filled up upon first startup of the WCS server.
Database files are created in the home directory of the WCS server in the 'database' directory.
If the database file does not exist, an attempt to create the database afresh will be made.
If the database file already exists, WCS Manager simply connects to this database.
Filling up the database
The base is filled up with default values (users, groups, applications etc.) only if there is no a super-group record.
In all other cases the contents of the database remain intact.
Migrating to MySQL
MySQL installation and setup
Install MySQL (on CentOS 7 example) with command
Launch MySQL and set root password
Log in to MySQL as root
Create database and user, grant to the user privileges to the database
Add the following strings to wcs-manager.properties file
- 'wcs_db' is the database name
- 'webcallserver' and 'password' is user name and password
Restart WCS server
Upon first startup of WCS, set spring.datasource.ddlMode=create in wcs-manager.properties. In this case all required tables will be created automatically. Upon a subsequent run, switch this setting to spring.datasource.ddlMode=validate. As a result connection to the existing database is performed without creating tables.
Data import from H2 to MySQL
Migrating from H2 to MySQL, data exported from H2 database can be imported to MySQL database::
a) using SQL script
b) loading data to tables from CSV files:
stop WCS server
log in to MySQL
load data from CSV file to existing table, e.g.,
However, SQL script and CSV files generated by H2 are not fully compatible with MySQL and would have to be changed for importing. E.g., for table STREAM_INFO_3 it would be required to change Boolean values.