nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

SitePublisher and LiveSite

nirjari

I want some basic distinction between SP and LiveSite.

LiveSite is used for generating components ie its used for development components. So LS is the back end tool. While SP is using the components ie its the front end tool. Is that right ?

Before both the front end and back end were taken care of by LiveSite only, is that right ?
thanks

Find more posts tagged with

Comments

Faizi

I want some basic distinction between SP and LiveSite.

LiveSite is used for generating components ie its used for development components. So LS is the back end tool. While SP is using the components ie its the front end tool. Is that right ?

Before both the front end and back end were taken care of by LiveSite only, is that right ?
thanks

Not..! SitePublisher is basically development area for developing a site dynamically using drag and drop feature with component and template. But LiveSite (runtime) is a production server. That is basically an application server. Default it is Apache Tomcat.

This thread will give you lots more to differentiate both.

vpatel

At a very high level:

SitePublisher is the drag-and-drop authoring interface along with some other functionalities. It is encapsulated within the TS server.

LiveSite is the Runtime piece -- it is a standard J2EE application. It sits on your Java application server (Tomcat, WebSphere, WebLogic, etc.)

You can use SitePublisher by itself if you generate static HTML pages. In some cases, I've seen clients generating JSP/ASP pages as well and have Java/.NET (no LiveSite) runtime environments.

If you want to take advantage of Interwoven's Targeting offering then you have to use LiveSite Runtime. It is almost always necessary if you have dynamic features/functionality in your components.

Further details in the product manuals/guides.

HTH.

nirjari

So LiveSite is not a toolkit or something that is used by the developer or user directly. Its an application being run in the background.
SitePublisher comes with some components to create website and if new components are needed, then we can develop it using SitePublisher. So there is no need of any other backend tool.
I think there was no SP before and LS was used for site development, right ? Then front end of LS which is LS PageEditor, SiteMap manager etc is renamed as SP and LS Runtime is used on the target application server. It sounds like opendeploy, where receiver server is needed on target. Is it like that or can we work just with SitePublisher ?

vpatel

It'll be beneficial to look at the product manuals and potentially pursue some training.

PayalGarg

Please refer to the thread

http://devnet.interwoven.com/forums_vb/showthread.php?t=29049&forumid=66

Thanks
Payal