Skip to content

Home

Development

IDEs

API Explorer

Releases

Release notes

Martini Runtime

Martini Desktop

Martini Online

Feature requests

Bug reports

Configuring the message broker

Martini uses the configured broker when saving and indexing Tracker and invoke monitor documents1, communicating with connected instances, listening to destinations for JMS listener endpoints, and more – like user-written JMS-reliant applications.

Why use a message broker?
  • Asynchronous communication

    Message brokers allow clients to proceed with other processes, whether or not the current service has provided a response.

  • Broker clustering

    Multiple brokers can be configured to work as a federated network of brokers for scalability purposes.

  • Location transparency

    The location of the applications don't need to be known which means changes in details about the services can also be made without affecting or disrupting the client.

  • Reliability

    Sources or destinations don't have to be simultaneously available in order to send or receive messages.

In production environments, it is recommended to replace the embedded ActiveMQ broker with something more robust, especially when Martini actively uses the broker for any of the tasks above.

In the following pages, we'll teach you how to setup the message broker instance and how to make Martini run your selected message broker.


  1. For performance efficiency.