Consider the following reasons for using a WebSphere Message Broker as an ESB with WebSphere Process Server:
1: You are currently using WebSphere Message Broker and want to leverage existing skills.
2: You have extensive heterogeneous infrastructures, including both standard and non-standards-based applications, protocols, and data formats. For example, you are using industry formats such as SWIFT, EDI, or HL7.
3: You are implementing a wide range of messaging and integration patterns, for example, complex event processing and correlation, message splitting, and aggregation.
4: You need extensive pre-built mediation support.
5: Reliability and extensive transactional support are key requirements.
6: You want to achieve high-performance with horizontal and vertical scaling.
7: You want integration with other IBM WebSphere and Tivoli® products, as well as third-party JMS providers.
8: You want to natively transform non-XML formats without the use of adapters or user-written data transformations.
9: You want advanced publish and subscribe capabilities, including the use of a wide range of transports; high speed, low-latency messaging; and both topic and content-based routing.
10: You need complex event processing. Complex events are conditions that relate to multiple messages and are defined by applying a combination of logical, arithmetic, and temporal operators to messages or message attributes.
The IntelligentFilter and SituationManager SupportPac™ provides the ability to handle complex events that span multiple messages. Its complex event processing engine enables fast and reliable development of reactive applications, without requiring programming skills.
11: You want to integrate telemetry devices. WebSphere Message Broker can coordinate end-to-end telemetry integration. It can serve as a conduit for passing data from remote telemetry devices into enterprise applications.
Similarly, it can control data flow from command or control applications to remote control devices.
Well said.
ReplyDelete