Home > INTERWOVEN > Interwoven TeamSite Templating

Interwoven TeamSite Templating

May 24, 2010

Interwoven TeamSite Templating provides an easy configurable way to capture, edit & store the data input by content contributors and define the look and feel of the captured data. The data capture process is separate and independent of the data presentation process, hence allowing unlimited usage of the captured data. The independent nature of the presentation process allows one to define different appearances for the same data depending on where and how the data is being used.

In TeamSite Templating the data is captured using a Data Capture Template(DCT). The data captured using a DCT is saved in an XML format in a file called as a Data ContentRecord(DCR). The DCR’s act as a source of data for Presentation Templates. A Presentation Template can use multiple DCR’s to generate a page(this page can be a JSP, ASP, XML, etc. as per the configuration defined).

Getting started – Configuring templating.cfg

Before creation of a DCT and Presentation templates associated with the data type we define some configurations in templating.cfg.

templating.cfg is the main TeamSite Templating configuration file. It is present at the following location:
/iw-home/local/config

The file is in an XML format and has information related to the following:
1. Data Categories and Types available for Templating
2. File extension of the files generated using a template
3. Mapping between presentation template and a data type
4. Mapping between files generated using presentation templates and the branch on which the files can be generated
5. Users or roles permitted to create or edit a DCR for a data type

Following is a sample of file templating.cfg containing a single category News which has only a single data type sports_news.

A template, Sports_Page_Template.tpl is defined under data type sports_news which will generate a file with extension .html .

Points to be noted:

The data storage hierarchy will be as follows:

1. There should be a directory named ‘templatedata’ inside your workarea.
2. Category ‘News’ will have a directory named ‘News’ representing the category inside directory ‘templatedata’ defined inside a branch.
3. Data type ‘sports_news’ will have a directory named ‘sports_news’ representing the data type inside directory ‘News’.
4. Inside directory ‘sports_news’ there will be two directories present namely:-
5. data – This will store the Data Content Records
6. presentation – This will store the templates for the data type

The following are important pointers related to tags used in templating.cfg

1. Tag contains only one tag
2. The definition of template is present inside tag . At least one tag should be present inside tag.
3. Attribute ‘extension’ is used to specify the extension of files generated using the template defined inside tag
4. Tag is used to define the location of presentation template file.
5. Tag is used to specify the output location of generated files

%d bloggers like this: