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; } } }

Are SitePublisher and Live site two different products

Raymand

Hi,
As I didn't find any product with the name "Site Publisher" from support.interwoven.com, Are SitePublisher and Live site two different products
could any help explain me the difference between these two products.

Thanks
Raymand

Find more posts tagged with

Comments

ISCBorisB

Hi,
As I didn't find any product with the name "Site Publisher" from support.interwoven.com, Are SitePublisher and Live site two different products
could any help explain me the difference between these two products.

Thanks
Raymand

Livesite Content Publishing Server (often referred as LiveSite) is a WYSIWYG platform for creating, deploying and
managing (relatively)small sites. It is composed of several modules like Edit, Admin, SiteCenter, etc...
SitePublisher is one of the LiveSite modules.

sdsdynmaic.rptdesign

Raymand

I got it. Thanks a lot for your help.

ccprofessional

SitePublisher is the other name for Livesite Runtime, which sits on the production server

Frederik

SitePublisher is the other name for Livesite Runtime, which sits on the production server

In my understanding, that's incorrect.

I believe that under 2.x, the terminology was

LiveSite Development ( => back-end, content editing...)
LiveSite Production; a.k.a LiveSite Runtime ( => front-end, run-time, web/app server...)

under 3.x that seem to have become

SitePublisher ( => back-end, content editing...)
LiveSite ( => front-end, run-time, web/app server...)

Quote from Release Notes:
LiveSite includes both development and runtime environment components. In past releases the LiveSite product name referred to both components. However, beginning with release 3.0, some product literature refers to the development component as SitePublisher, while the term LiveSite is reserved for the runtime environment component only. However, the LiveSite 3.0 product documentation continues to use the name LiveSite for both components.

samina

does it mean that SitePublisher is the module, using which you can create components in the back end ?
What will front end be called then ?

thanks

ISCBorisB

does it mean that SitePublisher is the module, using which you can create components in the back end ?
What will front end be called then ?

thanks

SitePublisher's Place in IWOV Suite of products changed significantly since this thread has been initiated.
Starting with the version V3 (I *think* ~12/2007 or thereabout) and up, it has been separated from the LiveSite and can be now
used in addition to (or instead of) TeamSite's FormsPublisher. Licensing is separate.

SitePublisher can be used as a static site generator. AFAIK *Native" Front-End is still called LiveSite Runtime.
Without LiveSite Runtime an alternative IWOV suggests is some additional generation of whatever you need from SP's
".page" Files or "another solution to render .page files", whatever that could possibly mean.

Personally, I find an idea of generating something ( .page Format ?) only to turn around and reverse-engineer it to
something else (HTML/JSP/ASP and whatnot) somewhat dubious but what do I know...

tec_iwov

Site publisher is the Livesite development environment. create site pages components.

there is the runtime production environment that runs within a j2ee container (tomcat is the default container) that will render the pages.

as mentioned you can within the Development environment generate html and deploy them to a standard http server but this limits the dynamic functionality the Livesite provides.

ISCBorisB

Site publisher is the Livesite development environment

Not any more. For some 7-8 Month now it is an independent Product.
You can use it with either LiveSite or TeamSite, in the latter one in addition to the FormPublisher

samina

If you use SitePublisher with TS, how do you use the components ? In case of LiveSite, components are available to use (Though I didnt use LiveSite, but one of my collegues was telling me how he used LiveSite front end).

Once you create components with SitePublisher , how do you make them available for use in TS ? I mean where do you keep them for use ?

thanks

ISCBorisB

If you use SitePublisher with TS, how do you use the components ? In case of LiveSite, components are available to use (Though I didnt use LiveSite, but one of my collegues was telling me how he used LiveSite front end).

Once you create components with SitePublisher , how do you make them available for use in TS ? I mean where do you keep them for use ?

thanks

As far as I can tell, divorced SitePublisher still has the same logistics it had during it's LiveSite marriage.

You have familiar Datums-Components-Pages-Site model, it just became available outside of LiveSite, that's all.
IWOV is a bit vague of how to render SitePublisher Components without LiveSite Runtime, see for example here.
The way I read it, it's the polite way to say "You use LiveSite Runtime or you are on your own".

I *think* it's quite possible that these ill-fitted jigsaw will be seriously modified within IWOV Venus/Gibraltar Initiative

tec_iwov

Livesite is a component of Teamsite all the resources built /w Livesite (components, templates, page, sites, etc...) are stored in Teamsite.

Livesite is made of 2 parts SitePublisher (the development environment that is an additional toolkit that runs in content center)

the runtime which is the production environment (a simple j2ee webapp that will run in a standard j2ee web container, tomcat by default)

Opendeploy and a Livesite workflow are used to deploy content from Sitepub to the runtime.

tec_iwov

without the runtime the only thing you can do in Generate static html and deploy it to a standard HTTP server.

ISCBorisB

without the runtime the only thing you can do in Generate static html and deploy it to a standard HTTP server.

Or you can write your own Web Application, parse .page Files upon request and generate what you want, Static, Dynamic, whatever.
Btw, next time could you please answer to the person that asked the question? I'm not the one.