The meshIQ Platform requires a version 11 license. Contact your meshIQ sales representative for details.
The meshIQ platform core services are leveraged by all modules in the meshIQ platform for run time services. The core services are installed first and then any related modules.
Upgrade Installation Steps
- Stop all meshIQ services and applications.
- Copy the package into [AUTOPILOT_HOME]/updates
- Using the GUI or from the command prompt, install the latest package
where <ver> AutoPilot version, # service update number.
If running using the GUI package manager, exit it before continuing.
Note: You must start one of the core services (Domain Server, CEP or Enterprise Manager) to finalize installation BEFORE installing any other packages or running package manager again.
The first time you restart after updating, the system updates jar files. But to load the jar files correctly requires more than one restart. The easiest way to restart initially is to just run the help option, which will update all jars, display help and then exit.
For the domain server:
For the CEP server:
Rebuild Package Management Tables
If you are upgrading to the meshIQ platform from AutoPilot M6, run the following from the command line version of package manager (not available from Windows Product Maintenance or GUI).
At this point, using the same procedure as above, install the updated versions of Application Implementation (AIM) and Scheduler (if previously installed).
If you have other modules to update you can proceed to them at this point or restart the meshIQ services if you have completed your installation.
- Deployment Tool: tree
- Business View: tree and graphs
- Business Process: graphs
- Sensor Selector: tree
CFA-33: To improve performance, sensors now take thread from pool by manager/policy name instead of just manager name.
CFA-41: A GRID failover issue, in which the WGS expert showed as greyed out and was not showing any facts although the WGS was running, has been addressed. The standby/failover CEP instance was timing out on the domain side, being removed from the cluster and set to inactive mode. Therefore the CEP was not rejoining the domain with the correct state when the connection between the CEP and Domain was lost and then restored.