IBM webMethods Universal Messaging

IBM webMethods Universal Messaging (formerly from Software AG) is message-oriented middleware that provides guaranteed message delivery between distributed applications. It carries data across public, private, and wireless networks, and across heterogeneous systems. According to IBM's documentation, it works without a web server and without changes to firewall policy.

Key Capabilities

• Publish/Subscribe and Queues: Publish/subscribe messaging runs through channels. Point-to-point messaging runs through queues, where a message is consumed by a single subscriber. Archived Software AG documentation lists several channel types, including reliable (memory), persistent (disk), transient, mixed, paged, and off-heap.
• JMS Support: The product supports the Java Message Service (JMS) API, with JNDI-based configuration of topic and queue connection factories.
• Multi-Protocol Access: Archived documentation describes native protocols, Comet (for web clients), multicast, shared memory, and MQTT, a lightweight publish/subscribe protocol for constrained devices. It also lists AMQP 1.0 support, limited to the parts exposed through the JMS API, on fully featured licenses.
• Clustering and Federation: Clustering supports high availability, with master election, quorum, outage recovery, and sites. Realm federation connects separate servers (realms).
• Client APIs: APIs cover multiple enterprise programming languages, plus web and mobile applications. Server administration is available through an API.
• Additional Features: Joins, plugins, Data Groups, and low-latency I/O.
• Administration: A client and server architecture, with the Enterprise Manager for UI-based administration.

Audience & Use Cases

• Audience: Integration architects, middleware administrators, and developers building distributed and event-driven systems, particularly in the webMethods ecosystem.
• Use Cases: Guaranteed delivery of business messages and events between enterprise applications, and messaging to web, mobile, and wireless clients. It also serves as the messaging layer for webMethods integration products.

Technical Specifications

• Delivery Model: Guaranteed delivery with publish/subscribe and point-to-point messaging.
• Standards: JMS, MQTT, and AMQP 1.0 (partial).
• Deployment: Server (realm) with client libraries. The product page positions it within IBM webMethods hybrid integration.
• High Availability: Clustering with quorum-based master election.