Posts Tagged ‘Page’

Today, we will see the significance of ElementCatalog and SiteCatalog tables, which we might have seen at many situations.

Firstly, the ElementCatalog and SiteCatalog are two important tables which are present in the Content Server Database.

When we code a Template or a CSElement, the actual ELEMENT is stored in the ElementCatalog table. That is, the code which write (JSP / XML / HTML) will be stored in this ElementCatalog table.

When we give a name for the Element, either in the Template creation, or SiteEntry creation, the PAGENAME will be stored in the SiteCatalog table. That is, the SiteEntry holds the names of the pages and pagelets.

Hence, Each row in the SiteEntry points to an entry in the ElementCatalog.

The Element in the ElementCatalog is called the ROOT ELEMENT, which is being pointed by the Page in SiteCatalog.





We will see how the process of rendering happens, basing on the page name being requested through browser.

  1. I have entered the following URL in the browser.
  2. Here, the page name is MySite/Home.
  3. Content server looks up the SiteCatalog table for the entry : MySite/Home
  4. From there, basing on the entry,  it will invoke the corresponding entry in the ElementCatalog table.
  5. The Element is executed. If caching is enabled, the output is cached.
  6. Output is rendered in the browser.

In this way, the SiteElement and ElementCatalog form crucial part in rendering the pages.

The term PAGE constitutes a very important concept in FATWIRE.

There are a few terminologies in Fatwire related to Page, such as PAGE, PAGELET , PAGE NAME, PAGE ASSET.

Really… they are confusing. At least, I’m very much confused with these terminologies in the beginning. We will discuss the basic differences between these terminologies, so that we will get some clear cut idea, and we will know when to use which term.

1. PAGELET: A Pagelet is the result of an HTTP request. It is a piece of a rendered page. Its one among several pagelets that are rendered and displayed in a browser window. It has an associated element file, and that element has logic to generate this Pagelet.  A pagelet can be cached in the Content Server and Satellite Server page caches.

2. PAGE:  A Page is nothing but the result of an HTTP request. It is the one which is displayed in a browser window. Sometimes, a page is created by compiling several pagelets into one final, displayed or rendered page. It has an associated element file, and that element has logic to generate this page. A page can be cached in the Content Server and Satellite Server  page caches.

3. PAGE NAME: This is the complete name given to the page. For example, if Full is the name of a page, and if its type is Article , and if it is in the site Sample, the following will be the PAGE NAME : Sample/Article/Full.

4. PAGE ASSET: A page asset is the one which simply act as containers for the actual content. These containers are arranged in the SITEPLAN tab of the TREE to facilitate the ease of navigation.You associate other content and other assets with these PAGE ASSETS and then you publish them.