- TIBAS_EVENT_PUT when a tuple is inserted, overwritten, or updated
- TIBAS_EVENT_TAKE when a tuple is taken or removed
- TIBAS_EVENT_EXPIRE when a tuple reaches the end of its time to live and expires from the space
- TIBAS_EVENT_SEED when there is redistribution after a seeder joins or leaves, and the local node is seeding or unseeding. This is only applicable if the listener distribution scope is SEEDED
- TIBAS_EVENT_UNSEED when there is redistribution after a seeder joins or leaves, and the local node is seeding or unseeding. This is only applicable if the listener’s distribution scope is SEEDED
Showing posts with label BusinessEvents. Show all posts
Showing posts with label BusinessEvents. Show all posts
29/03/2014
[TIBCO BusinessEvents] Listen for ActiveSpaces events
When working with TIBCO BusinessEvents, it's possible to create a channel on which to listen for TIBCO ActiveSpaces events such as:
08/02/2014
[TIBCO BusinessEvents] Send message to specific receiver on a multi-event queue
In an usual TIBCO BusinessEvents setting, all messages received on a channel are automatically mapped to the specified default event, but this process only works if ALL the messages received represent that particular event.
Since it's also possible to register multiple events on a queue binded to the same channel, for all the non-default events, we have to explicitly specify which event to fire, so that the incoming message is mapped to the correct event.
This can be done by adding two parameters to the message in the header section:
- _ns_ which specifies the namespace. The namespace points to the event type, eg: www.tibco.com/be/ontology/Events/MyEvent
- _nm_ which specifies the name of the event, eg: MyEvent
Subscribe to:
Posts (Atom)