Monitor and manage Java Message Service (JMS) queues that are active for your tenant.

You can use JMS queues, also referred to as message queues, to store messages temporarily on a tenant. SAP Integration Suite uses a JMS message broker as storage location for message queues.

The screen consists of two main areas: The main table at left that shows the active message queues.

When you select a queue, all messages stored in that queue are listed in the table at right.

The following adapters can store messages in queues or read messages from there: AS2 adapter, JMS adapter, XI adapter.

You can use message queues to implement scenarios where SAP Integration Suite handles the reprocessing (also referred to as: retry) of messages when an error happens. To do so, message queues come with a built-in retry mechanism. For example, if you use the JMS adapter to implement such a scenario, messages that cause an error are retried after a time period that depends on the retry interval defined by you for the JMS sender adapter.

Tip

Did you know? You can also get information about JMS message queues by an OData V2 application programming interface (API). You find the APIs and their documentation on SAP Business Accelerator Hub at: Message StoresInformation published on SAP site (under JMS Resources).

See also:

Managing Message Queues

Check both used and available JMS resources.

JMS resources in the connected JMS message broker are limited. For more information on the limits and how to increase storage capacity, check out JMS Resource Limits and Optimizing their Usage.

In the JMS Resources information box below the header, you can see the status of the current JMS resource usage. Click the link to find out more .

Monitor and manage all active queues.

This table shows all active queues. For each queue, the number of stores messages is shown. You can perform different actions on a selected queue, for example, retrying all messages in the selected queue, finding out the associated integration flows, or deleting all messages from the queue.

Tip

The system creates a JMS queue automatically on deployment of the first integration flow using a new JMS queue name.

Monitor and manage the messages stored in a selected queue.

This table shows all messages that are stored temporarily in a selected queue.

For each message, certain attributes are displayed like, for example, the JMS Message ID, the Message ID, the status of the message in the queue, information about when the message has been stored in the queue, and information on the next scheduled retry.

The JMS Message ID is generated by the runtime when the entry is written to the JMS queue, while the Message ID identifies the message processing log for the message. Clicking the Message ID link, you can navigate to the Monitor Message Processing screen for the selected message.

Show unused and missing queues.

As check result, you get:

You can delete any queues that aren't needed and generate missing queues by redeploying the integration flow.

Manually trigger retry of the selected message.

Download the selected message.

The message is downloaded as file archive (.zip) that contains message body, header and properties.

Learn more about message queues.

Managing Message Queues