EdgeServerJMS - Revision history

Matt: Undo revision 5889 by StevenCollins (Talk)

2012-02-29T08:24:23Z

Undo revision 5889 by StevenCollins (Talk)

StevenCollins at 19:14, 24 November 2011

2011-11-24T19:14:50Z

Matt: Reverted edits by Amesycyxa (Talk); changed back to last version by Gustavo.cabral

2010-11-26T19:43:33Z

Reverted edits by Amesycyxa (Talk); changed back to last version by Gustavo.cabral

Show changes

Amesycyxa at 23:13, 23 November 2010

2010-11-23T23:13:06Z

Show changes

Gustavo.cabral: /* Components */

2010-06-04T17:23:59Z

‎Components

Gustavo.cabral: /* Overview */

2010-06-04T17:22:15Z

‎Overview

Gustavo.cabral: /* A very, very brief JMS Introduction */

2010-06-04T17:18:29Z

‎A very, very brief JMS Introduction

Kyle: /* Components */

2009-09-24T20:12:03Z

‎Components

Kyle: /* Components */

2009-09-24T20:07:20Z

‎Components

Kyle: /* Setting up a Producer */

2009-09-24T19:53:37Z

‎Setting up a Producer

@@ Line 6: / Line 6: @@
 There are two types of clients to the server.  A ''JMS Consumer'' will consume JMS Messages.  A ''JMS Producer'' will send messages to the server.
