Messaging
To support your integration project at run-time, you need a messaging system that can reliably handle the volume of messages that will be sent and received. The system should have these characteristics:
-
Guaranteed delivery and fault tolerance—Message delivery must be guaranteed, and the system must be fault tolerant. If a message cannot be delivered because the recipient was unavailable, the messaging system must queue that message and continue to operate. The queued message must then be redelivered as appropriate.
-
Distributed architecture—A distributed, loosely coupled system is much more likely to support the fault-tolerance you require than a monolithic system that depends on one centralized server.
-
High throughput—High throughput without performance degradation is needed. Requirements vary throughout the day and throughout the business year, and you cannot afford performance degradation at the time when business increases.
-
Scalability—As your business grows, you want to be able to update your business integration in a simple and cohesive way. Furthermore, you want to be able to connect your integration project with other departments using a similar system. The messaging system must support this scalability.
ActiveMatrix BusinessWorks is based on messaging standards with proven track records. Supported protocols include TIBCO Rendezvous, JMS, and HTTP.