Skip to main content

Yet Another Event System - Revisited

Image
By
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.

Installation

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

Configuration

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

<configuration>
  <appSettings>
    <!-- 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"/>
  </appSettings>
</configuration>

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;

Usage

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);
    }
}


Labels:

Comments

Post a Comment

Popular posts from this blog

Scaling Policies

By
This post is part of a bigger topic Autoscaling Publishers in AWS . In a previous post we talked about the Auto Scaling Groups , but we didn't go into details on the Scaling Policies. This is the purpose of this blog post. As defined earlier, the Scaling Policies define the rules according to which the group size is increased or decreased. These rules are based on instance metrics (e.g. CPU), CloudWatch custom metrics, or even CloudWatch alarms and their states and values. We defined a Scaling Policy with Steps, called 'increase_group_size', which is triggered first by the CloudWatch Alarm 'Publish_Alarm' defined earlier. Also depending on the size of the monitored CloudWatch custom metric 'Waiting for Publish', the Scaling Policy with Steps can add a difference number of instances to the group. The scaling policy sets the number of instances in group to 1 if there are between 1000 and 2000 items Waiting for Publish in the queue. It also sets the
Post a Comment
Read more

Running sp_updatestats on AWS RDS database

By
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
1 comment
Read more

Toolkit - Dynamic Content Queries

By
This post if part of a series about the  File System Toolkit  - a custom content delivery API for SDL Tridion. This post presents the Dynamic Content Query capability. The requirements for the Toolkit API are that it should be able to provide CustomMeta queries, pagination, and sorting -- all on the file system, without the use third party tools (database, search engines, indexers, etc). Therefore I had to implement a simple database engine and indexer -- which is described in more detail in post Writing My Own Database Engine . The querying logic does not make use of cache. This means the query logic is executed every time. When models are requested, the models are however retrieved using the ModelFactory and those are cached. Query Class This is the main class for dynamic content queries. It is the entry point into the execution logic of a query. The class takes as parameter a Criterion (presented below) which triggers the execution of query in all sub-criteria of a Criterio
Post a Comment
Read more