Event Notifications
The Connection Services Hub manages event notifications for the eMessage Connector. This Hub is included in the Connection Services Extension that runs on the ThingWorx Platform.
The Connection Services Hub is used to send events to the ThingWorx Platform to notify you of potential warning or error conditions that have occurred on a Connector. For example, if a data item message is written to an entity that does not exist on the ThingWorx Platform, the Connector drops the message and sends an event to the Connection Services Hub. You can create subscriptions to these events and define whatever corrective actions are necessary.
The Connection Services Hub is available once the CSE extension has been imported into the ThingWorx Platform, and the Connector has been started.
Events
Event notifications that are defined in the ConnectionServicesHub Thing Template include the following:
Event Name
Data Shape
Description
WritePropertyError
Indicates a failure to write a property on an entity, and provides details in a context object.
ClearCacheEntry
Instructs a Connector to clear an entry for a specified cache and key.
AuthenticationError
Indicates that a token authentication request that the eMessage Connector sent to the ThingWorx Platform on behalf of an agent failed to authenticate. .
InternalError
Indicates an error within the Connector, and provides details in a context object.
ProtocolError
Indicates a protocol exchange problem with the edge device has occurred, such as an invalid type for a data item (property) or an unexpected message (no ping rate in the registration message from an eMessage agent), and provides details in a context object.
EdgeError
Indicates that the eMessage agent sent in a SOAPStatus message that indicated an error statusCode. .
FileNotFoundError
Indicates a requested file could not be found in the specified repository, and provides details in a context object.
ThingNotFoundError
Indicates a requested entity could not be found, and provides details in a context object.
UserError
Indicates that a user-provided configuration on the ThingWorx Platform is not correct or is missing. An example of an error that causes this event to be generated is the setting of an identifier on ThingWorx for an Axeda Thing. The eMessage Connector rejects any egress message that contains an identifier that was defined for an Axeda Thing (edge device) on the ThingWorx Platform.
Was this helpful?