Live Site Display Services

Do we need to have Live Site Display Services on our Staging & Production environments?
Can we have ONE Live Site Display Services ( QA server) and deploy the content to Staging & Production servers

Pls advice / doc ref

Thanks

Vin

Find more posts tagged with

Comments

nipper

If you are using SP to generate HTML or not at all, no.

Otherwise you will want LSDS. Do you have to have it on Stage as well as prod ? No, but you would be a fool not to. Can you share an LSDS install ? Possibly, if web server performance is not that important. I would never try it.

iwTech

Thanks Andy ,

please advice on the following design ?

nipper

Go ahead. I won't get fired if it is slow. You will

Your boss really wants to save a couple bucks and slow down the production web server ? Save more money and don't have a Staging server.

Like I said, that *might* work. You would have to try it out. I WOULD NEVER GET NEAR THAT IMPLEMENTATION BECAUSE YOU ARE SLOWING DOWN PROD WITH EXTRA LOAD

Again, not my job on the line, so do it.

Migrateduser

Sorry i am confused a bit here. As far as i am aware, you do not need a separate license for LSDS. you can configure LSDS for your app server (Tomcat/WAS/Weblogic) and use the separate instances.
Perhaps i am unable to grasp your issue here!

interDev

Sorry i am confused a bit here. As far as i am aware, you do not need a separate license for LSDS. you can configure LSDS for your app server (Tomcat/WAS/Weblogic) and use the separate instances.
Perhaps i am unable to grasp your issue here!

You do need seperate license for each LSDS instance thats why they are trying to use a shared LSDS for multiple servers (which is obviously not a right approach from performance point of view.)

Crsb

Thanks Andy ,

please advice on the following design ?

What is point of having 2 web servers if you only got one LS instance?
you will still have the same capacity of one LS server whether you hook it to 1 or 2 web servers... to Andy's point, you will boss will save more money by removing the second web sever Smiley Happy

.

It might make sense to share LSCS but not LSDS.

iwTech

Go ahead. I won't get fired if it is slow. You will

Your boss really wants to save a couple bucks and slow down the production web server ? Save more money and don't have a Staging server.

Like I said, that *might* work. You would have to try it out. I WOULD NEVER GET NEAR THAT IMPLEMENTATION BECAUSE YOU ARE SLOWING DOWN PROD WITH EXTRA LOAD

Again, not my job on the line, so do it.

Hi Andy ,
I want to present the possible options to the customer, but the performance is more important.

I have opened a ticket with support and waited a long , their answer is to contact professional service ?

Thank you for the help.
-Vin

nipper

Hi Andy ,
I want to present the possible options to the customer, but the performance is more important.
I have opened a ticket with support and waited a long , their answer is to contact professional service ?

Thank you for the help.
-Vin

If a consultant presented this option to my management team as a viable option I would tell management to get rid of them. Being prepared to answer that question is fine, but presenting that as an option is a horrid idea.

Untak

We can bypass LSDS if we are using Livesite Taglib which can be easily integrate with J2EE Application

Thanks

vpatel

We can bypass LSDS if we are using Livesite Taglib which can be easily integrate with J2EE Application

Thanks

Technically you are NOT bypassing LSDS. LS TagLib is still LSDS -- it just matter of whether it has its own container or if it is running within the same container as your custom J2EE application.