Chapter 2. Before You Begin
2.1. Comparison: Red Hat JBoss A-MQ and A-MQ for OpenShift Image
This topic details the differences between the regular release of JBoss A-MQ and the A-MQ for OpenShift image, and provides instructions specific to running and configuring the A-MQ for OpenShift image. Documentation for other JBoss A-MQ functionality not specific to the A-MQ for OpenShift image can be found in the Red Hat JBoss A-MQ documentation on the Red Hat Customer Portal.
Differences between the regular release of JBoss A-MQ and the A-MQ for OpenShift image:
- The Karaf shell is not available.
- The Fuse Management Console (Hawtio) is not available.
- To connect to the A-MQ web console, click the Connect button in the A-MQ pod of the OpenShift web console, or the Open Java Console button in OpenShift Container Platform.
Configuration of the broker can be performed:
- using parameters specified in the A-MQ application template, as described in Section 6.1, “Application Template Parameters for Persistent Configuration”.
- using the S2I (Source-to-image) tool, as described in Section 6.2, “Configuration using S2I”.
- Clients for the A-MQ xPaaS image need to specify the OpenShift API port (443) when setting the broker URL for SSL connections. Otherwise, A-MQ will attempt to use the default SSL port (61617).