Skip to main content
Skip table of contents

Mre Configurations

Following is the procedure to configure Mre:

  1. Stop EF_Mre service in Windows Services pane
  2. Navigate to <installation-dir>\hybrid-chat\core\mre 
  3. Open mre.jar with WinRar
  4. Navigate to Config  directory in mre.jar and open config.properties file with any text editor
  5. Save config.properties file after configuration changes and update it in mre.jar 
  6. Start EF_Mre service in Windows Services pane
  7. Mre logs are generated at /EFLogs/chat-solution/mre/ directory

Configuration

Sample config.properties file is as following:

config.properties

JAVA
#------------- ActiveMQ Properties ---------------#
ActiveMq_URL_1=localhost:61617
ActiveMq_URL_2=localhost:61617
AMQ_CONSUMER_PRIORITY=100
ActiveMq_Timeout=10000
Priority_Backup=false
Randomize=false
PrefetchSize=20000
#-----------------General Properties----------------------#
IS_STANDALONE=false
UMM_PATH=https://localhost:8443
USER_TYPE=CC
IS_UMM_CERT_SELF_SIGNED=true
UMM_USER=admin
UMM_PSWD=admiN123!
ENABLE_REPORTING=true
#---------------- SSL Properties ----------------#
SSL=true
KEYSTORE_PATH=../certs/client.ks
TRUSTSTORE_PATH=../certs/client.ts
KEYSTORE_PWD=password
TRUSTSTORE_PWD=password
#-----------Apache Kafka-----------#
# For detailed information of used params, please visit https://kafka.apache.org/documentation.html#producerconfigs
KAFKA_ENABLED=false
# Apache Kafka server url
KAFKA_SERVER_URL=localhost:9092
# Topic name
KAFKA_TOPIC=database-connector
# Acknowledgements, DO NOT CHANGE unless kafka is deployed in a cluster and you need to change cluster configs
ACKS=all
# Number of retries to carry out for sending a message
RETRIES=10
# Batch Size, DO NOT CHANGE
BATCH_SIZE=16384
# Linger time, milliseconds, DO NOT CHANGE
LINGER_MS=1
# Buffer Memory, DO NOT CHANGE
BUFFER_MEMORY=33554432
#---------------- Jetty Server Properties --------------------#
API_PORT=8097
API_PORT_HTTPS=8095
JKS_KEYSTORE_PATH=../certs/keystore.jks
JKS_KEY_STORE_PSWD=password
JKS_KEY_MANAGER_PSWD=password
CORS=*
#---------------- Database Connector Properties --------------#
DB_CONNECTOR_API_PATH=https://localhost:8450
#---------------- MRE Microservice Properties -----------------#
MRE_MICROSERVICE_PATH=https://localhost:8447
SYNC_WITH_MRE_MICROSERVICE=true

REPORTING_CONNECTOR_API_PATH=https://localhost:8442
REPORTING_DURATION=90000
# Possible values
# 0 - Task will be queued, it will not be routed to last agent / preffered agent
# 1 - Task will not be queued and system will try to route that task to last / preferred agent. Task will be queued if last / preferred agent is not available
# 2 - Task will be queued even if preferred agent is available. Upon task's turn in queue, task will be assigned to preferred agent if available, otherwise it will be assigned to any available agent.
PREFERRED_ROUTING=0

These parameters are explained in following table:


Configuration VariableDefault ValueExpected ValueLimitationsDescription
1ActiveMq_URL_1localhost:61617String
Primary ActiveMQ path
2ActiveMq_URL_2localhost:61617String
Secondary ActiveMQ path
3ActiveMq_Timeout10000Number
ActiveMQ connection timeout
4Priority_BackupfalseBoolean true / false 
ActiveMQ failover configuration
5RandomizefalseBoolean true / false 
ActiveMQ failover configuration
6PrefetchSize20000Number
ActiveMQ message prefetch size, do not change
7IS_STANDALONEtrueBoolean true onlyNot used anymore, do not change. Mre will not work if set to false . USER_TYPE variable is used instead.
8UMM_PATHhttps://localhost:8443String
UMM REST endpoint path
9USER_TYPECCString

UMM user type:

  • CC: Finesse Agents
  • DB: UMM Agents
10IS_UMM_CERT_SELF_SIGNEDtrueBoolean true / false 
Set it to true if UMM is hosted via self signed certificates
11UMM_USERadminString
UMM username for authorization
12UMM_PSWDadmiN123!String
UMM password for authorization
13ENABLE_REPORTINGfalseBoolean true / false 
Set to true if Reporting Connector is deployed
14SSLtrueBoolean true / false 
Specifies to host Mre API over HTTPS. Set to true for HTTPS, false otherwise.
15KEYSTORE_PATH../certs/client.ksString
ActiveMQ client keystore path
16TRUSTSTORE_PATH../certs/client.tsString
ActiveMQ client truststore path
17KEYSTORE_PWDpasswordString
ActiveMQ client keystore password
18TRUSTSTORE_PWDpasswordString
ActiveMQ client truststore password
19KAFKA_ENABLED

Not used anymore, do not change
20KAFKA_SERVER_URL

Not used anymore, do not change
21KAFKA_TOPIC

Not used anymore, do not change
22ACKS

Not used anymore, do not change
23RETRIES

Not used anymore, do not change
24BATCH_SIZE

Not used anymore, do not change
25LINGER_MS

Not used anymore, do not change
26BUFFER_MEMORY

Not used anymore, do not change
27API_PORT8097Number
HTTP port for Mre hosting
28API_PORT_HTTPS8095NumberApplicable only when SSL is true HTTPS port for Mre hosting
29JKS_KEYSTORE_PATH../certs/keystore.jksStringApplicable only when SSL is true Mre keystore path
30JKS_KEY_STORE_PSWDpasswordStringApplicable only when SSL is true Mre keystore password
31JKS_KEY_MANAGER_PSWDpasswordStringApplicable only when SSL is true Mre key manager password
32CORS*String
Allow CORS
33DB_CONNECTOR_API_PATHhttps://localhost:8450String
Database Connector API path
34MRE_MICROSERVICE_PATHhttps://localhost:8447String
Mre Microservice API path
35SYNC_WITH_MRE_MICROSERVICEtrueBoolean true / false 
Mre will not continue operations until configurations are read from Mre Microservice if set to true , false otherwise
36REPORTING_CONNECTOR_API_PATHhttps://localhost:8442String
Reporting connector API path to fetch Average Chat Handling Time for EWT calculation
37REPORTING_DURATION90000Number
Average Chat Handling Time of last time period specified in seconds
38PREFERRED_ROUTING0Number
# Possible values
# 0 - Task will be queued, it will not be routed to last agent / preffered agent
# 1 - Task will not be queued and system will try to route that task to last / preferred agent. Task will be queued if last / preferred agent is not available
# 2 - Task will be queued even if preferred agent is available. Upon task's turn in queue, task will be assigned to preferred agent if available, otherwise it will be assigned to any available agent.
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.