A collaboration bus message.
This is the main interface for handling messaging on the Collaboration Bus.
The Collaboration Bus Message header.
A service implement this method to receive messages that have been delivered to a channel for which the service is a consumer.
A client uses this interface to be notified of a populated CollaborationBusMessageHeader, before the message is actually sent.
Exception raised by the Collaboration Bus.
Channels are used to route messages between services. Messages can be exchanged using the point to point (Queue) model or the publish/subscribe (Topic)) model. It is very easy to use the collaboration bus. A service designed to consume messages on a channel need only specify it in the properties.xml file. Here is a sample xml snippet for a sample service that wants to consume messages on the "lottery" channel.
<message> <channel> <name>lottery</name> <type>ptop-single</type> <listener-class>com.avaya.collaboration.bus.sample.SampleCBConnector</listener-class> </channel> </message>This basically says the service has a class named SampleCBConnector which has a method named messageReceived(message). The messageReceived(message) method will be called asynchronously when a message is sent to the point to point (ptop) channel named lottery. Once this xml is added to the properties.xml file, the programmer needs to implement the one method. A publish/subscribe channel is set up the same way only the type is "pubsub-multi". A service can set up a maximum of 5 channels.
Copyright © 2014 Avaya. All Rights Reserved.