Posts Tagged ‘Teamsite’

Important Terms in Interwoven Teamsite

May 20, 2010 Comments off

Below are few of the important Terms used extensively in Teamsite :

Data Capture

The Data Capture sub-system enables the user to work with forms which are created through a ‘Data Capture Template’ (DCT). Once the user fills the required content in the DCT and saves it, a ‘Data Capture Record’ (DCR) is generated, which gets stored in the tool’s file system. This data is saved as an XML and is utilized to fill the ‘Presentation Template’ which governs the look of the final web page.
This sub-system can be employed in a TeamSite Templating Browser or a java environment.

The ‘Data Capture Subsystem’ consists of a series of Java applications to carry out the following tasks:

o Study datacapture.cfg and templating.cfg files and decide what data a user should be able to view
through WebDesk or WebDeskPro.
o Deduce the input of the person entering the data.
o Save the data entered in the required format.

Data Capture Template

A ‘Data Capture Template’ (DCT) consists of an XML file named datacapture.cfg which specifies the form to be used to get the data content from its subscribers.

It comprises of:

o Category
o Type

These specify what type of data the DCT uses. The content entered in the DCT is saved as an XML on TeamSite. One DCT can be used to generate multiple DCRs.

Data Presentation

Once the DCR gets created after the data entry in the DCT, the page can be generated through the page generation sub-system reachable by the command line. This enables the user to view the required data in the required format. An output file can also be created that uses data from more than one DCRs and database queries. This output file may also be deployed to a web server using OpenDeploy.

Presentation Template

A ‘Presentation Template’ specifies how the data entered looks on the generated page.

The data present in this template is obtained from the DCRs which was initially entered in the DCT. The TeamSite Templating can also be designed to fill the presentation template with selective information from a relational database.

These can also be used with:

o Component templates – i.e., a component of another presentation template or a nested template.
o A single DCR to fill multiple presentation templates, all having a different appearance and display.

It uses an XML file with extension .tpl.

The ‘Page Generation System’ is a simple sequence of programs and libraries, which helps to:

o Examine the presentation template and templating.cfg configuration files and
decide the user should be able to view through the TeamSite GUI.
o Deduce the input of the person entering the data.
o Use the DCR and presentation templates to generate the required results.

Data Content Record

A Data Content Record ‘DCR’ is XML file. It has the design information along with the data entered in the DCTs. The name of the DCR is user specific.

Categories: INTERWOVEN Tags: , , , , , ,

An Introduction to Autonomy Interwoven Teamsite

May 13, 2010 Comments off

Autonomy Interwoven Teamsite is a Content Management Solution. Team Site is a tool used for Web Content Management.This tool employs a hybrid architecture which offers file and database versioning, a user friendly workflow engine, support for windows and a high availability.

TeamSite Templating renders a highly configurable way to:

o Enable the user to enter, edit and store data or input.
o Specify the look and feel of the data to be shown.
o Incorporate other interwoven features/products like TeamSite Workflow and DataDeploy, etc with the data entered.

Some of its important features include :

1. Hybrid Architecture – The important features of this include:

• The ability for using file content without much expense of time and effort.
• Proper management of the content.
• Automatic storage of content to a database whenever it is created or updated.

2. An Easy Workflow Engine– This helps in:

• Improving management of project and guarantee reliability of the data.
• It has a better advanced user interface.
• Fast identification of the task assigned to individuals and manages them.
• Results in a shorter project development cycle.
• Offers more command over the production process.

3. Corroborate with Microsoft FrontPage 2000 Server Annexes – It provides:

• Reinforcement for Microsoft FrontPage 2000 Server annexes.
• Gives a better admittance to FrontPage Webs and Visual InterDev projects from inside the tool itself.

4. Multi-byte Sustenance– This includes:

• Allows both single-byte and multi-byte content to be entered and shown.
• Provides metadata management in topical dialect enabling the matter to be comfortably searched and utilized across multiple enterprises.
• Allows management of the entire material/content lifecycle in local dialect.

5. High Availability (HA) – The Team Site Server is highly accessible and provides:

• Higher security for the business information.
• Safeguard the content present in TeamSite by regularly saving the in-cache content to the disk enabling fast data retrieval.

6. Hardware Requirements – The following should be kept in mind:

• Dual CPU server should be used if data record searches are to be employed.
• For the Java based interface, an extra 60MB space is needed.
• The java templating on the client machine needs 20MB space.
• For Solaris, it can be run on Sparc/ UltraSparc platforms.

For more information Visit Autonomy Interwoven!

%d bloggers like this: