Skip to main content
Skip table of contents

Upgrade

Before you Upgrade

When using SwiftMQ 13, it's essential to follow some best practices for optimal operation:

  1. Use the Router Script: Always start SwiftMQ with the provided router script rather than custom scripts. The router script is integral to the system, regularly tested and updated with each release.

  2. Managing routerconfig.xml: The routerconfig.xml file in SwiftMQ is dynamic and changes automatically with various system components. Instead of version controlling this file, use preconfig files for your specific configurations like queues, topics, JMS listeners, etc. Include these preconfig files in your version control system (VCS). When starting SwiftMQ with the router script, add your preconfig files as parameters. This approach ensures that routerconfig.xml is consistently updated with your configurations.

Upgrade Procedure from 12.0.0 Onwards

Note: This upgrade procedure is valid for release 12.1.0 only! Upcoming releases will provide you with rolling upgrades without downtime. However, release 12.1.0 requires stopping both HA instances because we have removed Swiftlets which can't be handled by the rolling upgrade.

To upgrade a SwiftMQ HA Router follow these steps:

  • Install both instances of the new SwiftMQ HA Router (new release).

  • Stop both instances of the old SwiftMQ HA Router (old release).

  • Copy the complete data directory from the old to the new release for both instances.

  • Start both instances of the new SwiftMQ HA Router (new release).

During startup, the new SwiftMQ HA Router will automatically convert the routerconfig.xml and apply changes, if necessary. To accomplish this, it is important that you always use the router script of the new release!

SwiftMQ clients will transparently reconnect to the new SwiftMQ Router. If necessary, update them with the new swiftmq.jar when you have time.

Upgrade from older Releases

Please have a look here.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.