Skip to main content

Using Amazon SQS for Out-Scaled Deployers

When a Deployer Receiver receives a transport package, it notifies the Deployer Workers there is 'work' for them to do. This notification can take the form of JMS messages sent using some kinds of queuing mechanism. This post describes the Amazon Simple Queuing Service (SQS) to send these notifications. The Deployer workers receive these messages from SQS and they start deploying/undeploying the package.

In order to setup this notification system, we must first create the SQS queues and configure them across the Deployer Receiver and all Deployer Workers.

Start by creating Standard Queues using all default properties. We need 3 queues (commit, content, and prepare):

Once the SQS queues are in place, we can configure the Deployers to use them in the file deployer-config.xml. Amazon gives us the queues URLs. We need to specify the URL base separately, and then simply name the queues individually, as per below:

    <Queue Default="true" Verbs="Content" Adapter="JMS" Id="mihai-content">
        <Property Name="Workers" Value="16"/>
    <Queue Verbs="Commit,Rollback" Adapter="JMS" Id="mihai-commit">
        <Property Name="Workers" Value="16"/>
    <Queue Verbs="Prepare" Adapter="JMS" Id="mihai-prepare">
        <Property Name="Workers" Value="16"/>

    <Adapter Id="JMS">
        <Property Name="JMSConnectionFactoryBuilderClass"
        <Property Name="JMSUri" Value=""/>
        <Property Name="Username" Value="username"/>
        <Property Name="Password" Value="password"/>
        <Property Name="ReceiveTimeout" Value="200"/>

The properties Username and Password represent the AWS account credentials and they can be found in AWS user security settings.

The property Workers specifies the number of worker threads for each queue. Values that perform best are around 10-20 worker threads. Performance degrades using lower values and there isn't any significant performance gain when using higher values.


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: I stumbled upon the following post from 2008 (!!!), , 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

Content Delivery Monitoring in AWS with CloudWatch

This post describes a way of monitoring a Tridion 9 combined Deployer by sending the health checks into a custom metric in CloudWatch in AWS. The same approach can also be used for other Content Delivery services. Once the metric is available in CloudWatch, we can create alarms in case the service errors out or becomes unresponsive. The overall architecture is as follows: Content Delivery service sends heartbeat (or exposes HTTP endpoint) for monitoring Monitoring Agent checks heartbeat (or HTTP health check) regularly and stores health state AWS lambda function: runs regularly reads the health state from Monitoring Agent pushes custom metrics into CloudWatch I am running the Deployer ( installation docs ) and Monitoring Agent ( installation docs ) on a t2.medium EC2 instance running CentOS on which I also installed the Systems Manager Agent (SSM Agent) ( installation docs ). In my case I have a combined Deployer that I want to monitor. This consists of an Endpoint and a

Debugging a Tridion 2011 Event System

OK, so you wrote your Tridion Event System. Now it's time to debug it. I know this is a hypothetical situtation -- your code never needs any kind of debugging ;) but indulge me... Recently, Alvin Reyes ( @nivlong ) blogged about being difficult to know how exactly to debug a Tridion Event System. More exactly, the question was " What process do I attach to for debugging even system code? ". Unfortunately, there is no simple or generic answer for it. Different events are fired by different Tridion CM modules. These modules run as different programs (or services) or run inside other programs (e.g. IIS). This means that you will need to monitor (or debug) different processes, based on which events your code handles. So the usual suspects are: dllhost.exe (or dllhost3g.exe ) - running as the MTSUser is the SDL Tridion Content Manager COM+ application and it fires events on generic TOM objects (e.g. events based on Tridion.ContentManager.Extensibility.Events.CrudEven