Welcome Guest! Log in
Due to some maintenance operations, stambia.org will be switched to read-only mode during the 13th November. It will be possible to read and download, but impossible to post on the forums or create new accounts. For any question please contact the support team.


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
Prerequisites:
  • The java libraries corresponding to the JMS server provider must be installed in the Designer and Runtime

Note:

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.

 

Download

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
Connectivity

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

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

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

The following transaction modes are supported:

  • SESSION_TRANSACTED
  • CLIENT_ACKNOWLEDGE
  • AUTO_ACKNOWLEDGE
  • DUPS_OK_ACKNOWLEDGE
Receive methods

The received messages can be:

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

 

 

You have no rights to post comments

Articles

Suggest a new Article!