General questions about Joram.

Here are a list of commonly asked questions and answers.

See also these other sources of information:

• The documentation page which includes links to presentations, user's guide and API javadoc.
• The Getting started page,
• The Tutorials page,
• and the Features page that gives a listing of the main features available in Joram.

If you have a question not answered here, please join the community mailing list or alternatively, contact the development team directly at joram-team@ow2.org.

We welcome contributions so please help us make the documentation better!

What is Joram?

JORAM is an open sourced implementation of JMS 1.1 as part of the J2EE specification. It provides access to a true distributed MOM (Message Oriented Middleware), built on top of the ScalAgent agent based distributed platform.

JORAM, the MOM it gives access to, and the Scalagent platform are open source softwares and released under the LGPL license.

Why use Joram?

Message-Oriented Middleware is increasingly being seen as a key to improve the enterprise productivity and to facilitate the open services market. Today enterprises are faced with the challenges of time-to-market, data distribution, application integration and business flexibility in the context of loosely-coupled distributed systems encountered in multi-organization environments over the Internet:

• E-business, EAI and B2B solutions,
• Telco management systems,
• Networked devices management solutions: energy, building/home automation, etc.

What is the license?

This software is open source using the LGPL license (GNU Lesser General Public License or formerly the GNU Library General Public License). The LGPL is a free software license published by the Free Software Foundation (FSF).

How is JORAM priced?

JORAM is free software in both the gratis and libre senses.

Can I get commercial support?

Absolutely, see our Support page for information about commercial support.

You can also directly check the detailed description of ScalAgent D.T. professional services on JORAM.

JORAM is also supported as an open-source project, for general questions please join our mailing list or contact the development team at joram-team@ow2.org.

What is JMS?

The Java Message Service (JMS) API is an API for accessing enterprise messaging systems. It is a crucial component of the Java 2 Platform, Enterprise Edition (J2EE). If you need mor information see: what is JMS.

What is MQTT?

MQTT is an IoT (Internet of Things) connectivity protocol. It was designed as an extremely lightweight publish/subscribe reliable messaging transport. It is useful for connections with remote locations where a small code footprint is required and/or network bandwidth is at a premium. Due to its small size and low power usage it is also ideal for mobile applications where efficient distribution of information is needed.

MQTT is used in 62% of IoT solutions and remains the IoT messaging reference protocol (see IOT Developer Survey 2018).

If you need more information see: what is MQTT.

What is AMQP?

AMQP stands for the Advanced Message Queue Protocol and is a specification for how messaging clients and brokers can interoperate. AMQP is a specification of a wire-level protocol for client to message broker communication. It is not a messaging system like Joram, but just a messaging protocol.

Joram has code in the sandbox for implementing AMQP v0.9.1, it is aiming to provide support for AMQP 1.0 once it is finalised, as well as other open protocols.

Through these protocols, Joram can support clients in C/C++, C#, Ruby, Python, Perl, PHP, etc.

What is Stomp?

Stomp is a simpler text based protocol which is designed to be very simple to implement in any language or platform (e.g. you can use a telnet client to communicate via Stomp). There are already clients for many languages: C, C++, C#, Delphi, Erlang, Flash, Lisp, Objective-C, Perl, PHP, Python, etc.

Joram supports Stomp since 5.4.0, see the corresponding tutorial.

Is Joram transactional?

Yes. Persistent messages are handled by the Joram MOM in a transactionnal way providing atomicity and durability properties to the clients that request them.

The JMS client provides either regular JMS and XA transactions.

Does Joram support store-and-forward?

Yes, as a MOM Joram supports store-and-forward message sending.

Submit a question or problem?

Please join our mailing-list We'd like to hear from you.