O'Reilly - Java Message Service

More documents

Recommendations

Info

Java Message Service to naming and directory services, JMS abstracts access to MOMs. Using JMS, a messaging application's messaging clients are portable across MOM products. The creation of JMS was an industry effort. JavaSoft took the lead on the spec and worked very closely with the messaging vendors throughout the process. The initial objective was to provide a Java API for connectivity to MOM systems. However, this changed to the wider objective of supporting messaging as a first-class Java distributed computing paradigm equally with Remote Procedure Call (RPC) based systems like CORBA and Enterprise JavaBeans: There were a number of MOM vendors that participated in the creation of JMS. It was an industry effort rather than a Sun effort. Sun was the spec lead and did shepherd the work but it would not have been successful without the direct involvement of the messaging vendors. Although our original objective was to provide a Java API for connectivity to MOM systems, this changed over the course of the work to a broader objective of supporting messaging as a first class Java distributed computing paradigm on equal footing with RPC. - Mark Hapner, JMS spec lead, Sun Microsystems The result is a best-of-breed, robust specification that includes a rich set of message delivery semantics, combined with a simple yet flexible API for incorporating messaging into applications. The intent was that in addition to new vendors, existing messaging vendors would support the JMS API. 1.2.1 JMS Messaging Models: Publish-and-Subscribe and Point-to-Point JMS provides for two types of messaging models, publish-and-subscribe and point-topoint queuing. The JMS specification refers to these as messaging domains. In JMS terminology, publish-and-subscribe and point-to-point are frequently shortened to pub/sub and p2p (or PTP), respectively. This book uses both the long and short forms throughout. In the simplest sense, publish-and-subscribe is intended for a one-to-many broadcast of messages, while point-to-point is intended for one-to-one delivery of messages (see Figure 1.4). Figure 1.4. JMS messaging domains 10
Java Message Service Messaging clients in JMS are called JMS clients, and the messaging system - the MOM - is called the JMS provider. A JMS application is a business system composed of many JMS clients and, generally, one JMS provider. In addition, a JMS client that produces a message is called a producer, while a JMS client that receives a message is called a consumer. A JMS client can be both a producer and a consumer. When we use the term consumer or producer, we mean a JMS client that consumes messages or produces messages, respectively. We use this terminology throughout the book. 1.2.1.1 Publish-and-subscribe In pub/sub, one producer can send a message to many consumers through a virtual channel called a topic. Consumers, which receive messages, can choose to subscribe to a topic. Any messages addressed to a topic are delivered to all the topic's consumers. Every consumer receives a copy of each message. The pub/sub messaging model is by and large a push-based model, where messages are automatically broadcast to consumers without them having to request or poll the topic for new messages. In the pub/sub messaging model the producer sending the message is not dependent on the consumers receiving the message. Optionally, JMS clients that use pub/sub can establish durable subscriptions that allow consumers to disconnect and later reconnect and collect messages that were published while they were disconnected. The pub/sub JMS messaging model is discussed in greater detail in Chapter 2, and Chapter 4. 1.2.1.2 Point-to-point The point-to-point messaging model allows JMS clients to send and receive messages both synchronously and asynchronously via virtual channels known as queues. The p2p messaging model has traditionally been a pull- or polling-based model, where messages are requested from the queue instead of being pushed to the client automatically. In JMS, however, an option exists that allows p2p clients to use a push model similar to pub/sub. A given queue may have multiple receivers, but only one receiver may consume each message. As shown in Figure 1.4, the JMS provider takes care of doling out the work, insuring that each message is consumed once and only once by the next available receiver in the group. The JMS specification does not dictate the rules for distributing messages among multiple receivers, although some JMS vendors have chosen to implement this as a load balancing capability. P2p also offers other features, such as a queue browser that allows a client to view the contents of a queue prior to consuming its messages - this browser concept is not available in the pub/sub model. The p2p messaging model is covered in more detail in Chapter 5. 1.3 Application Scenarios Until now, our discussion of enterprise messaging has been somewhat abstract. This section attempts to give some real-world scenarios to provide you with a better idea of the types of problems that enterprise messaging systems can solve. 11
Page 2 and 3: Java Message Service Richard Monson
Page 4 and 5: Chapter 7. Deployment Consideration
Page 6 and 7: Java Message Service Although this
Page 8 and 9: Java Message Service Examples devel
Page 10 and 11: Java Message Service Chapter 1. Und
Page 12 and 13: Java Message Service Before we disc
Page 16 and 17: 1.3.1 Enterprise Application Integr
Page 18 and 19: Java Message Service Figure 1.5. Dy
Page 20 and 21: Java Message Service With J2EE, JSP
Page 22 and 23: Java Message Service recognition of
Page 24 and 25: TopicConnectionFactory conFactory =
Page 26 and 27: Java Message Service Before examini
Page 28 and 29: Understanding JNDI Java Message Ser
Page 30 and 31: Java Message Service The TopicConne
Page 32 and 33: protected void writeMessage(String
Page 34 and 35: Java Message Service When the Topic
Page 36 and 37: Java Message Service publishing a m
Page 38 and 39: Java Message Service Messages come
Page 40 and 41: 3.1.1.3 JMSMessageID Java Message S
Page 42 and 43: 3.2 Properties Java Message Service
Page 44 and 45: Java Message Service The following
Page 46 and 47: Notification of certain bids on inv
Page 48 and 49: Java Message Service When a consume
Page 50 and 51: UTF-8 Java Message Service UTF-8 en
Page 52 and 53: Java Message Service Table 3.1 show
Page 54 and 55: Java Message Service Essentially, M
Page 56 and 57: 3.4.9 Interoperability and Portabil
Page 58 and 59: 4.1.1 Running the B2B Application J
Page 60 and 61: jne.printStackTrace( ); System.exit
Page 62 and 63: try { Properties env = new Properti
Page 64 and 65:
Java Message Service Once the Retai
Page 66 and 67:
Java Message Service We can demonst
Page 68 and 69:
Java Message Service publish( ) met
Page 70 and 71:
Java Message Service The receive( )
Page 72 and 73:
4.7 Unsubscribing Java Message Serv
Page 74 and 75:
Java Message Service multiple consu
Page 76 and 77:
import javax.jms.TopicConnectionFac
Page 78 and 79:
} } try { System.out.println("\nRet
Page 80 and 81:
TopicConnectionFactory tFactory = n
Page 82 and 83:
public QWholesaler(String broker, S
Page 84 and 85:
Java Message Service have already p
Page 86 and 87:
} if (message != null){ int orderQt
Page 88 and 89:
Java Message Service Chapter 6. Gua
Page 90 and 91:
6.2.1 AUTO_ACKNOWLEDGE Java Message
Page 92 and 93:
Java Message Service via publish-an
Page 94 and 95:
Java Message Service message. If th
Page 96 and 97:
Java Message Service QWholesaler an
Page 98 and 99:
Java Message Service avoids process
Page 100 and 101:
Figure 6.8. Transactional messages
Page 102 and 103:
Java Message Service uses a JMS tra
Page 104 and 105:
} return; session.commit(); } else
Page 106 and 107:
Else, commit (that's what just happ
Page 108 and 109:
XAResource jmsXA = session.getXARes
Page 110 and 111:
... } { try { Thread.sleep(10000);
Page 112 and 113:
Chapter 7. Deployment Consideration
Page 114 and 115:
Java Message Service A vendor may h
Page 116 and 117:
Java Message Service that your memo
Page 118 and 119:
Java Message Service only really vi
Page 120 and 121:
7.2.5 The Bottom Line Java Message
Page 122 and 123:
Java Message Service There are two
Page 124 and 125:
Java Message Service Figure 7.2. Us
Page 126 and 127:
Chapter 8. J2EE, EJB, and JMS 8.1 J
Page 128 and 129:
Java Message Service JNDI ENC. In a
Page 130 and 131:
8.3 The JMS Resource in J2EE Java M
Page 132 and 133:
Java Message Service Although sessi
Page 134 and 135:
Figure 8.3. Lifecycle of a message-
Page 136 and 137:
Java Message Service With the messa
Page 138 and 139:
Java Message Service It's also supp
Page 140 and 141:
Java Message Service The FioranoMQ
Page 142 and 143:
Java Message Service The iBus//Mobi
Page 144 and 145:
9.6.2 Next Version Java Message Ser
Page 146 and 147:
A.1.2 Connection Java Message Servi
Page 148 and 149:
A.1.8 JMSException Java Message Ser
Page 150 and 151:
} public void setInt(String name, i
Page 152 and 153:
} public Message receiveNoWait( ) t
Page 154 and 155:
} public void writeInt(int value) t
Page 156 and 157:
A.2.6 QueueSender Java Message Serv
Page 158 and 159:
} throws JMSException; public Conne
Page 160 and 161:
Appendix B. Message Headers Java Me
Page 162 and 163:
Java Message Service are delivered
Page 164 and 165:
Java Message Service JMSTimestamp P
Page 166 and 167:
UTC Java Message Service UTC (Unive
Page 168 and 169:
Java Message Service JMSReplyTo Pur
Page 170 and 171:
Java Message Service JMSType Purpos
Page 172 and 173:
} public void setByteProperty(Strin
Page 174 and 175:
Java Message Service Each of the ac
Page 176 and 177:
JMSXAppID Java Message Service This
Page 178 and 179:
Appendix D. Message Selectors Java
Page 180 and 181:
The BETWEEN operator can be used to
Page 182 and 183:
D.5 Declaring a Message Selector Ja
Page 184:
Colophon Java Message Service Our l
show all

O'Reilly - Java Message Service

Create successful ePaper yourself

Delete template?

Save as template?