LiveSite: Why should it be installed on Production Server?

From the installation documents I observe that the LiveSite must be installed on the production server tooo. Why so?

What is the advantage ? can pages be edited directly from the production server? What will be deployed to the production server ".pages" or generated html? Why is the "generateHtml" option made available in the content center?

It would be great to point me to some detailed documentation and guide me through simple examples.

Thanks

Find more posts tagged with

Comments

Migrateduser

I have also tried to find out some documentation witch explains this kind of basic information, but with no luck.
It seems like there are others in this forum who wants to see this information.

Best luck with information hunting.
A-P

shanon

From the installation documents I observe that the LiveSite must be installed on the production server tooo. Why so?

LiveSite has two pieces:

A TeamSite piece, used to develop components and templates and use them to create sites and pages. This functionality is installed and accessible via the ContentCenter application.

A Runtime piece, used to serve the sites and pages to end users. This is a Java Web application that is integrated with Apache Tomcat 5 out of box. With the release of 2.2.1 we will also be officially supporting the runtime application in the following containers: BEA WebLogic 8.1, IBM Websphere and Sun ONE Java Server (iPlanet) 6.0.

Typically the TeamSite applicatoin and the Production Runtime application are hosted on separate machines or even a separate cluster ( depending on the runtime app container... )

LiveSite ships with a workflow that deploys sites, pages, and content to the runtime (production) environment so you can hit the ground running.

What is the advantage ?

The advantage is that we now have a presentation layer... this new functionality requires a Java Web or J2EE application container. ( if using .page files and not static .html -- see below )

can pages be edited directly from the production server?

No, pages are edited in TeamSite. However the "Live Page Edit" component ships out of box with the ability to link from a page on the runtime/production system directly into the Page Edit window within TeamSite. The typical use case is that a page editor is browsing the production site and sees an error that they'd like to correct. They click the "Edit" link on that page and are asked to log into ContentCenter. Upon auth, the Page Editor opens that page for editing. User makes the change, previews from w/in TeamSite, then pushes the content out to the runtime via the out-of-box or a custom workflow.

What will be deployed to the production server ".pages" or generated html? Why is the "generateHtml" option made available in the content center?

If the Runtime applicatoin is enabled, .page files may be served. However, some customers only wish to use a web server to serve .html. The Generate HTML menu option is provided for this reason. Generate HTML processes one or more .page files and into static HTML. Note that any dynamic functionality is processed at generate time and the output rendered in the static page i.e. this process loses any real-time dynamic performance ( other than AJAX/JS based functions ).

Hope this helps somewhat ... feel free to ask more questions.

Shanon

nipper

What kind of fuinctionality still exists if you choose not to install the production site ?

If I have a portal in house already, how can LS fit in ?

AnandaNR

Shanon, that was informative.

Can you please guide me in configuring LiveSite with "iPlanet 6.0" server?

Thanks

report-sample.rptdesign

report-sample.pdf

jkm

If the Runtime applicatoin is enabled, .page files may be served. However, some customers only wish to use a web server to serve .html. The Generate HTML menu option is provided for this reason. Generate HTML processes one or more .page files and into static HTML. Note that any dynamic functionality is processed at generate time and the output rendered in the static page i.e. this process loses any real-time dynamic performance ( other than AJAX/JS based functions ).

Hope this helps somewhat ... feel free to ask more questions.

Shanon

Hi Shanon,
Does this mean using livesite you can create only .page or .html files. If we need to create .jsp/.asp or any other kind a pages then those pages would not be produced by livesite???

shanon

What kind of fuinctionality still exists if you choose not to install the production site ?

If I have a portal in house already, how can LS fit in ?

LS can fit in any number of ways but the two most common are:

* Deploy the LiveSite Runtime Application ( a EAR or WAR ) insdie your portal container application. This enables LiveSite components to reuse all of your existing business logic and portal fx (e.g. personalization / commerce ) seamlessly via execution in the same JVM/Portal Application.

* Deploy LiveSite Runtime Application to its own server instance ( Tomcat or your Portal container ) and use web services to communicate w the portal.

If you choose not to install the production application, then you can use the Generate HTML menu item in TeamSite to convert a .page to a static .html file which can then be deployed. You'll still be able to use LiveSite's Page Editor to layout the pages, etc.

Shanon

shanon

Shanon, that was informative.

Can you please guide me in configuring LiveSite with "iPlanet 6.0" server?

Thanks

Well, I think the best reference is the iPlanet documentation... the LiveSite Runtime applicatoin is just a standard WAR and EAR. Both archives contain the same application but one is a Web App and once is an Enterprise Web App ( J2EE ). I believe that WARs are best for iPlanet 6...

Just deploy the runtime.war there, make sure that it runs exploded ( so you can deploy content from TeamSite into the application ) and you should be good to go. There may be some nuances with iPlanet's server.xml, but again, the iPlanet docs would be best for this.

Shanon

shanon

Hi Shanon,
Does this mean using livesite you can create only .page or .html files. If we need to create .jsp/.asp or any other kind a pages then those pages would not be produced by livesite???

I think that you're misunderstanding how LiveSite works. Maybe check out some of the demos... LiveSite's Page Editor allows you to drop components onto a page and lay them out kinda like designing a Powerpoint slide. Once you're set, you save this page as a .page file. I'm not sure how you would get to JSP/ASP from this or, frankly, why you'd want to.

LiveSite's runtime application plays nice with JSPs so you can have your own .jsp and LiveSite's .page files run together in the same app if you'd like... you can link them, etc. It's up to you. Re: ASP, you'd have to have an IIS instance and then have another Tomcat ( or other Java Web app Container ) to run LiveSite's app and talk via SOA ( Web Services ).

Hope this helps clear things up... if you have a more specific question, let me know.

Shanon

nipper

very helpful Shanon thanks.

Andy