Chapter 9. Broker solutions using WebSphere Business Integration Message Broker 267
}
/**
* @see javax.servlet.http.HttpServlet#void (javax.servlet.http.HttpServletRequest,
javax.servlet.http.HttpServletResponse)
*/
public void doPost(HttpServletRequest req, HttpServletResponse resp)
throws ServletException, IOException {
}
}
There are no deployment considerations for this application. It is a simple Web
application and doesn’t require any JMS resource definitions.
9.7.3 Build and deploy the message flow
The message flow for this scenario only requires one node (Figure 9-33). The
Real-timeOptimizedFlow node simply facilitates the communication between the
clients (both those that publish and those that retrieve information).
Figure 9-33 Real-time message flow
The node defines the port it will operate on. Clients who are publishing
information use this port to send information to. Message-driven bean clients
define this port in the topic connection factory (Figure 9-34).

Get Patterns: Broker Interactions for Intra- and Inter-enterprise now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.