# Configuration
The configuration file for TrueConf Calendar Connector is located at:
Windows:
C:/Program Files/TrueConf/Calendar/config.jsonLinux:
/opt/trueconf/calendar/etc/calendar/config.json
Please note that TrueConf Calendar Connector can work with multiple Exchange servers, only if they are united into a single cluster. You can learn more about clustering in the official Microsoft documentation (opens new window).
# Configuration of database and network port
{
"wsPort": 4315,
"dbConnectionConfig": {
"host": "localhost",
"port": 5441,
"user": "bridge",
"password": "", // by default, there is no password for database access, but if a password is set, you need to specify the encrypted password previously created for the impersonation account here
"database": "calendar"
},
"wsPort"– the port for the operation of the WebSocket server. This section should be edited, if a different port was selected during installation."dbConnectionConfig"– this section is needed for configuring connection with the database. The parameters in this section are automatically generated during installation and MUST NOT be changed manually.
# Conference settings
"launchConference": true,
"syncConferenceParticipants": true,
"showCancelledEventsMode": true,
"cache": {
"autoSync": false,
"backward": 2,
"forward": 3
}
"launchConference"– this parameter is responsible for the automatic start of a conference. TrueConf Calendar Connector sends a request to TrueConf Server when an event starts in Microsoft Exchange"syncConferenceParticipants"manages the synchronization of the participant list. If set totrue, the calendar will synchronize conference participants before the start and whenever there is a change in the participant list of the conference. If the parameter isfalse, there will be no participant synchronization (prior to version TrueConf Calendar Connector 2.0, this parameter was called"temporalConfParticipantsMode")."showCancelledEventsMode" is responsible for displaying canceled events in the user's personal area. If set to
true, canceled events will appear in the list (available only for version TrueConf Calendar Connector 2.0+);"cache"– the section where automatic synchronization settings can be configured:"autoSync"– if set totrue, calendar events will be fully synchronized. If set tofalse, the events created previously will not be displayed or synchronized within the selected time period."backward"– the number of months back from the current date for which recurring events should be displayed"forward"– the number of months ahead of the current date for which recurring events should be displayed.
# Configuration of access to TrueConf Server
"productWhitelist": {
"tcs": ["server.trueconf.name#vcs"]
}
"server.trueconf.name#vcs"- it is necessary to specify the domain name of TrueConf Server that will have access to TrueConf Calendar Connector.
# Configuration of access to Microsoft Exchange
On the Microsoft Exchange side, you need to pre-create impersonation accounts permitted to view calendars "on behalf of" other users.
"calendarProviders": [
{
"host": "exchange.example.com",
"path": "/EWS/Exchange.asmx",
"autodiscoverPath": "/autodiscover/autodiscover.svc",
"port": 443,
"type": "ews",
"credentials": [
{
"login": "test",
"password": "encrypted_password"
}
],
"users": [
"name1@example.com",
"name2@example.com",
"name3@example.com"
]
}
]
}
"calendarProviders"- the section where one can configure the settings for external calendar synchronization services"host"- the domain of the Microsoft Exchange server"path"- the path for accessing the EWS API (default path is specified)"autodiscoverPath"is a required parameter used for working with an Exchange server cluster. It contains the path to the autodiscover file (opens new window), namely"host"/"autodiscoverPath". You need to specify it even if you have only one Exchange server. There is no need to change this parameter; just leave it as is."port"- the default port for connecting to EWS"type"- the name of the external service (only Microsoft Exchange is supported)"credentials"- the section where one has to specify the credentials for the impersonation account on the Exchange server"login"- the impersonation account login on the Microsoft Exchange server;"password"- the encrypted account password. It is generated in the terminal.
"users"- an array of users' email addresses. The calendars of these users need to be forcibly synchronized when the tc_calendar service starts.