Skip to main content

Deploying the JMS Inbound Connector


The following operating systems are supported for instances of the JMS inbound connector:

  • Red Hat Enterprise Linux (RHEL 8 and 9) / CentOS 7
  • Ubuntu 20.04
  • Ubuntu 22.04
  • Debian 10 (only on x86_64 hardware)
  • Debian 11

Installing on Linux

The connector is supported on both amd64 and arm64 architectures. Follow these steps on the system or systems where you plan to run the connector:

Install Java 11 or later, if it is not already installed.

RHEL or CentOS

sudo yum install java-11-openjdk

Debian or Ubuntu

sudo apt-get install openjdk-11-jre
  1. Install the connector package

Go to the Aerospike Enterprise downloads site to download the connector package for your operating system. After downloading the package, run either of these commands:

RHEL or CentOS

sudo rpm -i aerospike-jms-inbound-3.0.2-1.noarch.rpm

Debian or Ubuntu

sudo dpkg -i aerospike-jms-inbound-3.0.2.all.deb
  1. Install the Aerospike Database Enterprise Edition feature-key file

feature-key-file is deprecated in version 2.0.0. Verify that the feature file with the feature key mesg-jms-connector turned on and is loaded into the Aerospike server. The feature key is read directly from the Aerospike server.

Download the feature-key file and put in at the desired location which is accessible to the connector at runtime. The property mesg-jms-connector feature must be enabled in the feature key file.

  1. Enable connector auto start

Run this command to enable the connector to start on system startup or reboot:

sudo systemctl enable aerospike-jms-inbound

Run this command to start the connector:

sudo systemctl start aerospike-jms-inbound

Deploying on Docker

Aerospike provides Docker images for the Aerospike connect for JMS Inbound on Docker Hub.

sudo docker run -p 8080:8080 -v /home/aerospike/Downloads/aerospike-jms-inbound.yml:/etc/aerospike-jms-inbound/aerospike-jms-inbound.yml aerospike/aerospike-jms-inbound:3.0.2