Pre-requisites:
Having installed Java Runtime Environment (JRE) 21
Make sure the Java binaries are present in the Path variable (Environment Variables).
If you are upgrading from a 5.x version to a 6.x or higher version, take into account that the token format has changed (it cannot be copied and pasted).
The media storage has changed its layout: now the http and https folders are prefixed with a version directory (v1). After you run and the Middleware completes a full cycle, you may remove the old http and https folders.
To upgrade the Middleware to its latest version follow the steps below:
A. Download the new version
From the top bar menu, go to SETTINGS >> Broadcast Tools
Click on Middleware App (from here you will always get the latest version).
Or Download it here.
B. Stop the old Middleware
If you are running the old Middleware as a standalone, press CTRL+C to stop it and then close the command line window.
If you are running the old Middleware as a service, stop the service. Then uninstall the service running bin/flowics-middleware-uninstall-service.bat on the old Middleware folder.
C. Run the new Middleware
As a standalone run bin/flowics-middleware.bat on the new Middleware folder.
As a service:
Install the service running bin/flowics-middleware-install-service.bat on the new Middleware folder.
Start the service
To better understand, please read our Middleware installation guide at point 4.1 which describes how to upgrade the middleware from a previous version.
D. Check if the new Middleware is online
Stay informed about the Middleware's state with a quick status check:
Navigate to the Monitoring section:
Access the Settings menu in the top bar.
Select "Middlewares"
Click on the "Monitoring" tab.
View the Middleware status:
The status will be displayed as either "Online" or "Offline."
Check source status (if applicable):
If you're not using the Middleware for NCS integrations, you can also view the status of the Middleware sources.
By regularly monitoring the Middleware's status, you can ensure its smooth operation and promptly address any potential issues.
Monitoring Version Upgrades
When upgrading from a previous version you can simultaneously run different middleware versions on different servers using the same configuration token. This allows you to test the same Middleware Source integrations your existing middleware is syncing.
Take into consideration that both middlewares attempt to store media and files (if configured) into the Shared Folder Path, so that’s why you’ll need a different server to run the new instance. Also if you’re using the Database integration, you’ll need to configure a different database for every middleware to store data in a separate database.
Given this setup, you’ll be able to monitor both Middleware instances attached to the same configuration. A version selector appears in the Middleware Monitoring tab that allows you to choose the version to monitor.
