Moving QueueMetrics to a different server
This chapter explains the required steps in order to move a working QueueMetrics to a different server.
Prerequisites
-
Stop qloader on the Asterisk server
-
Make a backup of the current QM database
-
Make sure the clocks of all servers involved are aligned to a sub-second difference (use NTP)
Required steps
The following steps must be followed:
-
Install a barebone QM - same version- on the new server
-
Move the database from the old server to the new one (overwrite the existing database)
-
Move the files web.xml, tpf.properties and configuration.properties to the new server (make sure you use the correct path on each server - you can find this on the License page)
-
Edit the file /etc/sysconfig/qloaderd so that you can upload data to the new server. You will likely be adding grants on the new server’s MySQl so that a user from the Asterisk box can connect
-
Restart qloaderd and make sure it is uploading data to the new server. You can see if this works from the DBTEST → Live DB inspector. When there is a new line on the queue_log, you should also see it in the database, after 1-2 seconds
-
Edit the configuration.properties file to make sure that the AMI connection strings (those properties that contain strings like with "tcp:…") point to your Asterisk server. You will probably have to edit Asterisk (/etc/asterisk/manager.conf) to allow AMI connections from a new server. You can test if this works from DBTEST → AMI Tester
-
If you use audio recordings, make sure that you can access them from the new server (you may have to use a network mount on the Asterisk server, and edit the path in configuration.properties)