Skip to content

Latest commit

 

History

History
33 lines (26 loc) · 1.85 KB

README.md

File metadata and controls

33 lines (26 loc) · 1.85 KB
Raw

Activemq Artemis

Introduction

  • Activemq Artemis is insalled using helm chart that has been slightly modified from the original.
  • Activemq Artemis runs in master-slave configuration with failover and failback features.
  • Persistence is enabled by default.
  • On AWS an internal load balancer (LB) is spawned as per settings in values.yaml.
  • The LB's address may be used by ABIS to connect to broker on port 61616.
  • For web console, enable access via MOSIP internal facing LB via ingress. See ingress settings in values.yaml

Domain name

Create a sub-domain like activemq.sandbox.xyz.net and point it to internal load balancer. Access to activemq must NOT be opened to public. It is assumed that the sub-domain and hosts have been defined in global configmap as given here

Install

  • Review values.yaml.
  • Install
./install.sh
  • Master/slave: Note that after successful installation you will see Artemis master pod in 2/2 state while slave pod will continue to be in 1/2 state. This is the high-availability master-slave configuration. If master fails, the slave will become 2/2 receiving traffic from Artemis service and vice-a-versa. You will see "readiness probe failed" message for the slave pod - this is normal and expected.

Web console

  • Console url: https://activemq.your-domain.com
  • Default username: artemis
  • Password: Run get_pwd.sh

ABIS connection to broker

ABIS must connect to internal LB address (or activemq.your-domain.com) over port 61616.

CLI

  • Activemq command line utility may be downloaded from here.
  • Activemq port 61616 is not accessible externally, you must run the same from a machine that has access to internal load balancer.