Glossary

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.

A WebSphere MQ process that performs subscription resolution in a publish/subscribe model.

A WebSphere MQ object that is a logical communication link.

The WebSphere MQ combination of encryption algorithm and hash function applied to an SSL message after authentication completes.

A set of cryptographic algorithms used by an SSL connection.�

A network of queue managers that are logically associated in some way. �

A WebSphere MQ queue hosted by a cluster queue manager and made available to other queue managers in the cluster.�

A WebSphere MQqueue manager that is a member of a cluster�.

The process of converting readable text, called plain text, and an unreadable form, called cipher text.�

The process of converting cipher text messages back to their plain text form.

Provides protection against impersonation. A digital certificate binds a public key to its owner, whether that owner is an individual, a queue manager, or some other entity.

A JMS subscription that retains messages while a client is disconnected.

The process that converts a plain text message to cipher text.

A WebSphere MQ queue manager that hosts a complete set of information about every queue manager in the cluster.�

Java Message Service.

The store for digital certificates and their associated private keys.�

A WebSphere MQqueue manager that an application connects to.�

A JMS application that produces or consumes messages.

WebSphere MQ, the message-oriented middleware provided by IBM.

WebSphere MQ publish-and-subscribe function.

WebSphere MQ message queue interface programming API.

WebSphere MQ message queue manager process that manages a queue.

A JMS subscription that retains messages only while a client is connected.

In WebSphere MQ, refers to the queue managers in the cluster, which inquire about the information in the full repositories and build up their own subsets.�

A WebSphere MQ message body.

The secret key that must be kept secret in asymmetric algorithms.�

The secret key that can be public in asymmetric algorithms.

In WebSphere MQ, the information that is sent by a publisher.

In WebSphere MQ, the sender in a publish/subscribe model.

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.�

The same secret key used by symmetric algorithms.

In WebSphere MQ, the grouping of related MQ topics.

In WebSphere MQ, the receiver in a publish/subscribe topology.

A Tibco JMS domain for publishing or consuming one-to-many messaging.

Cryptography algorithms that require both parties to use the same secret key.

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.