-
Notifications
You must be signed in to change notification settings - Fork 57
Configuration
eXo Chat can be configured with properties file or system properties.
2 possible services implementations : mongo or jcr (jcr implementation is available as demo mode only, it can't be used in Production)
Default value : mongo
Weemo gives access to Video conferencing and screen sharing features. A key is needed. If empty, Video conferencing is deactivated.
Default value : EMPTY
If using MongoDB, you can set mongo db or an embed
Default value : mongo
Host of DB server.
Default value : localhost
Port of DB server.
Default value : 27017
Name of the Chat database in Mongo
Default value : chat
Is authentication needed?
Default value : false
If authentication, database username
Default value : EMPTY
If authentication, database password
Default value : EMPTY
Base URL of the Chat Server. Chat server can run on a dedicated server. Base URL must use a format like : http://127.0.0.1:8080
If empty, eXo Chat will use the Client server as the Chat Server BaseURL. Thus, this automatic mode won't run with a Two-Servers installation.
Default value : EMPTY
URL to access Chat Server
Default value : /chatServer
Page where is installed eXo Chat
Default value : /portal/intranet/chat
Cron job value to clean read notifications
Default value : 0 0/60 * * * ?
eXo group who will answer to Public discussions
Default value : /platform/administrators
eXo group who can create Teams
Default value : /platform/administrators
Secret passphrase to access Rest services
Default value : chat
Public mode allows to have unauthenticated discussions in the Chat with a Support team
Default value : false
When getting message from a room. How many days in the past should we go.
Default value : 30
How many messages can we get in the Chat room?
Default value : 200
How many messages can we export in the Chat room?
Default value : 2000
Interval to refresh Chat messages in milliseconds
Default value : 3000
Interval to keep Chat session alive in milliseconds
Default value : 60000
Interval to refresh User status in milliseconds
Default value : 15000
Interval to refresh Notifications in the main menu in milliseconds
Default value : 3000
Interval to refresh Users list in milliseconds
Default value : 5000
Time after which a token won't be valid. A use will then be considered offline
Default value : 25000
For report support in Meeting notes, Host of the SMTP Mail Server.
Default value : smtp.gmail.com
Port of SMTP Mail Server
Default value : 587
User used for SMTP Authentication
Default value : exo
Password used for SMTP Authentication
Default value : EMPTY
you can copy a chat.properties file into tomcat/conf/. Each property will override default values. Example :
servicesImplementation=mongo
weemoKey=---
dbServerType=mongo
dbServerHost=127.0.0.1
dbServerPort=27017
dbName=chat
dbAuthentication=false
dbUser=admin
dbPassword=pass
chatServerBase=localhost
chatServerUrl=/chatServer
chatPortalPage=/portal/intranet/chat
chatIntervalNotif=3000
chatIntervalChat=3000
chatIntervalSession=60000
chatIntervalStatus=15000
chatIntervalUsers=5000
chatPassPhrase=chat
chatCronNotifCleanup=0 0/60 * * * ?
publicMode=false
publicAdminGroup=/platform/administrators
teamAdminGroup=/platform/users
chatTokenValidity=25000
chatReadDays=30
chatReadTotalJson=200
chatReadTotalTxt=2000
mailHost=smtp.gmail.com
mailPort=587
mailUser=exo
mailPassword=---
You can also use System properties when starting tomcat. In this case, you will use a prefix "chat.".
To override the DB name for example you can use : -Dchat.dbName=chatProd