Deployment and Installation of Desktop Connect Wallboard
Overview
The installation of the wallboard requires a Tomcat installation.
The Tomcat running the DC product using the Wallboard frame can be used
for small-mid sized installations, but since the Wallboard monitors
affect server performance, a separate instance (possibly a separate
VM/host) is recommended for large installations. The Tomcat
running Wallboard must be configured for https.
Read about Tomcat installation in the following article: Desktop Connect for CRM - InstallationGuide
Wallboard Installation Steps
- In order to deploy the application, copy the GeoWallboardDataSource.war file to the Tomcat/webapps folder. Tomcat will auto-deploy the application.
If the Tomcat is not configured to auto-deploy the application, you will have to deploy it manually. A description can be found on this link. Instead of dc4crm, choose the wallboard file to deploy. However, we highly recommend to proceed with the option we provided in step 1. - Follow the configuration steps as described below.
- Restart the server.
See the section below for Wallboard Configuration Details.
Configuration
The Queues Dashboard configuration uses the core services AES configuration.
Please follow the Configuration Guides of the relevant Desktop Connect product in order to have the Queue Dashboard enabled.
WBLog4j Properties
Insert the WBlog4j.properties from the log4j config file to the Tomcat.lib folder.
loggerName=SrvI_1
log4j.rootLogger=DEBUG, SR
log4j.appender.SR=org.apache.log4j.RollingFileAppender
log4j.appender.SR.File=C:/Geomant/Wallboard/Logs/Wallboard.log
log4j.appender.SR.MaxFileSize=10MB
log4j.appender.SR.MaxBackupIndex=2
log4j.appender.SR.layout=org.apache.log4j.PatternLayout
log4j.appender.SR.layout.ConversionPattern=%d [%t] %-5p %c - %m%n
log4j.logger.com.avaya.jtapi=ERROR, SR
log4j.logger.com.avaya.jtapi.tsapi=ERROR, SR
log4j.logger.JtapiServer=LOG, SR
log4j.additivity.JtapiServer=false