红帽全球峰会2.5. Upgrading a broker instance from 7.5.0 to 7.6.0
The following subsections describe how to upgrade a 7.5.0 broker instance to 7.6.0 for different operating systems.
Starting with AMQ Broker 7.1.0, you can access AMQ Management Console only from the local host by default. To learn about configuring remote access to the console, see Configuring local and remote access to AMQ Management Console.
2.5.1. Upgrading from 7.5.0 to 7.6.0 on Linux
The name of the archive that you download could differ from what is used in the following examples.
Procedure
- Download the desired archive from the Red Hat Customer Portal. Follow the instructions provided in Downloading the AMQ Broker archive.
Change the owner of the archive to the same user that owns the AMQ Broker installation to be upgraded. The following example shows a user called
amq-broker.sudo chown amq-broker:amq-broker amq-broker-7.6.0.redhat-1.zipMove the archive to the directory created during the original installation of AMQ Broker. The following example uses
/opt/redhat.sudo mv amq-broker-7.6.0.redhat-1.zip /opt/redhatAs the directory owner, extract the contents of the compressed archive. In the following example, the user
amq-brokerextracts the archive using theunzipcommand.su - amq-broker cd /opt/redhat unzip amq-broker-7.6.0.redhat-1.zipIf the broker is running, stop it.
<broker_instance_dir>/bin/artemis stopBack up the instance directory of the broker by copying it to the home directory of the current user.
cp -r <broker_instance_dir> ~/(Optional) Note the current version of the broker. After the broker stops, you see a line similar to the one below at the end of the
<broker_instance_dir>/log/artemis.logfile.INFO [org.apache.activemq.artemis.core.server] AMQ221001: Apache ActiveMQ Artemis Message Broker version 2.9.0.redhat-00054 [0.0.0.0, nodeID=554cce00-63d9-11e8-9808-54ee759954c4]Edit the
<broker_instance_dir>/etc/artemis.profileconfiguration file.Set the
ARTEMIS_HOMEproperty to the new directory created when the archive was extracted.ARTEMIS_HOME='/opt/redhat/amq-broker-7.6.0-redhat-1'Edit the
JAVA_ARGSproperty. Add the bootstrap class path argument, which references a dependent file for the log manager.-Xbootclasspath/a:$ARTEMIS_HOME/lib/wildfly-common-1.5.2.Final-redhat-00002.jar
Start the upgraded broker.
<broker_instance_dir>/bin/artemis run(Optional) Confirm that the broker is running and that the version has changed. After starting the broker, open the
<broker_instance_dir>/log/artemis.logfile. Find two lines similar to the ones below. Note the new version number that appears in the log when the broker is live.INFO [org.apache.activemq.artemis.core.server] AMQ221007: Server is now live ... INFO [org.apache.activemq.artemis.core.server] AMQ221001: Apache ActiveMQ Artemis Message Broker version 2.11.0.redhat-00001 [0.0.0.0, nodeID=554cce00-63d9-11e8-9808-54ee759954c4]
Additional Resources
- For more information about creating an instance of the broker, see Creating a broker instance.
-
You can now store a broker instance’s configuration files and data in any custom directory, including locations outside of the broker instance’s directory. In the
<broker_instance_dir>/etc/artemis.profilefile, update theARTEMIS_INSTANCE_ETC_URIproperty by specifying the location of the custom directory after creating the broker instance. Previously, these configuration files and data could only be stored in theetc/anddata/directories within the broker instance’s directory.
2.5.2. Upgrading from 7.5.0 to 7.6.0 on Windows
Procedure
- Download the desired archive from the Red Hat Customer Portal. Follow the instructions provided in Downloading the AMQ Broker archive.
- Use a file manager to move the archive to the folder you created during the last installation of AMQ Broker.
- Extract the contents of the archive. Right-click the .zip file and select Extract All.
If the broker is running, stop it.
<broker_instance_dir>\bin\artemis-service.exe stopBack up the broker using a file manager.
-
Right-click the
<broker_instance_dir>folder and select Copy. - Right-click in the same window and select Paste.
-
Right-click the
(Optional) Note the current version of the broker. After the broker stops, you see a line similar to the one below at the end of the
<broker_instance_dir>\log\artemis.logfile.INFO [org.apache.activemq.artemis.core.server] AMQ221002: Apache ActiveMQ Artemis Message Broker version 2.9.0.redhat-00054 [4782d50d-47a2-11e7-a160-9801a793ea45] stopped, uptime 28 minutesEdit the
<broker_instance_dir>\etc\artemis.profile.cmdand<broker_instance_dir>\bin\artemis-service.xmlconfiguration files. Set theARTEMIS_HOMEproperty to the new directory created when the archive was extracted.ARTEMIS_HOME=<install_dir>Edit the
<broker_instance_dir>\etc\artemis.profile.cmdconfiguration file. Set theJAVA_ARGSenvironment variable to reference the correct log manager version and dependent file.JAVA_ARGS=-Xbootclasspath/%ARTEMIS_HOME%\lib\jboss-logmanager-2.1.10.Final-redhat-00001.jar;%ARTEMIS_HOME%\lib\wildfly-common-1.5.2.Final-redhat-00002.jarEdit the
<broker_instance_dir>\bin\artemis-service.xmlconfiguration file. Set the bootstrap class path start argument to reference the correct log manager version and dependent file.<startargument>-Xbootclasspath/a:%ARTEMIS_HOME%\lib\jboss-logmanager-2.1.10.Final-redhat-00001.jar;%ARTEMIS_HOME%\lib\wildfly-common-1.5.2.Final-redhat-00002.jar</startargument>Start the upgraded broker.
<broker_instance_dir>\bin\artemis-service.exe start(Optional) Confirm that the broker is running and that the version has changed. After starting the broker, open the
<broker_instance_dir>\log\artemis.logfile. Find two lines similar to the ones below. Note the new version number that appears in the log when the broker is live.INFO [org.apache.activemq.artemis.core.server] AMQ221007: Server is now live ... INFO [org.apache.activemq.artemis.core.server] AMQ221001: Apache ActiveMQ Artemis Message Broker version 2.11.0.redhat-00001 [0.0.0.0, nodeID=554cce00-63d9-11e8-9808-54ee759954c4]
Additional Resources
- For more information about creating an instance of the broker, see Creating a broker instance.
-
You can now store a broker instance’s configuration files and data in any custom directory, including locations outside of the broker instance’s directory. In the
<broker_instance_dir>\etc\artemis.profilefile, update theARTEMIS_INSTANCE_ETC_URIproperty by specifying the location of the custom directory after creating the broker instance. Previously, these configuration files and data could only be stored in the\etcand\datadirectories within the broker instance’s directory.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}