Need help understanding separating code from content on the server end.

MLee7404

Hello.

I spoke to our technology team and they were trying to get a better
understanding of how teamsite works.

They asked questions about using the "separating code from content"...approach than pushing generated jsp pages(which we did at my previous company).

If the constructs of a page exist in an app tier of our servers
and all content(text), images, css, javascript live in the web tier.

I'm just trying to best explain to them how a web page is formed when you use the approach of separating code from content so that tech administrators
can understand what's happening.

They way it was explained was that raw text content in XML is passed
to a database which then calls the approrpriate assets and presentation tempaltes to form the page. JSP components such as the masthead, left nav, etc are formed together to create a page.

They asked "which database"? What is content? and is it correct that the database constructs are on the app tier and the assets, content and assets are on the web tier.

(I hope this made sense).


Thanks.

nipper

They asked questions about using the "separating code from content"...approach than pushing generated jsp pages(which we did at my previous company). If the constructs of a page exist in an app tier of our servers and all content(text), images, css, javascript live in the web tier. I'm just trying to best explain to them how a web page is formed when you use the approach of separating code from content so that tech administrators can understand what's happening. They way it was explained was that raw text content in XML is passed to a database which then calls the approrpriate assets and presentation tempaltes to form the page. JSP components such as the masthead, left nav, etc are formed together to create a page. They asked "which database"? What is content? and is it correct that the database constructs are on the app tier and the assets, content and assets are on the web tier.

There is no 1 size fits all answer here. TS is extremely flexible. It can have a template that is used to create flat HTML files. TS can have a template that generates JSP/ASPX files which will be run on the application server. Finally TS can have a template insert that data into a RDBMS of your choice (as long as it is supported by DataDeploy) and it can be read from JSP/ASPX code.

You need to understand the architecture in detail of the overall web solution and then see how TS fits into it rather than making it conform to TS.

By your questions, I certainly hope you company is going to bring a TeamSite architect in for a couple months. That will save you a great deal of grief.

Andy