🔗 Source article (Salesforce): Click here
This procedure describes how to migrate Unified-Messaging and/or its database to another server.
With 'migration' we understand moving UM and/or its DB to another server.
Make sure the minimal requirements are met: Unified Messaging Minimal Requirements
Typically, your migration can be described as one of the following scenario's:
Should your migration differ from one of these scenario's, contact support@healthconnect.be
Scenario 1: Moving UM from server A to server B, DB stays on server SQL X
On server A:
Open Mybox Interface with any Admin-role (e.g. http://localhost:8080) and go to Settings. Copy to Notepad the value of your License-ID:
run services.msc and check properties of unified-messaging. Note the directory of 'path to executable' (e.g."C:\Program Files\unified-messaging\" (="[location]")
take a backup of [location]\application.properties and license.key
run services.msc and stop the services unified-messaging and unified-admin
open the properties of service unified-messaging and unified-admin and set startup type to 'disabled'
On SQL server X:
take a backup of the DB on which UM connects
you can find the connection string in [location]\application.properties on server A
On server B:
if you connect on the DB using Integrated Security, you need to launch the installer with that user in order to pass the test. If this user is a service user, you need to grant logon/execute rights temporarily.
in the database connection test, fill in the same connection string as written in application.properties on server A. In the port-section, use the same port as before (written in backup of application.properties, field server.port)
when shown the Machine ID, copy it to Notepad:
Initiate a Live Chat via https://support.corilus.be/healthconnect/ with LicenseID and MachineID, mentioning 'License Migration Unified Messaging' Do not proceed until you receive confirmation of your licence migration from Healthconnect Support
After receiving confirmation of License Migration from Support, proceed with the installer and finish it. Wait 5-10 minutes for Unified-Messaging to start.
if you connect on the DB using Integrated Security, run services.msc and change logon user for unified-messaging to correct user. Restart unified-messaging. Wait 5-10 minutes for Unified-Messaging to start.
test interface: http://localhost:8080
Important: If you connect to Healthdata (HD4DP), inform them that Unified-Messaging has moved and that the location is http://[hostname:port]
Important: if you use any of the webservices of UM (ConsultRN, Insurability, Helena Publication, Healthpages, Recipe, ...), make sure to adapt the endpoints to new host
Important: if your file interface configuration (e.g. for sending-receiving protocols) pointed to local disks (e.g.c:\), then you need to point your application to the local disk of the new host, or alternatively change the configuration in Unified Messaging Settings.
Scenario 2: Moving UM from server A to server B, moving DB from server SQL X to server SQL Y
On server A:
Open Mybox Interface with any Admin-role (e.g. http://localhost:8080) and go to Settings. Copy to Notepad the value of your License-ID:
run services.msc and check properties of unified-messaging. Note the directory of 'path to executable' (e.g."C:\Program Files\unified-messaging\" (further mentioned as "[location]")
take a backup of [location]\application.properties and license.key
run services.msc and stop the services unified-messaging and unified-admin
open the properties of service unified-messaging and unified-admin and set startup type to 'disabled'
On SQL server X:
take a backup of the DB on which UM connects
you can find the connection string in c:\Program Files\Unified-Messaging\application.properties on server A
On SQL server Y:
import backup of DB
make sure to migrate/recreate the user also, and that it is still DBOwner
On server B:
if you connect on the DB using Integrated Security, you need to launch the installer with that user in order to pass the test. If this user is a service user, you need to grant logon/execute rights temporarily.
in the database connection test, fill in the connection string pointing to new DB on SQL server Y. In the port-section, use the same port as before (written in backup of application.properties, server.port - typically 8080)
when shown the Machine ID, copy it to Notepad:
Initiate a Live Chat via https://support.corilus.be/healthconnect/ with LicenseID and MachineID, mentioning 'License Migration Unified Messaging' Do not proceed until you receive confirmation of your licence migration from Healthconnect Support
After receiving confirmation of License Migration from Support, proceed with the installer and finish it. Wait 5-10 minutes for Unified-Messaging to start.
if you connect on the DB using Integrated Security, run services.msc and change logon user for unified-messaging to correct user. Restart unified-messaging. Wait 5-10 minutes for Unified-Messaging to start.
test interface: http://localhost:8080
Important: If you connect to Healthdata (HD4DP), inform them that Unified-Messaging has moved and that the location is http://[hostname:port]
Important: if you use any of the webservices of UM (ConsultRN, Insurability, Helena Publication, Healthpages, Recipe, ...), make sure to adapt the endpoints to new host
Important: if your file interface configuration (e.g. for sending-receiving protocols) pointed to local disks (e.g.c:\), then you need to point your application to the local disk of the new host, or alternatively change the configuration in Unified Messaging Settings.
Scenario 3: Moving DB from server SQL-X to server SQL-Y (UM stays on server A)
On server A: run services.msc and stop the services unified-messaging and unified-admin
On SQL server X:
take a backup of the DB on which UM connects
you can find the connection string in c:\Program Files\Unified-Messaging\application.properties on server A
On SQL server Y:
import backup of DB
make sure to migrate/recreate the user also, and that it is still DBOwner
On server A:
if you connect on the DB using Integrated Security, you need to launch the installer with that user in order to pass the test. If this user is a service user, you need to grant logon/execute rights temporarily.
In the database connection test, fill in the connection string pointing to new DB on SQL server Y
If license.key-file is present in the install-directory, proceed with the installer and finish it. Wait 5-10 minutes for Unified-Messaging to start.
if you connect on the DB using Integrated Security, run services.msc and change logon user for unified-messaging to correct user. Restart unified-messaging. Wait 5-10 minutes for Unified-Messaging to start.
test interface: http://localhost:8080