|Sesat > Docs + Support > Development using the SFC|
|work in progress|
For newcomers there's a tutorial on how to build sesam.com. This may prove more useful to begin with than the following documentation.
The SFC - SESAT Frontend Container - is the place to create vhosts that are using the full SESAT functionality.
All sites or applications running within the SFC also runs on the same JVM as the SESAT Kernel.
All code, configuration, images etc. related to a vhost are termed resources. These resources may be on the same file system as SESAT Kernel (in the Tomcat deployment catalogue), or they can be on some other server reachable by http.
In effect, SFC is just the notion of the JVM where we deploy and run applications using SESAT Kernel.
The following text will expose the details of how to create a site within the SFC.
The resources are found under the main catalogue. As for now we are using the following:
The hierarchy for where a sitesearch is placed is: generic.sesam.no -> genericno.sesam.no -> genericsitesearch.sesam.no -> sitesearch.sesam.no (vg.sesam.no)
It's important to remember that every project inherits all the template-, css-, imagefiles and so on from the level above. That's a reason why we use the generic genericsitesearch.sesam.no to keep the sitesearch spesific stuff for itself.
While not a requirement, most users would want to use HTML to encode search results. SESAT does not pose any strict requirements on the user, but we strongly recommend following international standards.
While SESAT support any "style" of HTML-coding, we recommend using XHTML 1.0 with the TRANSITIONAL doctype.
The templates are defined through a custom templating system defined via the layout element in views.xml. Using these definitions work with the search:include tag or the searchTabInclude velocity macro.
We recommend the following:
The benefits by doing this are:
Simple tutorial Developing a quick and simple Enrichment tutorial