The JMS- and MQ-related terms defined here are used throughout this document.
The cryptography algorithms that use one key for encryption and a different key for decryption. One of these must be kept secret, but the other can be public.
The WebSphere MQ combination of encryption algorithm and hash function applied to an SSL message after authentication completes.
A WebSphere MQ queue hosted by a cluster queue manager and made available to other queue managers in the cluster.�
The process of converting readable text, called plaintext, and an unreadable form, called ciphertext.�
Provides protection against impersonation. It binds a public key to its owner, whether that owner is an individual, a queue manager, or some other entity.
A WebSphere MQqueue manager that hosts a complete set of information about every queue manager in the cluster.�
In WebSphere MQ, refers to the queue managers in the cluster, which inquire about the information in the fullrepositories and build up their own subsets.�
In JMS, a domain for point-to-point messaging.
In WebSphere MQ, an object that stores sent messages.
In WebSphere MQ, a different queue manager from the one the application is connected to. �
The WebSphere MQ rules and formatting header used by MQ publish/subscribe. All messages sent to the MQ publish/subscribe broker or to the stream queue must have an RF header. The RF header conveys control information to the MQ publish/subscribe broker. In MQ publish/subscribe 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.
An industry standard protocol for transmitting data in a secure manner over an unsecured network.�
In TIBCO JMS, similar to queues, but used for one-to-many messaging.
In WebSphere MQ, the subject of a publication. WebSphere MQ publish/subscribe topics and JMS topics are different. In JMS, a topic is a publish/subscribe endpoint, whereas in WebSphere MQ publish/subscribe topics and JMS topics are different.