Skip to main content

REL Standard Tag Library - Installation

This post explains the steps to install RSTL on your Tridion presentation server.

For more information about RSTL, check out my post REL Standard Tag Library.

To download RSTL go to my Google Code page. Always use the latest JAR.

Prerequisites

Although installation itself is very simple, there are some prerequisites:
  • Install and configure a Content Delivery server. This can be either a Java or .NET.
    • If CD API is used, make sure you call the PageContentAssembler to assemble Pages and ComponentPresentationAssembler to assemble Component Presentations. This ensures the REL tags are executed;
    • If CD Web Service (OData) is used, make sure all content is published to the CD DB;
  • Create and configure a Deployer that publishes the content and/or metadata to the CD DB:
    • For CD API, content does not have to be in the CD DB, but in order to execute REL tags it should be;
    • for OData, all content and metadata should be in the CD DB;
  • Create and configure a Publication Target that uses the defined Deployer;

Installation

  • Copy the JAR (rel-standard-tag-library-x.y.jar) to your WEB-INF/lib folder (for Java) or to bin/lib (for .NET);
  • Edit your cd_dynamic_conf.xml file (located either in WEB-INF/classes or bin/classes) and add the following line just below the <TCDLEngine>:
        <TagBundle Resource="rel-standard-tag-library.xml" />
  • Restart the application server;


Comments

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: 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...

REL Standard Tag Library

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

Publish Binaries to Mapped Structure Groups

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