Skip to content

Install Aerospike Connect to JMS

Installer

Starting with version 4.0.0, a single installer handles both XDR 5.0 wire protocol and HTTP. Go to the Aerospike Enterprise downloads site to download and install the connector package for your platform. The connector is supported on both amd64 and arm64 architectures.

Remember to set the protocol based on the change notification source. See protocol for details.

Prerequisites

Aerospike Database change notification configuration

Deploy on Docker

Aerospike provides Docker images for Aerospike Connect for JMS on Docker Hub.

Terminal window
sudo docker run \
-v <path to local aerospike-jms-outbound.yml>:/etc/aerospike-jms-outbound/aerospike-jms-outbound.yml \
container.aerospike.com/aerospike/aerospike-jms-outbound:4.2.10

<path to local aerospike-jms-outbound.yml>: The path (including the name) of the configuration file in your local filesystem.

Installation prerequisites on Linux

Supported operating systems

The connector is supported on the following operating systems:

  • RHEL/CentOS (8 and 9)
  • Ubuntu (20.04, 22.04 and 24.04 LTS)
  • Debian (11 and 12)
  • Amazon Linux 2023

Java Runtime Environment

This connector is a Java web-application that requires Java 17 or later. Both Oracle and OpenJDK Java Runtime Environments are supported.

Installation

The installation steps below apply to both the Debian (*.deb) and Red Hat Enterprise Linux (RHEL) (*.rpm) packages. Significant differences between the supported platforms are pointed out.

Install Java

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

RHEL or CentOS

Terminal window
sudo yum install java-17-openjdk

Debian or Ubuntu

Terminal window
sudo apt-get install openjdk-17-jre

Amazon Linux

Terminal window
sudo dnf install java-11-openjdk

Install connector package

Go to the Aerospike Enterprise downloads site to download the connector package for your platform and install it.

RHEL (8 and 9), CentOS, etc.

Terminal window
sudo rpm -i aerospike-jms-outbound-4.2.10-1.noarch.rpm

Debian, Ubuntu, etc.

Terminal window
sudo dpkg -i aerospike-jms-outbound-4.2.10.all.deb

Amazon Linux etc.

Terminal window
sudo rpm -i aerospike-jms-outbound-4.2.10-1.noarch.rpm

Verify/update connector configuration

The connector’s configuration can be found in the /etc/aerospike-jms-outbound/ directory. For details on how to configure the JMS provider and enable TLS, see the configuration guide.

Start the connector

The connector package includes a Systemd service definition. The installation procedure creates an aerospike-jms-outbound service.

Enable the connector to start on system startup or reboot:

Terminal window
$ sudo systemctl enable aerospike-jms-outbound

To start the connector service run:

Terminal window
$ sudo systemctl start aerospike-jms-outbound

Configure Connector

Feedback

Was this page helpful?

What type of feedback are you giving?

What would you like us to know?

+Capture screenshot

Can we reach out to you?