The Apama Cumulocity IoT transport implementation has changed some of the internal channel names (since 10.5.0).

This will be transparent to most users, but if you are trying to debug or test code by subscribing a receiver to those channels, you may need to subscribe to the CumulocityIoTGeneric channel instead of, or in addition to, the CumulocityIoT channel. In addition, if you are connecting to a tenant which does not have automatic hostname mapping (such as with a Cumulocity IoT Edge instance) you may need to explicitly set the CUMULOCITY_TENANT option in your configuration properties.

Unicode variable names in mapping rules cannot be resolved (since 5.0).

Mapping in the correlator-integrated messaging adapter for JMS does not support internationalization for variable names. That is, only English characters are allowed in complex mapping template variable names.