|
A
Java Message Service (JMS) client that you can use to interact with
JMS providers to send or receive messages. The JMS service enables
interaction with JMS providers that implement both point-to-point
messaging and publish/subscribe messaging:
-
Point-to-point messaging involves clients that send messages to
a queue. Other clients extract the messages from the queues. After
the message is extracted, it is deleted from the queue. This type
of messaging is used when each message that is sent to a queue must
be received by only one JMS client.
-
Publish/subscribe messaging involves clients that publish
messages to a topic. The JMS provider sends the messages to other
clients that have subscribed to the topics. The message is deleted
after all subscribers have received the message. This type of messaging
is used when each message should be received by any number of clients.
Queues
and topics must be configured on the JMS provider (by an administrator)
before you can use them. Typically, JMS applications use Java Naming and
Directory Interface (JNDI) services for finding the names of the
topics and queues that are configured. After finding the name, the
JMS client connects to the JMS service to interact with the queues
and topics.
JMS messages include a header and a body. The
header includes metadata about the message in the form of properties
and corresponding values. Some property names are dependent on the
JMS application that you are using, and are used for message receivers
for interpreting the message. Other properties are used by the JMS
provider for processing the message.
Note:
To use
the operations that this service provides in a short-lived process,
you need to configure the transaction settings of the process version
so that transaction propagation is not supported. (See
Modifying processes
.)
For information about using the JMS service, see
LiveCycle ES2.5 Services
.
|
|
|
