Thank you for your advice, I’ll check onto that ..read more

Hey @Zainul_Abideen the free trial is already updated and you can download it via the usual free trials download form. The new license is valid till the end of October 2024 ..read more

As Philipp has mentioned this can be solved by using the Microservice SDK and updating the context in which you execute the creation of a new measurement: return microserviceSubscriptionsService.callForTenant(tenantId, () -> { // remove application header from context final MicroserviceCredentials clonedContext = new MicroserviceCredentials( contextService.getContext().getTenant(), contextService.getContext().getUsername(), contextService.getContext().getPassword(), contextService.getContext().getOAuthA ..read more

SmartREST 2 does not provide an interface for deleting of devices. It is intended that users (not devices) control when a device is deleted because deleting a device always and irreversibly removes the device and all its attached data. This includes all measurements, events, alarms and operations. Potentially also child devices and all their data is removed depending on chosen options. The device is also removed from the asset hierarchy which can have effects on other devices and their access for users. Altogether this is not an action that should be done implicitly by a device and requires ca ..read more

As explained in your last question, the microservice SDK provides means to remove the X-Cumulocity-Application-Key header. It just doesn’t work through the MeasurementApi class itself but through the context. Exclude a particular header in MeasurementApi or InventoryApi which creating or updating Most relevant headers including the X-Cumulocity-Application-Key header are controlled through the context. So in order to change or remove a header you’ll have to create a new context and run your request within it. The context is managed through com.cumulocity.microservice.context.ContextService< ..read more

Product/components used and version/fix level: Cumulocity IoT 1020.296.0 Detailed explanation of the problem: We need to delete a device using MQTT. Here I didn’t find any template to do so. Then I tried to define a custom SmartRest template, but on inventory the permitted operations are GET, POST and PUT Am I missing something? Is DELETE permitted using REST API only? Best Luca Error messages / full error message screenshot / log file: Question related to a free trial, or to a production (customer) instance? Customer instance ..read more

We are facing the issue, where we are not getting online statues for a device even though the device is getting the measurements every minute. We are using cumulocity sdk to send the measurements to the deviceas shown below: MeasurementRepresentation createMr = new MeasurementRepresentation(); createMr.set("measurement",xyz); createMr.setSource(xxx); createMr.setType(xxx); createMr.setDateTime(dateTime); measurementApi.create(createMr); If we use RestApi it is working fine. We had posted the question h ..read more

Hi Kirtish, ask your colleagues if they have a prepared installation image with which you can install your own copy of Designer. From the Documentation section of teh community look for the “Working with Designer” Guide as well as the “Service Development Help” Guide as a first starting point. Eventually you want to look for an adequate Beginner´s Training on learning.softwareag.com. Regards, Holger ..read more

Hi Venkat, search in the SAG_directory for a file called “cacerts”. This one is considered the base truststore file for your jvm when installed in the SAG_directory. When creating custom truststores, which contain additional root and intermediate CAs, which are not already present in cacerts-truststore, remember to add the “-trustcacerts” parameter to the keytool-command. Otherwise you might have to add these CAs to your custom truststores additionally. Regards, Holger ..read more

In the end the issue is simply that I’m using Spring’s WebSocketHandler with: public boolean supportsPartialMessages() { return true; } Setting this to false and setting a bigger size limit for the text messages for the session (WebSocketSession.setTextMessageSizeLimit() for example in the afterConnectionEstablished() method) solved the issue. The good news is that it means that Cumulocity webSocket implementation supports partial messages If let to true, I would need to check the value of WebSocketMessage.isLast ..read more