Streaming Analytics

Release 10.6.0.21

This release upgrades the Apama-ctrl microservice to use Apama 10.5.0 Fix 21 (which is the same as Apama 10.5.4.0).

Fixes

Component	Description	Issue
Smart rules and EPL apps	Smart rules and EPL apps now pick up the tenant options `messaging/sms.senderName` and `messaging/sms.senderAddress` to set the sender name and address values used for `SendSMS` events. In your EPL apps, you can override the tenant options by specifying `senderName` and `senderAddress` in the `extraParams` field of the `SendSMS` event. Note that the tenant options are only read when the Apama-ctrl microservice is started. If the tenant options are changed, you must restart the microservice for the new values to take effect. If these tenant options are not defined, the following system default values are used: "Apama" as the sender name and "apama" as the sender address.	PAB-2148

Release 10.6.0.5

This release upgrades the Apama-ctrl microservice to use Apama 10.5.0 Fix 12 (which is the same as Apama 10.5.3.3).

Fixes

Component	Description	Issue
Apama-ctrl microservice	`onGeofenceCreateAlarm` and `onGeofenceSendEmail` smart rules behaved incorrectly when updates were received without location information. This problem has now been resolved.	PAB-1699

Release 10.6.0.4

This release upgrades the Apama-ctrl microservice to use Apama 10.5.0 Fix 10 (which is the same as Apama 10.5.3.1).

Fixes

Component	Description	Issue
Apama-ctrl microservice	The Apama-ctrl microservice will fail to start up if a corrupt smart rule is present. This problem has now been resolved.	PAB-1466
Apama-ctrl microservice	The ROLE_SMS_ADMIN role is missing from the Apama microservice manifest. This problem has now been resolved.	PAB-1498
Apama-ctrl microservice	The connection between the Apama-ctrl microservice and the correlator can be closed. This problem has now been resolved.	PAB-1459

Release 10.6.0.3

Fixes

Component	Description	Issue
Apama Analytics Builder	In the model manager, the user was not able to set a date for simulation mode using the date picker. This has been corrected, and the user can now use the date picker to select a date.	PAB-1419
Apama-ctrl microservice	When the Apama-ctrl microservice entered Safe mode, it did not disable all extensions. Thus, if an extension had a syntax error, Apama-ctrl could enter a restart loop as it would fail to start. This has been corrected, and Apama-ctrl now logs all extensions that are present but not loaded due to running in Safe mode.	PAB-1424

Release 10.6.0

Migration notes

If you have an on-prem installation of Cumulocity IoT (instead of using the cloud) and you upgrade Cumulocity IoT to 10.6.0, you must also upgrade the Apama-ctrl microservice from earlier versions to 10.6.0. This is mandatory due to a change in the communication protocol between Cumulocity IoT and Apama. Earlier versions of the Apama-ctrl microservice will not function correctly if running in Cumulocity IoT 10.6.0.

Improvements in Apama EPL Apps

Some events have been added to the Apama Cumulocity IoT API to allow easy retrieval of information in some predefined areas.

You can get the values for all the tenant options in the tenant, or search for specific tenant options. See the request-response events for looking up TenantOption in Querying Cumulocity IoT data.
You can look up the details and roles of the user you connected as, or the microservice service user. Alternatively, you can forward on the Authorization header or OAuth cookies of an incoming request to validate the roles of that user. See the request-response events for looking up CurrentUser in Querying Cumulocity IoT data.

In EPL, you can now receive a response for the creation or update of the predefined types (Alarm, Operation, Event, Measurement, MeasurementFragment and ManagedObject) by using the newly added withResponse action. Headers can now be set on the request, for example to determine the processing mode within Cumulocity IoT. For further information, see for example Sending alarms requesting response and setting headers in the Apama documentation.

It is now possible to listen for individual measurement fragments in EPL, rather than having to listen for and dissect entire measurements. For detailed information, see Measurement fragments.

Improvements in Apama Analytics Builder

The documentation for Apama Analytics Builder, including release notes, is available separately. For your convenience, the release notes from the above documentation are also given below:

The following new blocks are now available in the model editor:
- Machine Learning - Invokes the specified Machine Learning model that scores the input data. To use this block, the Machine Learning application must be available with the respective Machine Learning models in the tenant.
- Counter - Gives a count of the total inputs and repeated inputs.
See the Block Reference in the model editor for more information on the new functionality.
The Event Output block type now has an additional input port named Text Input. If connected, this sets the text of the event. If not connected, the Message parameter determines the text to be used. If neither are set, the model name is used as the text. See the Block Reference in the model editor for more information on the input port.
Apama Analytics Builder now also supports Polish. See also Language settings.

Fixes

Component	Description	Issue
Apama Analytics Builder	Within the block parameter editor, the error message displayed when the Zementis microservice has no models has been changed from saying that the Zementis microservice is unavailable to saying that the Zementis microservice has no models.	PAB-1250