Creating or editing a JMS endpoint
JMS endpoints provide information that Studio and the Integration
Appliance use to connect to a JMS instance.
Specifying delivery rules and retry parameters for JMS activities
The JMS Connector uses a single login session for all connections
to a JMS endpoint. If a session expires, the connector automatically
establishes a new session. The JMS Connector does not count the initial
attempt to reacquiring the session as a retry attempt. The JMS Connector
assumes the typical connector retry behavior after the initial attempt
to reacquire a session fails.
Get Message activity
You can use the Get Message activity to get a message from
the queue. If there is no message present the activity can time out.
Poll Message activity
The Poll Message activity is a starter activity that polls
the configured queue for the message. This activity supports the ATLEAST
ONCE and EXACTLY ONCE delivery semantics. The Poll Message Activity
supports batching, if the batching option is selected.
Publish Message activity
The Publish Message activity is an executable activity
that allows you to publish data on the configured topic. This activity
supports the ATLEAST ONCE and ATMOST ONCE delivery semantics.
Send Message activity
The Send Message activity is an executable activity that
sends message to the configured queue. The Send Message activity supports
the AT LEAST and AT MOST ONCE delivery semantics. Request-reply use
cases can use the Poll Message and Send Message activity; there is
no separate activity for reply.
Subscribe Message activity
The Subscribe Message activity is a starter activity that
allows you to subscribe to a JMS topic. This activity supports the
ATLEAST ONCE and EXACTLY ONCE delivery semantics.