Getting Started with WebSphere Application Server

More documents

Recommendations

Info

110 Getting Started with WebSphere Application Server Community Edition Figure 6.1 - Messaging: The big picture 6.2 Java Message Service Java EE includes the Java Message Service (JMS) specification, which defines a set of interfaces and semantics that Java EE applications can utilize to send or receive messages to a messaging provider. A messaging provider provides the infrastructure that supports messaging, such as Active MQ or IBM WebSphere MQ products. JMS is the API specification only. It is analogous to what JDBC does for accessing databases. 6.2.1 JMS application roles A JMS application is composed of the following parts: 1. JMS provider - This is a messaging system that implements the JMS specification. Community Edition uses Active MQ as its default JMS provider. 2. JMS client - This is a Java application that sends and receives messages. There are two kinds: - JMS Producer - A JMS client that sends messages to a destination of a JMS provider. - JMS Consumer - A JMS client that receives messages from a destination of a JMS provider.
Chapter 6 – Messaging 111 3. Messages - These are objects that are used to communicate information between JMS clients. 4. Administered objects - These are preconfigured JMS objects that are created by an administrator of the JMS provider for the use of JMS clients. In Community Edition, these are called the JMS resource group. - Destination - A destination encapsulates addressing information for a specific JMS provider. A JMS client uses a destination object to address a message to a specific destination on the underlying JMS provider. - ConnectionFactory - A connection factory encapsulates the configuration information that is required to connect to a specific JMS provider. A JMS client uses a connection factory to create a connection to that JMS provider. 6.2.2 JMS application models As messaging technologies have evolved, two types of asynchronous messaging models have emerged, Point-to-Point and Publish/Subscribe. These models describe how JMS clients communicate with each other through JMS destination provided by the JMS provider. 6.2.2.1 Point-to-Point In this model, there is a one-to-one mapping between the sender and receiver of a message. The destination is usually referred to as a queue. Figure 6.2 shows the Point-to- Point messaging model. Figure 6.2 - Point-to-Point messaging model 6.2.2.2 Publish/Subscribe In this model, there is potentially a one-to-many relationship between the sender and receiver of a message. The destination is usually referred to as a topic. Figure 6.3 shows the Publish/Subscribe messaging model.
Page 3 and 4:
G E T T I N G S T A R T E D W I T H
Page 5 and 6:
Notices This information was develo
Page 7 and 8:
Trademarks IBM, the IBM logo, and i
Page 9 and 10:
3.8 Exercises .....................
Page 11 and 12:
9.3.2 Changing port numbers .......
Page 13 and 14:
13 Preface Keeping your skills curr
Page 15:
The DB2 on Campus book series 15
Page 18 and 19:
18 Getting Started with WebSphere A
Page 21 and 22:
1 Chapter 1 - Introduction to WebSp
Page 23 and 24:
Introduction to WebSphere Applicati
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 47 and 48:
3 Chapter 3 - Development with Comm
Page 49 and 50:
Chapter 3 - Development with Commun
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60: Chapter 3 - Development with Commun
Page 65 and 66: 4 Chapter 4 - Working with database
Page 67 and 68: Chapter 4 - Working with databases
Page 89 and 90: 5 Chapter 5 - Enterprise Java Beans
Page 91 and 92: 1. Define local and remote interfac
Page 93 and 94: Chapter 5 - Enterprise Java Beans 9
Page 97 and 98: Note: Chapter 5 - Enterprise Java B
Page 109: 6 Chapter 6 - Messaging Messaging i
Page 113 and 114: Chapter 6 - Messaging 113 2. Get JM
Page 115 and 116: Chapter 6 - Messaging 115 Figure 6.
Page 117 and 118: Chapter 6 - Messaging 117 Figure 6.
Page 119 and 120: Chapter 6 - Messaging 119 For examp
Page 121 and 122: textMessage.getText()); } catch (JM
Page 123 and 124: Chapter 6 - Messaging 123 3. Copy t
Page 125: Chapter 6 - Messaging 125 D. Messag
Page 128 and 129: 128 Getting Started with WebSphere
Page 161:
PART III - ADMINISTERING COMMUNITY
Page 164 and 165:
164 Getting Started with WebSphere
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 181 and 182:
10 Chapter 10 - Tuning a Community
Page 183 and 184:
Chapter 10 - Tuning a Community Edi
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
10.4.2 Operating system tuning Chap
Page 193:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 211 and 212:
A Appendix A - Solutions to review
Page 213 and 214:
Appendix A - Solutions to review qu
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
B Appendix B - Up and running with
Page 221 and 222:
Appendix B - Up and running with DB
Page 223 and 224:
4. The following is performed by de
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235:
C Appendix C - Using the sample cod
Page 238 and 239:
Page 240:
show all

Getting Started with WebSphere Application Server

Create successful ePaper yourself

Delete template?

Save as template?