Skip to content

Overview

Concepts and Principles

Development

Overview

IDEs

API Explorer

Releases

Release Notes

TORO Integrate

Coder Studio

Coder Cloud

Bug Reports

Search

Configuring Remote ActiveMQ

By default TORO Integrate ships with an embedded instance of ActiveMQ. The embedded instance requires no further configuration.

However, for production instances processing a large volume of messages, it is recommended that TORO Integrate be configured to use a standalone instance of ActiveMQ instead.

Prerequisites

For the purpose of this documentation, it is recommended that you have a standalone ActiveMQ deployed in your machine. You can learn about how to install ActiveMQ here.

Configuration

Step 1: Switch to data folder

After acquiring the necessary prerequisites, proceed to the data directory of TORO Integrate.

1
cd <TORO_INTEGRATE_HOME>/data

Step 2: Modify override.properties file

Open the override.properties file in the data folder, then add the following properties that will override the default properties file. This is where we will indicate the use of a remote ActiveMQ instance.

1
2
3
jms.file=remote-activemq
jms.clientId=toro-integrate
jms.url=tcp://<activemq-ip-address>:61616?closeAsync=false

If you'd like to use more than one instances of ActiveMQ with your TORO Integrate instance, check out our documentation on Master-Slave configurations for ActiveMQ.

Application Properties

The Properties UI can be used to modify TORO Integrate's properties as well. This is where you can personalize details like jms.prefix values and more through the UI. A restart is required for these changes to take effect.

Step 3: Start ActiveMQ

Start your remote ActiveMQ instance if it's not already running. By executing:

For Unix

1
./activemq start

For Windows

1
bin\activemq start

Start vs. Console

Similar to TORO Integrate's start and run commands, ActiveMQ has start and console. start is a parameter used to start the ActiveMQ instance while console is used to start the process while seeing the logs appear in real time. Although, to navigate away from this process (execution of ActiveMQ via console) you will need to either start a new session or kill the process.

Step 3: Restart TORO Integrate

Restart your TORO Integrate instance. You can check out this page if you don't know how to restart it.

Step 4: Access ActiveMQ web console

Proceed to the admin page of your ActiveMQ using your (e.g  <http://localhost:8161/admin>)

ActiveMQ Topics

Step 5: ActiveMQ topic

Select the Topics tab. You should see a topic named jmsPrefix.io.toro.integrate.Tracker.

Step 5: Invoke

Invoke any service (e.g. RssMethods.readRss(...) method), do it several times. You'll notice that the enqueued messages property of jmsPrefix.io.toro.integrate.Tracker topic will increase.

Broker Menu

The Broker menu item will disappear from the TORO Integrate web UI (available in the Server Edition) once TORO Integrate is configured to use a remote ActiveMQ instance. To view broker statistics you need to use the ActiveMQ administration console.

You have now successfully configured TORO Integrate with a remote instance of ActiveMQ.