Article - CS288599
GetProperties service used in Mashups leads to request overhead in ThingWorx
Modified: 17-Dec-2024
Applies To
- ThingWorx Platform 8.1 to 9.3
Description
- GetProperties service used in Mashups leads to request overhead
- In a Mashup, the GetProperties service can be used and configured to automatically update values when new values are received, without having to refresh the Mashup manually
- This service is only visible in the Mashup Builder and not available when inspecting the Thing's services
- The GetProperties' ServiceInvokeCompleted Event can be used to call subsequent services once a new value is received
- For each property bound to a Widget, the dependent service will be invoked once - e.g.
- if 1 property from the GetProperty service is bound to a Widget and 1 dependent service is called, 1 service call will be sent to the ThingWorx Platform server
- if 10 properties from the GetProperty service are bound to a Widget and 1 dependent service is called, 10 service calls will be sent to the ThingWorx Platform server
- if 10 properties from the GetProperty service are bound to a Widget and 10 dependent services are called, 100 service calls will be sent to the ThingWorx Platform server
- Depending on the number of properties bound, the number of services called, the frequency of property updates and the number of times the Mashup is simultaneously viewed this design could lead to potential performance issues with ThingWorx as the Platform will be flooded with requests and Tomcat might not be able to catch up with answering/responding to the massive amount of incoming requests
This is a printer-friendly version of Article 288599 and may be out of date. For the latest version click CS288599