Posts Tagged ‘Part 1’


IMPORTANT TAGS IN FATWIRE:

These days, I’m much concentrating on how to work with the TAGS available in FATWIRE. The TAGS which we are going to discuss now are basic and very important tags in Fatwire programming. As it is not possible for me to discuss all these tags in a single post, we will discuss them in different articles followed by this article.

Lets start..

1. Content Server Context tag:

This is the tag that Creates the Content Server Context. This is the first tag , and also the last tag of the JSP or XML. What ever the code that falls between these tags, should be rendered by the content server.  The Full form of FTCS tag is Future Tense Content Server tag.

JSP Syntax:

<ftcs1_0:ftcs>
———–

</ftcs1_0:ftcs>

XML Syntax:

<FTCS>

———-

</FTCS>

2. Tag for displaying the value of a variable:

The tag for displaying the value of a variable is given below for both xml and jsp. It displays the value of a variable, session variable, built-in, etc.

JSP Syntax:

<ics:getvar
name=”variableName”/>

XML Syntax:

<CSVAR
NAME=”variableName”/>

Example:

String l_C =<ics:getvar name=”c”/>     // Gets the value of “c”, i.e., the asset type, and returns the value to a string variable.

String l_C = ics.GetVar(“c”);    // Similar kind of Usage in different form

3. Tag for setting the value of a variable:

SETVAR is the tag for setting the value of a content server variable. The syntax is given below for both xml and jsp:

JSP Syntax:

<ics:setvar
name=”variableName”
value=”variableValue”/>

XML Syntax:

<SETVAR
NAME=”variableName”
VALUE=”variableValue”/>

Example:

<ics:setvar name=”errno” value=”0″/>

4. Tag for setting the session variable:

SETSSVAR is the tag for setting a session variable. The syntax is given below for both xml and jsp:

JSP Syntax:

<ics:setssvar
name=”variableName”
value=”variableValue”/>

XML Syntax:

<SETSSVAR
NAME=”variableName”
VALUE=”variableValue”/>

Example:

<ics:setssvar name=”preferred_locale”  value='<%=ics.GetVar(“default:locale:id”)%>’/>

We will see more tags in the upcoming posts..

Stay tuned…


The STATIC Publishing method, other wise called as EXPORT TO DISK publishing method is a best option, especially when we want to export the files to the file system on the same machine on which the content server is residing. It exports the rendered html files (or any other files that are approved) to the location specified by the user. For example, if we want to export the html, css, js, etc files to an application server residing on the same machine as the content server, we should follow the Static Publishing method. In this topic, we are going to discuss how we should create a static destination, and how to publish (export) the files.

CREATION OF STATIC PUBLISH DESTINATION:

The following steps are involved in the creation of a STATIC PUBLISHING DESTINATION:

  • Login to the Advanced user interface.
  • Go to the admin tab of the tree.
  • Expand PUBLISHING -> DESTINATIONS.
  • Click on ADD NEW. The following screen appears:

image

  • In the “DELIVERY TYPE” drop down, select “EXPORT TO DISK: EXPORT WEB FILES TO DISK”.
  • Enter a name for the publishing destination in NAME field
  • The BASE DIRECTORY is the directory into which the files will be exported. For Jump Start kit, the following is the default location into which the files will be exported: <Drive>:\FatWire\JSK\7.5Patch5\ContentServer\7.5.5\export. If we give a name, a new directory will be created under the export folder specified above.
  • Select the roles which approve the assets for publishing to this location.
  • Select the roles which can publish to this destination.
  • Select the sites for which this destination will be available.
  • Click on ADD NEW DESTINATION button in the bottom.

That’s it, the publishing destination is created for Static Publishing.

In the next few posts, we are going to know how to work this Static Publishing.