Justification WebSphere Business Integration Message Broker would be an ideal choice if there is a need to handle high-volume of messages, reliable messaging and other sophisticated capabilities of integration. Given the lack of clarity on these non-functional aspects and in order to keep the solution simple, we would use the Web services gateway. The solution could be migrated to WebSphere Business Integration Message Broker at a later time. 12.2.4 Products In this section we look at the products available to implement the various components in the Exposed Broker runtime pattern. Product implementation options Product choices for this scenario are based on: Design decisions made in 12.2.3, "Analyze design options" on page 343. Extended Enterprise capabilities of the products Products currently available We can use the following currently available products to implement the Broker component in the given scenario: Web services gateway component in WebSphere Application Server Network Deployment. WebSphere Business Integration Message Broker For this scenario, the Web services gateway component in WebSphere Application Server Network Deployment meets all of the requirements and, as a result, is the product of choice. The complete product mapping for this scenario is shown in Figure 12-4 on page 346. Chapter 12. Exposed Broker runtime pattern: generic profile 345