Skip to end of metadata
Go to start of metadata


  • This update requires the installation of extra software next to the existing Tomcat installation.
    • This software uses an embedded Tomcat installation that gets installed as a service and contains our unified-messaging application.
  • Check if the minimal system requirements (min MSSQL2016!) and network requirements are met.
  • Also run our installer to check the firewall (and DB connection of possible) see this instruction but with some side notes.
    • Don't stop the existing Tomcat installation if port 8080 is occupied by it, just pick another one (this is just a test anyway, not the actual install)
    • if no recent installation of Java 8 64bit is found on the machine. our installer will attempt to download it from
      • You can circumvent this by manually installing a recent version of java 8 first.
  • Since the unified-messaging service will run on a new port, make sure the port can be accessed from outside of the machine if needed.
    • this may not be needed at all since UM is not the application the end users use.
      they use the application know as eForms to us, it will keep running under the existing Tomcat installation.
      This is also the reason, not to change the port on the existing tomcat installation and pick an extra one.

The steps of the installation/update

Prior to the installation.

  1. Inform the end users the application will be unavailable during the update timeslot.
  2. Let a DBA make a backup of the 'unified-messaging' and 'eforms' databases. (the exact names can be found in the context.xml of Tomcat)

Changes to the tomcat installation.

  1. Stop the Tomcat Service (typically called HIP, unless a custom Tomcat installation by the customer was used)
  2. Move both the folder and war of "unified-messaging" out of the tomcat\webapps folder to a backup location.
  3. Adapt the context.xml file (tomcat\conf) and change the connectionstring of "jdbc/unifiedmessaging" to point to the database of eforms.
    Now both jndi connections "jdbc/unifiedmessaging" and "jdbc.eforms" will point to the same database but this is intentional to get this setup working.

Changes on the DB (To be done by the DBA)

  1. Move all the tables starting with IAM_ or iam_ from the HCUM/unified-messaging database to the eforms database.
  2. adapt the port in the 'propertyValue' content of the row which has 'hector.service.endpoint' as value for the 'propertyKey' column in the table in the eforms database to the port that will be used 

Start and check of the old eforms and IAM installation

  1. Start the tomcat service and wait for 5 minutes for the applications to start
  2. Check if eForms and IAM are Running
    1. go to the eforms login page. If this opens eforms is running
    2. Login with a user. if this works IAM is running.

The Actual update

  1. Start the unified-messaging install wizzard.
  2.  Click [Next] 
  3. Scroll Down, click [Accept]
  4. Click [Next]
  5. Set the desired folders for the application and logs, click [Next]
  6. Connection test
    1. set a proxy if required
    2. Pick Acceptation or Production depending if it's a test or production environment.
    3. Click [Test] and wait for the checks to pass
    4. Click [Next]
  7. Database Connection
    1. for Type Pick MSSQL
    2. adapt the url so the jdbc connection points to the unified-messaging database.
    3. Click [Test]
    4. Click [Next]
  8. Acces
    1. keep the interface on
    2. set the port that was picked for the unified-messaging installation
    3. Click [Test]
    4. Click [Next]
  9. Admin service
    1. keep the port on 10101
    2. Click [Test]
    3. Click [Next]
  10. Installation
    1. Click [Next]
    2. When finished Click [Close]


  1. Wait 5 minutes for the application to be started and migrated.
  2. check the logs of the um to see if the DB migration was successful
  3. login to the web interface of unified messaging with a support account (this can only be done by Healthconnect)
    1. Create an admin account for the ict department of the customer.
    2. do a basic send and receive test.
  4. Application Testing done by the customer 


  • No labels