Install the Aerospike Pulsar Outbound Connector
Prerequisites
Aerospike Database change notification configuration
Deploying on Docker
Aerospike provides Docker images for the Aerospike connect for Pulsar on Docker Hub.
sudo docker run \ -v <path to local aerospike-pulsar-outbound.yml>:/etc/aerospike-pulsar-outbound/aerospike-pulsar-outbound.yml \ container.aerospike.com/aerospike/aerospike-pulsar-outbound:3.3.12
<path to local aerospike-pulsar-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 11 or later. Both Oracle and OpenJDK Java Runtime Environments are supported.
Java 17 is supported since Pulsar outbound version 2.2.0 and later.
Installation
The installation steps below apply to both the Debian (*.deb) and RHEL (*.rpm) packages. Where there are significant differences between the supported platforms, this will be pointed out. Multiple instances of the connector are required based on your throughput and latency requirements.
Install Java 11 or later version
The Aerospike Connect for Pulsar package does not include a Java runtime environment. Most supported platforms provide official JDK 11 packages. For platforms that do not, you can get Oracle’s JDK 11 builds from jdk.java.net/11/.
RHEL (8 and 9), CentOS, etc.
sudo yum install java-11-openjdk
Debian, Ubuntu, etc.
sudo apt-get install openjdk-11-jre
Amazon Linux etc.
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.
sudo rpm -i aerospike-pulsar-outbound-3.3.12-1.noarch.rpm
Debian, Ubuntu, etc.
sudo dpkg -i aerospike-pulsar-outbound-3.3.12.all.deb
Amazon Linux, etc.
sudo rpm -i aerospike-pulsar-outbound-3.3.12-1.noarch.rpm
Verify/update connector configuration
The connector’s configuration can be found in the /etc/aerospike-pulsar-outbound/
directory. For details on how to configure the Pulsar provider, enable
TLS, etc., refer to the configuration guide.
Start the connector
The connector package includes a systemd service definition. The installation procedure creates an aerospike-pulsar-outbound service.
Enable the connector to start on system startup or reboot:
$ sudo systemctl enable aerospike-pulsar-outbound
To start the connector service run:
$ sudo systemctl start aerospike-pulsar-outbound