6.2 Accessing the demo activemq broker

Disclaimer: This section of the Wiki is ment for participants of the NebulOuS European project

Please read first: https://github.com/eu-nebulous/nebulous/wiki/6.1-Accessing-NebulOuS-dev-K8s

Using kubectl to redirect the activemq ports

To forward local (localhost, 127.0.0.1) to the demo activemq broker you will need to forward various ports on local host to the remote AMQ server. There are multiple ports to consider:

• The management control port, allowing you to connect with a browser to the server to see connected clients and message topics:
   kubectl -n nebulous-playground port-forward service/nebulous-activemq 8161:8161
• The normal port for unencrypted AMQ protocol messages: kubectl -n nebulous-playground port-forward service/nebulous-activemq 5672:5672
• The port for TLS encrypted AMQ protocol messages: kubectl -n nebulous-playground port-forward service/nebulous-activemq 5671:5671 (not currently active)
• A port for the Java Messaging System (JMS): kubectl -n nebulous-playground port-forward service/nebulous-activemq 61616:61616
• All of the above:
  kubectl -n nebulous-playground port-forward service/nebulous-activemq 5672:5672 8161:8161 61616:61616

ActiveMQ connection details

• Address: 127.0.0.1:61616 (JMS protocol) or 127.0.0.1:5672 (AMQ protocol - see above)
• Name: activemq
• Username: admin
• Password: admin

Clients to test the connection

There are unfortunately not a standardised client application that can be used to test the connection to the AMQ server. The following have been identified, but not validated or testing. Feedback is welcome!

• amazonmq-cli is correctly packages so no extra installation of other libraries are necessary, but may no longer be maintained, and it is unclear if it supports the AMQ Protocol or only the JMS protocol.
• AMQCLI would be a type of client that would be good to have, but it seems to assume that you have many libraries installed locally (undocumented), and perhaps it is written to test an AMQ Broker running locally?
• The "A" tool is again quite complete, with a developer community, but it seems to have some internal errors and gave Geir an "ArrayIndexOutOfBoundsException"
• amqp-client-cli is a simple connect-and-publish or connect-and-subscribe tool. Untested. It was mainly written for creating automated messages (cron jobs).
• Fotis has a similar script pushing messages on a topic. We can also use stubs of his middelware to monitor individual topics (full documentation is needed)