Both the JMS- and MQ-related terms defined here are used throughout this document.
A TIBCO JMS subscription that retains messages while the client is not connected.
A TIBCO JMS subscription that retains messages only while the client is connected.
In TIBCO JMS, a domain for point-to-point messaging.
In WebSphere MQ, an object that stores sent messages.
The WebSphere MQ rules and formatting header used by MQ pub/sub. All messages sent to the MQ pub/sub broker or to the stream queue must have an RF header. The RF header conveys control information to the MQ pub/sub broker. In MQ pub/sub messages, the message payload contains a RF header, followed by the application data.
The WebSphere MQ rules and formatting header; the portion of the message header that provides rules and formatting information for that message
A TIBCO JMS message provider. For instance, TIBCO JMS is a service provider, called a messaging provider in this document.
In TIBCO JMS, similar to queues in, but used for one-to-many messaging.
In WebSphere MQ, the subject of a publication. WebSphere MQ pub/sub topics and JMS topics are different. In JMS, a topic is a pub/sub endpoint, whereas in WebSphere MQ pub/sub, a topic is a subject of a message.
WebSphere MQ pub/sub topics and JMS topics
are different. In JMS, a topic is a pub/sub endpoint, whereas
in WebSphere MQ pub/sub, a topic is a subject of a message.