Skip to main content

Setup Apache ActiveMQ

This is a follow up of my previous post JMS Cache Channel Setup. The goal is to configure JMS cache invalidation for Tridion Content Delivery. In my previous post I was describing how to configure the Tridion Deployer to use JMS technology and to post cache notification messages to an Apache ActiveMQ server. This post describes the steps I took to install and configure ActiveMQ on my machine.

I started my endeavor without having any prior experience with ActiveMQ. To my surprise, the installation was a breeze and took me about 20 minutes to get everything running.

I started by visiting the home of ActiveMQ -- activemq.apache.org. The latest version as of the day was 5.10.0. I followed the no-nonsense guide on the home page and I first downloaded ActiveMQ. I use a Mac (like every freelancer who respects himself :-p) and I personally love FreeBSD, so I downloaded the Unix/Linux/Cygwin Distribution. Namely, a file named apache-activemq-5.10.0-bin.tar.gz.

The Getting Started Guide instructs you to:
  • decompress the archive to a folder of your choice (I used /srv). Execute the command
        tar zxvf activemq-5.10.0-bin.tar.gz

This creates folder /srv/apache-activemq-5.10.0
  • if activemq start-up script is not executable, make it executable by executing the following:
        > cd /srv/apache-activemq-5.10.0/bin
        > chmod 755 activemq

Next, you can proceed to configure ActiveMQ. This is where the Getting Started Guide is a bit inaccurate. Before being able to run ActiveMQ, you need to run the 'setup' command. This will create a configuration file in the location of your choice. I used my homedir ~/.activemqrc and executed the following:

        > cd /srv/apache-activemq-5.10.0
        > bin/activemq setup ~/.activemqrc

And really that's all, folks. You should now be able to run ActiveMQ, start up your Deployer and see it connect to the JMS server (check the cd_core log in debug mode).

Start command:

        > bin/activemq start

Shutdown command:

        > bin/activemq stop

Check running state:

        > bin/activemq status

Don't forget there is also a web console with default user & pass admin/admin, and it's very helpful in monitoring the server:

        http://localhost:8161/admin


Comments

Popular posts from this blog

Running sp_updatestats on AWS RDS database

Part of the maintenance tasks that I perform on a MSSQL Content Manager database is to run stored procedure sp_updatestats . exec sp_updatestats However, that is not supported on an AWS RDS instance. The error message below indicates that only the sa  account can perform this: Msg 15247 , Level 16 , State 1 , Procedure sp_updatestats, Line 15 [Batch Start Line 0 ] User does not have permission to perform this action. Instead there are several posts that suggest using UPDATE STATISTICS instead: https://dba.stackexchange.com/questions/145982/sp-updatestats-vs-update-statistics I stumbled upon the following post from 2008 (!!!), https://social.msdn.microsoft.com/Forums/sqlserver/en-US/186e3db0-fe37-4c31-b017-8e7c24d19697/spupdatestats-fails-to-run-with-permission-error-under-dbopriveleged-user , which describes a way to wrap the call to sp_updatestats and execute it under a different user: create procedure dbo.sp_updstats with execute as 'dbo' as...

REL Standard Tag Library

The RSTL is a library of REL tags providing standard functionality such as iterating collections, conditionals, imports, assignments, XML XSLT transformations, formatting dates, etc. RSTL distributable is available on my Google Code page under  REL Standard Tag Library . Always use the latest JAR . This post describes each RSTL tag in the library explaining its functionality, attributes and providing examples. For understanding the way expressions are evaluated, please read my post about the  Expression Language used by REL Standard Tag Library . <c:choose> / <c:when> / <c:otherwise> Syntax:     <c:choose>         <c:when test="expr1">             Do something         </c:when>         <c:when test="expr2">             Do something else         </c:when...

Publish Binaries to Mapped Structure Groups

Today's TBB of the Week comes from the high demand in the field to publish binary assets to different mapped Structure Groups. By default SDL Tridion offers two ways of publishing binaries: All binaries publish to a folder defined in your Publication properties; All binaries rendered by a given template publish to a folder corresponding to a given Structure Group; In my view, both cases are terrible, over-simplified and not representing a real use-case. Nobody in the field wants all binaries in one folder and nobody separates binary locations by template. Instead, everybody wants a mapping mechanism that takes a binary and publishes it to a given folder, defined by a Structure Group, and this mapping is done using some kind of metadata. More often than not, the metadata is the TCM Folder location of the Multimedia Component. I have seen this implemented numerous times. So the solution to publish binaries to a given location implies finding a mapping from a TCM Folder to a...