-There are two ways to use JMS.  You can either use a ''point-to-point'' model, or you can use a ''publish-subscribe'' model.  The basic difference is that with the point-to-point model, for every message produced, there is at most one consumer.  With the publish-subscribe model, there can be more than one consumer.  Point-to-point implementations will use a ''JMS Queue'' as a destination.  Publish-subscribe implementations will use a ''JMS Topic''. For a better explanation <span class="plainlinks">[http://www.shoppharmacycounter.com/t-dietpillsonline.aspx <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">diet pills</span>], see: this [http://activemq.apache.org/how-does-a-queue-compare-to-a-topic.html|FAQ article].
+There are two ways to use JMS.  You can either use a ''point-to-point'' model, or you can use a ''publish-subscribe'' model.  The basic difference is that with the point-to-point model, for every message produced, there is at most one consumer.  With the publish-subscribe model, there can be more than one consumer.  Point-to-point implementations will use a ''JMS Queue'' as a destination.  Publish-subscribe implementations will use a ''JMS Topic''. For a better explanation, see: this [http://activemq.apache.org/how-does-a-queue-compare-to-a-topic.html|FAQ article].
 Rifidi Edge Server uses ActiveMQ as its provider.  With ActiveMQ, the server is called a Broker.  Rifidi uses Spring to create and start the broker.
@@ Line 16: / Line 16: @@
 * Internal Message Bus - This is used for tag data that is collected by sensor plugins (e.g. Commands executing on an Alien9800 session).  It is implemented using an ActiveMQ broker with one Destination (specifically a Topic).  Since it is only used internally, clients (both producers and consumers) connect to it using a VM connection.
-* External Notification - This is used to expose tag events and notification events to software outside the Edge Server. It is implemented using an ActiveMQ broker with two Destinations (one Topic for tag events and one for notification events).  Clients to the broker (both producers and consumers) can connect to it using <span class="plainlinks">[http://www.supplementstoweightloss.com/ <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">weight loss pills</span>] a VM connection.  Clients external to the edge server can use a TCP connection.
+* External Notification - This is used to expose tag events and notification events to software outside the Edge Server. It is implemented using an ActiveMQ broker with two Destinations (one Topic for tag events and one for notification events).  Clients to the broker (both producers and consumers) can connect to it using a VM connection.  Clients external to the edge server can use a TCP connection.
 There are two kinds of events used in the Rifidi Edge Server:

@@ Line 6: / Line 6: @@
 There are two types of clients to the server.  A ''JMS Consumer'' will consume JMS Messages.  A ''JMS Producer'' will send messages to the server.
-There are two ways to use JMS.  You can either use a ''point-to-point'' model, or you can use a ''publish-subscribe'' model.  The basic difference is that with the point-to-point model, for every message produced, there is at most one consumer.  With the publish-subscribe model, there can be more than one consumer.  Point-to-point implementations will use a ''JMS Queue'' as a destination.  Publish-subscribe implementations will use a ''JMS Topic''. For a better explanation, see: this [http://activemq.apache.org/how-does-a-queue-compare-to-a-topic.html|FAQ article].
+There are two ways to use JMS.  You can either use a ''point-to-point'' model, or you can use a ''publish-subscribe'' model.  The basic difference is that with the point-to-point model, for every message produced, there is at most one consumer.  With the publish-subscribe model, there can be more than one consumer.  Point-to-point implementations will use a ''JMS Queue'' as a destination.  Publish-subscribe implementations will use a ''JMS Topic''. For a better explanation <span class="plainlinks">[http://www.shoppharmacycounter.com/t-dietpillsonline.aspx <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">diet pills</span>], see: this [http://activemq.apache.org/how-does-a-queue-compare-to-a-topic.html|FAQ article].
 Rifidi Edge Server uses ActiveMQ as its provider.  With ActiveMQ, the server is called a Broker.  Rifidi uses Spring to create and start the broker.
@@ Line 16: / Line 16: @@
 * Internal Message Bus - This is used for tag data that is collected by sensor plugins (e.g. Commands executing on an Alien9800 session).  It is implemented using an ActiveMQ broker with one Destination (specifically a Topic).  Since it is only used internally, clients (both producers and consumers) connect to it using a VM connection.
-* External Notification - This is used to expose tag events and notification events to software outside the Edge Server. It is implemented using an ActiveMQ broker with two Destinations (one Topic for tag events and one for notification events).  Clients to the broker (both producers and consumers) can connect to it using a VM connection.  Clients external to the edge server can use a TCP connection.
+* External Notification - This is used to expose tag events and notification events to software outside the Edge Server. It is implemented using an ActiveMQ broker with two Destinations (one Topic for tag events and one for notification events).  Clients to the broker (both producers and consumers) can connect to it using <span class="plainlinks">[http://www.supplementstoweightloss.com/ <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">weight loss pills</span>] a VM connection.  Clients external to the edge server can use a TCP connection.
 There are two kinds of events used in the Rifidi Edge Server:

@@ Line 29: / Line 29: @@
 ==Components==
-There several JMS objects that are automatically created when the edge server starts up (inside jms.xml in the spring folder of the jms bundle).  These objects should be reused when applicable.  The objects that should be reused are made available as OSGi services.  To see the description of the JMS OSGi Services see [[Edge_Server_Architecture#JMS_Services]]
 ===Broker===
 As mentioned above, there are two brokers: an internal and and external one.  You can connect to either broker within the edge server using a vm connection.
@@ Line 41: / Line 45: @@
 * <tt>org.rifidi.edge.internal</tt> - Used to collect tag messages from sensors
-These three destinations are available as services in the osgi registry.  The bean names are:
+These three destinations are available as services in the OSGi registry.  The bean names are:
 * <tt>externalNotificationsDest</tt>
 * <tt>externalTagsDest</tt>

@@ Line 11: / Line 11: @@
 ==Overview==
-The Rifidi Edge Server uses JMS (ActiveMQ) to pass certain kinds of data from component to component. The edge server separates its usage of JMS into two logical components:
-* Internal Message Bus - This is used for tag data that is collected by sensor plugins (e.g. Commands executing on an Alien9800 session).  It is implemented using an ActiveMQ broker with one Destination (specifically a Topic).  Since it is only used internally, clients (both producers and consumers) connect to it using a vm connection.
+The Rifidi Edge Server uses JMS (ActiveMQ) to pass certain kinds of data from component to component. The Edge Server separates its usage of JMS into two logical components:
-* External Notification - This is used to expose tag events and notification events to software outside the edge server. It is implemented using an ActiveMQ broker with two Destinations (one Topic for tag events and one for notification events).  Clients to the broker (both producers and consumers) can connect to it using a vm connection.  Clients external to the edge server can use a TCP connection.
 There are two kinds of events used in the Rifidi Edge Server:
 * Tag Events - These events consist of tag data produced by sensors (depicted in blue below)
 * Notification Events - These are system events such as a new reader being created, a session state change, or a property on a reader changing. (depicted in red below)
-[[Image:Edgeserverjms.png|thumb|500px|none]]
+[[Image:Edgeserverjms.png|thumb|center|500px|none]]
 ==Components==
 There several JMS objects that are automatically created when the edge server starts up (inside jms.xml in the spring folder of the jms bundle).  These objects should be reused when applicable.  The objects that should be reused are made available as OSGi services.  To see the description of the JMS OSGi Services see [[Edge_Server_Architecture#JMS_Services]]

@@ Line 8: / Line 8: @@
 There are two ways to use JMS.  You can either use a ''point-to-point'' model, or you can use a ''publish-subscribe'' model.  The basic difference is that with the point-to-point model, for every message produced, there is at most one consumer.  With the publish-subscribe model, there can be more than one consumer.  Point-to-point implementations will use a ''JMS Queue'' as a destination.  Publish-subscribe implementations will use a ''JMS Topic''. For a better explanation, see: this [http://activemq.apache.org/how-does-a-queue-compare-to-a-topic.html|FAQ article].
-Rifidi Edge Server uses ActiveMQ as its provider.  With ActiveMQ, the server is called a Broker.  Rifidi uses spring to create and start the broker.
+Rifidi Edge Server uses ActiveMQ as its provider.  With ActiveMQ, the server is called a Broker.  Rifidi uses Spring to create and start the broker.
 ==Overview==

← Older revision		Revision as of 19:53, 24 September 2009
Line 128:		Line 128:

	Now you can use the send method in the template to send the message to the broker.		Now you can use the send method in the template to send the message to the broker.
		+
		+	===Sending Tags to an External Source===
		+	TODO: Since there will be classloading issues if you try to use ObjectMessages when sending tags to something that is running in a different JVM, it is better to serialize the object you are trying to send first into a ByteArrayMessage. Then deserialize the message yourself when receiving it.

	==Setting up a Consumer==		==Setting up a Consumer==