Navigation:  Messaging and Streaming > Publish-Subscribe > Messaging Destinations >

About Destinations

Previous pageReturn to chapter overviewNext page

WebORB messaging destinations must be configured in the messaging-config.xml file located in the WEB-INF/flex folder. If WebORB is deployed into a ASP.NET application which uses the publish-subscribe functionality, the WEB-INF/flex folder must be present in the deployment with all the files from the default installation.

 

Consider the following examples of messaging destinations:

 

Sample polling destination:

<destination id="SamplePollingDestination">
 <properties>
   <server>
     <durable>false</durable>
   </server>
   <message-service-handler>Weborb.Messaging.PubSub.Memory.MessagingServiceHandler</message-service-handler>
   <message-storage-policy>Weborb.Messaging.PubSub.Memory.MemoryStoragePolicy</message-storage-policy>
 </properties>
 <channels>
   <channel ref="my-polling-amf"/>
 </channels>        
</destination>

 

Sample RTMP destination:

<destination id="SampleRTMPDestination">
 <properties>
   <server>
     <durable>false</durable>
   </server>
   <message-service-handler>Weborb.Messaging.PubSub.Memory.MessagingServiceHandler</message-service-handler>
   <message-storage-policy>Weborb.Messaging.PubSub.Memory.MemoryStoragePolicy</message-storage-policy>
 </properties>
 <channels>
   <channel ref="weborb-rtmp"/>
 </channels>
</destination>

 

Messages published to and retrieved from a WebORB messaging destination are processed by a class implementing the Weborb.V3Types.Core.IServiceHandler interface. The class is referred to as messaging service handler. It is responsible for processing the incoming messages and either directly or indirectly delivering them to the subscribers. WebORB includes the following implementations of the messaging service handlers:

 

WebORB Message Routing (default handler) - this handler has a configurable policy for storing messages received from publishers and retrieving messages for delivery to subscribers. The default implementation of the storage policy stores messages in memory, however the policy can be overridden to save messages in a database or any other persistent storage.
 
MSMQ Message Routing (MSMQ handler) - maps a destination to a MSMQ queue. Routes messages received from the publishers to the queue. Also acts as an intermediary between the subscribers and the queue. Messages received from the queue are automatically routed to the subscribers.
 
Apache NMS Message Routing (NMS handler) - maps a destination to a messaging broker available through the Apache NMS API including ActiveMQ. WebORB publishes messages delivered to the WebORB destination to the corresponding NMS destination. Similarly WebORB retrieves messages from the NMS destination and delivers them to the WebORB subscribers.