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.
Subject: Core Services 11.1.3 Package release notes.
Date: 31-Oct-2024
Includes:
AP11.1_SU03.pkg
AP_AIM-11.1.3.pkg
JOB_SCHEDULER-11.1.3
ABOUT:
This package can be used for a new installation or to update an existing installation.
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
[AUTOPILOT_HOME]/bin/pkgman ../updates/AP11_SU<#>.pkg
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:
[AUTOPILOT_HOME]/naming/ATPNAMES -h
For the CEP server:
[AUTOPILOT_HOME]/localhost/ATPNODE -h
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).
[AUTOPILOT_HOME]/bin/pkgman -rebuild
Next Steps
At this point, using the same procedure as above, install the updated versions of Application Implementation (AIM) and Scheduler (if previously installed).
[AUTOPILOT_HOME]/bin/pkgman ../updates/AP_AIM-11.1.3.pkg
[AUTOPILOT_HOME]/bin/pkgman ../updates/JOB_SCHEDULER-11.1.3.pkg
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.
Fixes
11.1.3
CFA-59 Policies under Policy Managers are showing as stopped
CFA-96 registry.xml is corrupted after repeated saves, array type property on read appends null values
CFA-99 Syslog expert is not reading the facility details correctly.
CFA-100 logging performance improvements
CFA-147 [Code Roll-in] To autopilot setup.ini must be added old jars remove
CFA-93 On grid when changing CEP service data, they will not to changed on domain and after CEP restart that data are lost
CFA-105 Autopilot sensors ignore periods works incorrectly
CFA-107 Webhook randomly blocks other notification activities
CFA-138 [Code Roll-in] Policy File not loading properly, while saving corrupts it
11.1.2
CFA-83 Resolved issue in which sensor with rule operations “is greater than“, “is less than“, “is at least“ or “is at most operation“ was not triggered for time values (HH:mm:ss) or string values with nonnumeric first characters.
11.1.1
CFA-60 Domain server does not start after updating Autopilot version from 11.0.3 to 11.1.1
CFA-70 CEP server health grayed out
CFA-73 Got error when trying to Load LDAP server user/user group
CFA-13 System facts service growing "Connection Agents" facts
CFA-76 variables are not being substituted as expected
CFA-5 Switch AutoPilot to use meshIQ BOM dependencies and CodeArtifact repositories
CFA-6 StringIndexOutOfBoundsException when regex is missing closing >
CFA-7 policy which has not active facts should not generate ERROR
CFA-16 Master domain server must contains secondary domain metrics in HA mode
CFA-17 Change outdated L&F selection library
CFA-30 Autopilot v 11.1 build fix by newest versioning