...
Setup Fedora to Talk to External ActiveMQ
You might wish to use an external ActiveMQ instead of Fedora's built-in one. This offers easier access to the ActiveMQ web console, the ability to upgrade ActiveMQ independently of Fedora, and the ability to distribute messaging across servers (among other possible benefits). The instructions below offer one possible approach to achieving this setup.
Download the latest ActiveMQ 5 Linux .tar.gz from https://activemq.apache.org/components/classic/download
...
- Edit /opt/activemq/conf/activemq.xml and change port numbers in the transportConnectors section (to avoid conflicts with Fedora’s built-in ActiveMQ; feel free to choose different port numbers as needed, just replace below as needed):
- 61616 -> 41616
- 61613 -> 41613
- Start and enable the service: sudo systemctl enable activemq ; sudo systemctl start activemq
- Edit /opt/fedora/fcrepo.properties and add some properties to customize the configuration and file location for the internal Fedora ActiveMQ (feel free to choose different file paths as appropriate to your Fedora setup):
- fcrepo.activemq.configuration=file:///opt/fedora/config/activemq.xml
- fcrepo.activemq.directory=/opt/fedora/queue
- Create /opt/fedora/config/activemq.xml (this is the default Fedora ActiveMQ configuration with a fedora_bridge network connector added to forward messages to port 41616):
...
- Reconfigure Camel Toolbox by editing /opt/fedora/config/fcrepo-camel-toolbox.properties and adding:
- jms.brokerUrl=tcp://localhost:41616
- Restart Camel Toolbox: (e.g., if you have set it up as a service: sudo systemctl restart cameltoolbox)