Welcome Guest! Log in
Stambia versions 2.x, 3.x, S17, S18, S19 and S20 are reaching End of Support January, 15th, 2024. Please consider upgrading to the supported Semarchy xDI versions. See Global Policy Support and the Semarchy Documentation.

The Stambia User Community is moving to Semarchy! All the applicable resources have already been moved or are currently being moved to their new location. Read more…

Stambia Data Integration allows to work with Java Message Service (JMS) servers.

A JMS Metadata is available to define all the server's credentials and communication properties, and to design the different JMS objects.

It can then be used on the dedicated Process Actions that allows to:

  • Send messages to topics or queues
  • Receive messages from queues or subscribers
  • Manage the transactions
  • The java libraries corresponding to the JMS server provider must be installed in the Designer and Runtime


Stambia DI is a flexible and agile solution. It can be quickly adapted to your needs.

If you have any question, any feature request or any issue, do not hesitate to contact us.

This component may require a dedicated license.

Please contact the Stambia support team if you have any doubt and if you need to use it in a production environment.



All the necessary material to use JMS with Stambia DI is already included in the Designer and Runtime.


Supported features

You can find bellow an overview of what Stambia can do with JMS servers

Name Description

Messages can be sent to or received from the following JMS items:

  • Topic (send)
  • Subscribers (receive)
  • Queues (send and receive)

All the operations can be managed in transactions, committed manually or automatically.

The following transaction modes are supported:

Receive methods

The received messages can be:

  • Stored directly in a file
  • Used in the rest of the Process through a Bind Link




Suggest a new Article!