This topic describes the JMS topic resources provided by the default messaging provider for JMS publish/subscribe messaging, and supported by a service integration bus.
JMS publish/subscribe messaging and the default messaging provider is shown in the following figure.
An application that uses JMS publish/subscribe messaging acts as a producer or consumer of messages with JMS topics, and has no need to know about other service integration resources that support the JMS topic.
An administrator can define a JMS topic, an administrative object that encapsulates the name of a topic and a topic space on a service integration bus. Applications can obtain the JMS topic by looking its name up in the JNDI namespace.
JMS applications can publish messages to, and subscribe to messages from, JMS topics. Subscribing applications can normally receive messages published to a topic only when the subscriber is connected to the server.
The default messaging provider also supports the use of durable subscriptions to topics, which enable the subscriber to receive messages that were published when the subscriber was disconnected. For more information about durable subscriptions, see section 6.11.1 of the JMS 1.1 specification.
Unlike configuring queues, the administrator does not need to assign the topic space to a bus member. A topic space has a publication point defined automatically for each messaging engine in the bus. Messages for the topic space are stored and processed on all its publication points.
When subscribing to topics, applications can specify wildcard characters to select a range of topics.
With JMS 1.1, you are recommended to use domain-independent JMS connection factories for new applications. Domain-specific topic connection factories are supported for backwards compatibility for JMS applications developed to use domain-specific topic interfaces, as described in section 1.5 of the JMS 1.1 specification.
For more information about creating temporary JMS destinations, see section 4.43 of the JMS 1.1 specification.
For a temporary JMS topic, the service integration bus creates a temporary topic space, which the administrator can list and browse but normally does not need to act on. A temporary topic space is deleted automatically when the connection is closed.