The configuration file is:
$PLATFORM_TOMCAT_HOME/gatein/conf/chat.properties for Tomcat.
$PLATFORM_JBOSS_HOME/standalone/configuration/gatein/chat.properties for JBoss.
You were asked to create the file and edit the
chatPassPhrase property for security during the setup,
so the property is not repeated here.
|mongo||You should always use the default value. The other value, embed, is used for unit testing.|
|localhost||The host name or IP of MongoDB.|
|27017||The port number to connect to MongoDB host.|
|chat||Name of the Mongo database name.|
|false||Set it true if authentication is required to access MongoDB.|
|EMPTY||Provide the username to access the database if authentication needed.|
|EMPTY||Provide the password to access the database if authentication needed.|
Generally, you do not need to configure those unless you have secured your MongoDB. See details about connecting to secured MongoDB in Secured MongoDB.
|0 0/60 * * * ?||
The notifications are cleaned up every one hour by default. To learn the syntax of Cron expression, see Scheduled synchronization, Administrator guide.
The eXo group who can create teams.
When a user reads a chat, the application displays messages of some days in the past.
The number of messages that you can get in the Chat room.
Time interval to refresh messages in a chat.
Time interval to keep a chat session alive in milliseconds.
Time interval to refresh user status in milliseconds.
Time interval to refresh Notifications in the main menu in milliseconds.
Time interval to refresh Users list in milliseconds.
Time after which a token will be invalid. A user will then be considered offline.