Greetings! One of the topics I covered during my Dreamcore presentation on Data Access Techniques with Sitecore CMS was Link Database. While it is a great feature that enables fast and efficient retrieval of item relations, there is one caveat, it requires some maintenance and configuration to be working properly in multi server environment. Many customers face this challenge, and while there is a number of ways you can tackle this, the approach I want to share today seems like the most appropriate to me.
The idea behind the scenes is to separate the Link Database used on the Content Delivery side from the one used on the Content Management side by introducing a second link database. This database will be updated during item publishing. This way if CMS decides to update its own Link DB, the one used on the front-end will not be affected.
So, here is what you need to do:
1. Add the FrontEndLinkDatabase definition below the default <LinkDatabase> in web.config file of the CMS server:
<!-- LINK DATABASE -->
<LinkDatabase type="Sitecore.Data.$(database).$(database)LinkDatabase,
Sitecore.Kernel">
<param connectionStringName="core" />
</LinkDatabase>
<!-- FRONT END LINK DATABASE -->
<FrontEndLinkDatabase type="Sitecore.Data.$(database).$(database)LinkDatabase,
Sitecore.$(database)">
<param desc="connection" ref="connections/web" />
</FrontEndLinkDatabase>
2. Compile the following code that contains two Sitecore event handlers (publish:itemprocessed and publish:itemprocessing)
using System;
using Sitecore.Configuration;
using Sitecore.Links;
using Sitecore.Publishing;
using Sitecore.Publishing.Pipelines.PublishItem;
using Sitecore.Diagnostics;
namespace Sitecore.SharedSource.LinkDatabaseRebuilder
{
public class EventHandler
{
protected static LinkDatabase FrontEndLinkDatabase
{
get
{
return (Factory.CreateObject("FrontEndLinkDatabase", true)
as LinkDatabase);
}
}
public string Database { get; set; }
public void OnItemProcessed(object sender, EventArgs args)
{
var context = ((ItemProcessedEventArgs)args).Context;
Assert.IsNotNull(context,
"Cannot get PublishItem context");
Assert.IsNotNull(FrontEndLinkDatabase,
"Cannot resolve FrontEndLinkDatabase from config");
if (context.PublishOptions.TargetDatabase.Name.Equals(Database))
{
var item = context.PublishHelper.GetTargetItem(context.ItemId);
// if an item was not unpublished,
// the call below will reintroduce the reference
// removed within OnItemProcessing method
if (item != null)
{
FrontEndLinkDatabase.UpdateReferences(item);
}
}
}
public void OnItemProcessing(object sender, EventArgs args)
{
var context = ((ItemProcessingEventArgs)args).Context;
Assert.IsNotNull(context,
"Cannot get PublishItem context");
Assert.IsNotNull(FrontEndLinkDatabase,
"Cannot resolve FrontEndLinkDatabase from config");
if (context.PublishOptions.TargetDatabase.Name.Equals(Database))
{
if (context.Action == PublishAction.DeleteTargetItem)
{
var item = context.PublishHelper.GetTargetItem(context.ItemId);
Assert.IsNotNull(item, "Source item cannot be found");
FrontEndLinkDatabase.RemoveReferences(item);
}
}
}
}
}
3. Last thing to do is to define the two event handler mapping in web.config.
<events>
<event name="publish:itemProcessing">
<handler type="Sitecore.SharedSource.LinkDatabaseRebuilder.EventHandler,
Sitecore.SharedSource.LinkDatabaseRebuilder" method="OnItemProcessing">
<database>web</database>
</handler>
</event>
<event name="publish:itemProcessed">
<handler type="Sitecore.SharedSource.LinkDatabaseRebuilder.EventHandler,
Sitecore.SharedSource.LinkDatabaseRebuilder" method="OnItemProcessed">
<database>web</database>
</handler>
</event>
</events>
That’s all you need to do. For the sake of simplicity, here is the link to the whole VS project where you can find the auto-include file.
While this solution has been tested on 6.2, it is expected to work on all Sitecore 6 installations.
Let me know if it does not ;-)
![no_filter[1]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgie9zD_uUPJ1nr8vNztNMW0hr38Wpba1DzXgcazaGZ46Aq-u87xlt43qHwqB8sxQtT6-OfT_dSdeZoUfQeocKyYQokuY5IHgevgLv0rPg1nTHX0Wky1Yr6i1W11mWHHft4JOkL/s1600-h/no_filter%5B1%5D%5B4%5D.png "no_filter[1]")
