Apama 10.15.0 | Other Resolved Issues | Release 10.5.1 | Cumulocity IoT Transport
 
Cumulocity IoT Transport
*PAM-30999
Runtime error when activating model in Analytics Builder which should be more robust in handling “atypical” objects.A runtime error was seen in Analytics Builder when a model failed to activate in one of the subtenants.
This issue is now resolved.
*PAM-31014
Cumulocity chain should log a WARN message if measurement timestamp is not set or invalid.
It is possible to forget setting a timestamp when sending measurements, alarms or events. If the timestamp is unset or is during the year 1970, a warning message is logged once per managed object.
*PAM-31036
Cumulocity IoT transport cannot use credentials from environment for long polling.
Previously, the old Cumulocity IoT transport required a user name and password to be specified in a configuration file. Now, it can pick up configurations from the environment. This is especially useful in the microservice mode where the user does not need to populate the configuration file and an empty configuration file can be injected. In the case of an app-key, a lookup for the application using its name is performed. If the lookup fails, then the app-key must be provided in the configuration file.