Skip to end of metadata
Go to start of metadata

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: https://dev.healthconnect.be/confluence/x/4ow9

Typically, your migration can be described as one of the following scenario's:

  1. Moving UM from server A to server B, DB stays on server SQL X
  2. Moving UM from server A to server B, moving DB from server SQL X to server SQL Y
  3. Moving DB from server SQL-X to server SQL-Y (UM stays on server A)

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

    1. On server A:
      1. run services.msc and check properties of unified-messaging. Note the directory of 'path to executable' (e.g."C:\Program Files\unified-messaging\" (="[location]")
      2. take a backup of [location]\application.properties
      3. run services.msc and stop the services unified-messaging and unified-admin
      4. open the properties of service unified-messaging and unified-admin and set startup type to 'disabled'
    2. On SQL server X: 
      1. take a backup of the DB on which UM connects
        1. you can find the connection string in [location]\application.properties on server A
    3. On server B:
      1. run installer https://download.healthconnect.be/products/unified-messaging/slow-ring
        1. 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.

      2. in the database connection test, fill in the same connection string as written in application.properties on server A (point b.i.1)
        In the port-section, use the same port as before (written in backup of application.properties, field server.port)
      3. proceed with the installer and finish it.
        Wait 5-10 minutes for Unified-Messaging to start.
      4. 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.
      5. test interface: http://localhost:8080
  • If you connect to Healthdata (HD4DP), inform them that Unified-Messaging has moved and that the location is http://[hostname:port]
  • if you use certain webservices, make sure to adapt the endpoints to new host
  • 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

    1. On server A:
      1. 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]")
      2. take a backup of [location]\application.properties
      3. run services.msc and stop the services unified-messaging and unified-admin
      4. open the properties of service unified-messaging and unified-admin and set startup type to 'disabled'
    2. On SQL server X: 
      1. take a backup of the DB on which UM connects
        1. you can find the connection string in c:\Program Files\Unified-Messaging\application.properties on server A
    3. On SQL server Y:
      1. import backup of DB
      2. make sure the user that will connect to the DB is still DBOwner
    4. On server B:
      1. run installer https://download.healthconnect.be/products/unified-messaging/slow-ring
        1. 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.

      2. 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)
      3. proceed with the installer and finish it.
        Wait 5-10 minutes for Unified-Messaging to start.
      4. 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.
      5. test interface: http://localhost:8080
  • If you connect to Healthdata (HD4DP), inform them that Unified-Messaging has moved and that the location is http://[hostname:port]
  • if you use certain webservices, make sure to adapt the endpoints to new host
  • 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)

    1. On server A: run services.msc and stop the services unified-messaging and unified-admin
    2. On SQL server X: 
      1. take a backup of the DB on which UM connects
        1. you can find the connection string in c:\Program Files\Unified-Messaging\application.properties on server A
    3. On SQL server Y:
      1. import backup of DB
      2. make sure the user that will connect to the DB is still DBOwner
    4. On server A:
      1. run installer https://download.healthconnect.be/products/unified-messaging/slow-ring
        1. 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.

      2. in the database connection test, fill in the connection string pointing to new DB on SQL server Y
      3. proceed with the installer and finish it.
        Wait 5-10 minutes for Unified-Messaging to start.
      4. 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.
      5. test interface: http://localhost:8080

 

  • No labels