Skip to main content

Yet Another Event System - Revisited

As a followup of my previous post Yet Another Event System?, it is time for a follow up on the code and examples.

The code has been added to Google Code and it's available for free at YAES source code. You can simply download the entire solution and start coding. If you're only interested in the main functionality class, go directly to ConfigurationManager.cs.


This is a normal Event System installation process:
  • Copy the compiled Event System DLL to a location of your choosing
  • Reference the DLL from file [Tridion_Home]\conf\Tridion.ContentManager.config, in section configuration / extensions / add, attribute assemblyFileName
  • Copy a .config file to the same directory where your Event System DLL is located, and name it the same as your DLL, but with extension .config
  • Restart Tridion processes. For knowing exactly which process to restart, have a look at my earlier post Debugging a Tridion 2011 Event System


The .config file along with the DLL contains a few configuration options:

    <!-- Amount of minutes to keep a loaded Configuration dictionary in the cache -->
    <add key="SystemComponentCacheMinutes" value="5"/>

    <!-- Where to read the System Component from (Publication, Current, TcmUri or WebDavUrl). Multiple values are comma separated -->
    <add key="SystemComponentLocation" value="Publication"/>

    <!-- Which metadata field contains a Component Link to the SystemComponent. Multiple fields separated by commas -->
    <add key="SystemComponentField" value="Configuration,conf"/>

    <!-- Search for System Component recursively (going up into the parent Folder/SG)? -->
    <add key="SystemComponentRecursive" value="true"/>

    <!-- When merging several System Components, should it override values for the same key? -->
    <add key="SystemComponentOverride" value="true"/>

The configuration keys have the following meaning and possible values:
  • SystemComponentCacheMinutes - the amount of minutes to keep a loaded Configuration object into memory cache;
  • SystemComponentLocation - the location where the configuration Component is located in Tridion CM. Possible multiple values comma-separated are:
    • Publication - denotes the configuration Component is to be read from the Publication Metadata. Specify then also key SystemComponentField;
    • Current - denotes the configuration Component to be read from the Metadata of the current item's Organizational Item (so either its parent Folder or Structure Group). The current item is the item for which the Event System code is performing the action. Specify then also key SystemComponentField;
    • TcmUri - represents an TcmUri string to read the configuration Component from;
    • WebDavUrl - represents a WebDavUrl string to read the configuration Component from;
  • SystemComponentField - comma separated field names to attempt to read the configuration Component from. Each of these values are attempted to be accessed in the metadata of the Organizational Item or Publication. The configuration Component is assumed to be a Component Link from this metadata field to the actual configuration Component;
  • SystemComponentRecursive - string denoting a boolean value (true or false), which instructs whether the configuration Component should be attempted to be read recursively up into the parent Organizational Item until the Root is found;
  • SystemComponentOverride - string denoting a boolean value (true or false), which instructs whether the configuration values found should be overridden in case the same configuration key is encountered. If false, then the value of an existing key will be set once and shall not be overridden;


Use the static method GetInstance(RepositoryLocalObject) to get the latest up-to-date ConfigurationManager singleton instance. This method also checks the cache and reloads the configurations when/if needed. Execute this method from each Event System interception (call-back) method.

[TcmExtension("Yet Another Event System")]
public class EventSystem : TcmExtension {

    private ConfigurationManager configManager;

    public EventSystem() {
        EventSystem.Subscribe<Component, CheckInEventArgs>(OnComponentCheckIn, EventPhases.Initiated);
        EventSystem.Subscribe<TemplateBuildingBlock, CheckInEventArgs>(OnTBBSavePre, EventPhases.TransactionCommitted);

    private void OnComponentCheckIn(Component component, CheckInEventArgs args, EventPhases phase) {
        configManager = ConfigurationManager.GetInstance(component);

    private void OnTBBSavePre(TemplateBuildingBlock tbb, CheckInEventArgs args, EventPhases phase) {
        configManager = ConfigurationManager.GetInstance(tbb);


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