Skip to main content

A Implementation - Little Bit of Linking

In order to resolve links, the Linking API must be invoked on the Content Delivery server, when the page is being quested. This is also called frying. This ensures that links are always displayed only if the target page is available (i.e. published).

In DD4T, when we resolve a Component link, we call one of the ResolveLink methods of the ILinkFactory factory.

public interface ILinkFactory
    string ResolveLink(string componentUri);
    string ResolveLink(string sourcePageUri, string componentUri,
            string excludeComponentTemplateUri);

    ICacheAgent CacheAgent { get; set; }
    ILinkProvider LinkProvider { get; set; }

Since we are using strongly-typed models, it means we can easily include this logic in the model itself. This means we can provide a lazy loaded property on the ModelBase class that calls the ILinkFactory.ResolveLink method using the Id property of the model.

public class ModelBase : IComparable<ModelBase>
    public string Id { get; set; }
    public ISchema Schema { get; set; }
    public string Title { get; set; }

    private string _resolvedUrl;
    public string ResolvedUrl
            if (string.IsNullOrEmpty(_resolvedUrl))
                ILinkFactory linkFactory =
                _resolvedUrl = linkFactory.ResolveLink(Id);

            return _resolvedUrl;

The property ResolvedUrl gives us the URL of the page where this model appears on, if available. Otherwise, it returns null.


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