See information about the latest product version
Scenarios: WebSphere Message Broker using TCP/IP
WebSphere® Message Broker can be added to systems that use TCP/IP for transport, to generate a more flexible architecture for communication between components.
The scenarios in the Scenarios: TCP/IP topic show how systems can be created to use TCP/IP as a transport mechanism. The following sections show how WebSphere Message Broker can be added to those systems to generate a more flexible architecture for communication between components:
- Expense submission illustrates TCP/IP to TCP/IP routing
- Price-change notification illustrates routing and transformation to other formats
Expense submission
The expense submission scenario shown in the Scenarios: TCP/IP topic requires a direct connection from the client applications to the end server. With that model it is difficult to add new consumers of the expense submission information, and it is also difficult to change the end application that processes them. However, by adding WebSphere Message Broker as an intermediary router, the two systems can be separated without any changes to their interfaces, as shown in the following diagram:

Price-change notification
The price-change notification scenario shown in the Scenarios: TCP/IP topic can be modified to use a broker for routing and transformation. It could also allow support for other protocols like WebSphere MQ, which would allow new applications to be written to different interfaces without the need for changing the current client or server applications:
