Skip to main content

Toolkit - A Tridion File System Broker

Image
By
In the following series of posts, I am describing a custom file system storage, called the Toolkit, that mimics the behaviour of the Tridion File System Broker. There are a couple of noticeable differences from the File System Broker in that it:

The Toolkit offers the following functionality:

Backing the Toolkit implementation are the following:
  • Model Factory offering CRUD operations on models backed by a cache for model objects and a file system provider acting as data layer abstraction;
  • File System Provider acting as Data Abstraction Layer that offers CRUD operations between model objects, JSON de-/serializer, JSON files, and the underlying file system;
  • Cache Factory offering EHCache memory storage for frequently used models;
  • Cache invalidation mechanism that removes stale items from cache;
  • Custom indexes and handling logic that provides performance for content queries;
  • Tridion Deployer module and Tridion Storage extension that publish/unpublish the JSON files from the file system;

Each of the modules above are described in following posts.

The Toolkit is written in plain Java without using any additional framework or third party data access / indexing API. The Toolkit does use FasterXML's Jackson JSON API in its interaction with JSON.

Toolkit is available as open source on the GitHub project of this blog (https://github.com/mitza13/yet-another-tridion-blog/tree/master/File System Toolkit). The distributable JARs are available in its /distributable folder.

Some performance metrics of the Toolkit can be found in post Toolkit - Performance.

Installation and configuration steps can be found in post Toolkit - Installation and Configuration.

Examples for using the Toolkit API can be found in post Toolkit - Examples.



Labels:

Comments

Post a Comment

Popular posts from this blog

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...
2 comments
Read more

REL Standard Tag Library

By
The RSTL is a library of REL tags providing standard functionality such as iterating collections, conditionals, imports, assignments, XML XSLT transformations, formatting dates, etc. RSTL distributable is available on my Google Code page under  REL Standard Tag Library . Always use the latest JAR . This post describes each RSTL tag in the library explaining its functionality, attributes and providing examples. For understanding the way expressions are evaluated, please read my post about the  Expression Language used by REL Standard Tag Library . <c:choose> / <c:when> / <c:otherwise> Syntax:     <c:choose>         <c:when test="expr1">             Do something         </c:when>         <c:when test="expr2">             Do something else         </c:when...
2 comments
Read more

Publish Binaries to Mapped Structure Groups

By Unknown
Today's TBB of the Week comes from the high demand in the field to publish binary assets to different mapped Structure Groups. By default SDL Tridion offers two ways of publishing binaries: All binaries publish to a folder defined in your Publication properties; All binaries rendered by a given template publish to a folder corresponding to a given Structure Group; In my view, both cases are terrible, over-simplified and not representing a real use-case. Nobody in the field wants all binaries in one folder and nobody separates binary locations by template. Instead, everybody wants a mapping mechanism that takes a binary and publishes it to a given folder, defined by a Structure Group, and this mapping is done using some kind of metadata. More often than not, the metadata is the TCM Folder location of the Multimedia Component. I have seen this implemented numerous times. So the solution to publish binaries to a given location implies finding a mapping from a TCM Folder to a...
10 comments
Read more