The installActiveMQ installation script will create an installation directory $CONNECT/activemq-workspace which will be the installed and configured instance of the ActiveMQ container.
-
Once installed, do not delete the activemq-workspace directory as it contains the active configuration for the ActiveMQ container.
-
If you re-run or need to re-deploy ActiveMQ, the installActiveMQ script will delete the activmq-workspace directory, volumes and other configuration it created previously.
The script will not remove the ActiveMQ stack if it is already running. You must
remove it first and then run the script.
-
The installation script does not have re-try logic, failure to answer a question could exit the script. When this occurs, execute the script again to complete the installation successfully.
Follow the steps below:
-
Run the installActiveMQ.sh script.
-
Answer Y to proceed with the installation. Any prior installed ActiveMQ docker components will be removed.
-
Enter the value to set the Encryption passphrase. This will be used to encrypt other ActiveMQ passwords.
-
Enter the value for _JMX1_, this will be used to set the JMX username.
-
Enter the value for _JMX2_, this will be used to set the JMX user’s password,
-
Enter the value for _CREDS1_, this will be used to set the ActiveMQ’s admin user’s password.
-
Enter the value for _CREDS2_, this will be used to set the ActiveMQ’s read/write user’s password.
-
Enter the value for _CREDS3_, this will be used to set the ActiveMQ’s read-only user’s password.
-
Enter the value for _CREDS4_, this will be used to set the keystore password. The password must be at least 6 characters long. The script will exit if the minimum length is not satisfied.
-
Enter the value for _CREDS5_, this will be used to set the truststore password. The password must be at least 6 characters long. The script will exit if the minimum length is not satisfied.
The installation script will now ask questions to build a keystore and truststore which will be used for secured communication between ActiveMQ and the other connect components.
-
The installer will confirm the machines fully qualified hostname. For example, "connect.domain.com"
-
This needs to be a valid fully qualified name that can be accessed by DNS.
-
Later in the installation, while configuring the Connect Dispatcher, Agent, and LogAgent, you must provide a brokerURL in the form ‘failover:ssl://[host]:61617’.
The [host] setting must be the fully qualified hostname entered here. If there is
a difference in the host setting, the secured connection to ActiveMQ will be denied.
If the name is incorrect, enter n and you will be asked to provide a correct name.
-
-
Confirm the fully qualified hostname again.
-
Enter the name of your organization unit.
-
Enter the name of your organization.
-
Enter the name of your City or Locality.
-
Enter the name of your State or Providence.
-
Enter the two-letter country code.
-
Confirm the "Distinguished Name" that will be used in the TLS certificate.
The installer will create the TLS artifacts and required Docker volumes.
-
Confirm that you want to deploy the ActiveMQ container
The installation will deploy and start the ActiveMQ Docker container.
The location of the amq-client.ts will be displayed. This file is required during the installation of the Dispatcher, Agent, and LogAgent.
-
Verify that the service is provisioned by issuing the host shell command:
docker service ls
When the service has provisioned correctly, the count under ‘REPLICAS’ must read 1/1.