com.apama.cumulocity.notifications2
Event SubscribeTenantNotifications
Event which should be sent to its SEND_CHANNEL to trigger the creation of a Notifications 2.0 dynamic chain for a particular tenant. Unless a fatal issue is ran into, this will continually attempt to subscribe, until it succeeds.
If a tenant is already subscribed (either because CUMULOCITY_NOTIFICATIONS_AUTO_START is set to True, or because this event was previously called), this event will do nothing, except return a successful SubscribeTenantNotificationsComplete event.
If a N2.0 subscription already exists, this will resume with that subscription (and thus, pick up anything from the backlog). Otherwise, it will use the Notifications 2.0 API to create a new subscription.
A SubscribeTenantNotificationsComplete event with the same request ID will be delivered to indicate the status of the subscription request.- Since:
- 10.15.5.0
- See Also:
- com.apama.cumulocity.notifications2.SubscribeTenantNotificationsComplete - Event sent on completion of this request.
| Constant summary |
|---|
string | SEND_CHANNEL := "apama.notifications2.SubscribeTenantNotifications"
Channel to send this event to. |
SEND_CHANNEL
string SEND_CHANNEL := "apama.notifications2.SubscribeTenantNotifications"
Channel to send this event to.
reqId
integer reqId
Identifier for this request; must be generated using com.apama.cumulocity.Util.generateReqId().
tenant
com.apama.cumulocity.TenantDetails tenant
The tenant for which a Notifications 2.0 subscription and dynamic chain should be created.