For basic differences with the meshIQ platform, first read What makes the meshIQ Platform (Version 11) different?
The migration steps for moving from 10.x to version 11.x are very similar to what was done in the past.
If you are using deployment packs and their upgrade scripts, the process is the same. See the deployment pack documentation for details.
The rest of this article applies if you are using package manager to apply your changes as an in-place upgrade. This is just a summary, see product documentation and release notes for details.
Upgrading your AutoPilot server components
The AutoPilot engine is now referred to as Core Services. You will need the latest service update (and any prerequisite updates you have not applied). We have dropped the SU01, SU02 from the package names for consistency across the platform. For example, AP_CORE-11.2.pkg is version 11.2 is the initial release and AP_CORE-11.2.1.pkg is service update 1. As with any service update, it is important to make a complete backup before starting, as uninstall will not be able to revert from version 11 back to an earlier version. Folder and configuration files remain intact when upgrading with this method.
Upgrading your Navigator components
With version 11, Navigator is called Manage and NavxWSM is called Secure. In addition to their new names, the applications have an updated look and feel. The same capabilities remain but their presentation is improved. The upgrade process is unchanged. Download and unzip the main bundle. For example, Manage_11.2.zip. After download, use package manager to install the services. Then run the nsqjdbcmk scripts to upgrade the databases. Be sure to back up the tables as there is no built-in restore process. Copy the web applications to your Apache servers, noting the name changes and ensuring any configuration files are updated. After restarting, be sure to log in using manage and secure. Existing bookmarks will no longer function.
What's next?
For most Navigator customers, at this point, you have migrated your existing components to Manage. You do not need to progress further but there are new capabilities that you may not have. The following are some examples.
Viewing policies and metrics reports
You can use the Track GUI to view data collected by your environment. This includes all metrics collected by Manage as well as policies and sensors from Observe. For example, you might want to create an ad hoc report of all queues that have default persistent set on or view queues currently in alarm. This requires data services and Track to be installed
Grafana / Prometheus Integration
Many customers have Grafana and Prometheus in place. As a replacement for or in addition to Track, customers can use these to view and alert on Navigator metrics. This requires data services to be installed.