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 license??????

AJ_23

Hi Team,

Well I have a question which will sound very funny to you all… but please help me out to understand this…

I am a novice for Livesite.
I am working on Teamsite 7.1. But willing to work on Livesite, at least Sitepublisher part of it.
Does (only) Sitepublisher require a separate license? (My client is not ready to invest money for any new license)

I know that Runtime does requires license for installation…
But can I have only Siteplisher without any license integrated with my Teamsite 7.1 so I can go ahead and at least try my hands on some static and dynamic component development?

Thank you

Find more posts tagged with

Comments

santosh013

Hi Team,

Well I have a question which will sound very funny to you all… but please help me out to understand this…

I am a novice for Livesite.
I am working on Teamsite 7.1. But willing to work on Livesite, at least Sitepublisher part of it.
Does (only) Sitepublisher require a separate license? (My client is not ready to invest money for any new license)

I know that Runtime does requires license for installation…
But can I have only Siteplisher without any license integrated with my Teamsite 7.1 so I can go ahead and at least try my hands on some static and dynamic component development?

Thank you

Hi,
Don't we have a TS.lic file for TS and SP.
Do you really need a license for runtime?

Rick Poulin

Yes, SitePub requires a license. Specifically, your TS.lic license for teamsite must enable SitePublisher. SitePub can work without the LiveSite runtime, in which case you'd be using it to generate static HTML.

The LSDS (display services) portion of the runtime does not have a license file, but obviously there's a purchase cost for it anyway. LSCS (content services) does use a license file, and that's another add-on that you don't necessarily need.

KoenDeSmet

The concept 'sitepublisher' and 'livesite' has always been a bit blurry.
Both are using the same ear file generated by the build done on the teamsite server. When running the ear file on the tomcat buildin into teamsite it's called SitePublisher. When running this ear file on a seperate frontend server ,and configure teamsite to deploy to that instance it's called 'livesite'.
As told before ,sitepublisher(teamsite) is configured out of the box to generate static files. As teamsite is sold as one product together with Sitepublisher in this setup there is no additional licensing for Livesite (since there is no livesite). But from the moment you'll use the ear file generated by teamsite on a frontend server (tomcat,wepshere,weblogic) then you'd need a livesite license. At least this is what I understood from it (might be wrong).

Rick Poulin

The concept 'sitepublisher' and 'livesite' has always been a bit blurry.

Why? Because a large amount of underlying code is shared between the two? The line isn't blurry at all: SitePublisher is the authoring piece, LiveSite is the (dynamic) rendering piece.

Deploying the EAR from TeamSite into a front-end servlet container works, but it's not the way it was intended to work. Yes, SitePublisher includes a part of the LiveSite runtime to enable the preview of pages, but it's not the same build as the LiveSite Runtime per se. In particular, I'm pretty **** sure that SitePublisher's LiveSite preview does not enable component caching (config sets cache time to -1 or somesuch).

AJ_23

Thank you all for wonderful posts.

Well, here is what I can figure out from above discussion… (Still lil bit confused, please correct me if I am wrong.)

If I have licensed Teamsite 7.1 version installed, I can go ahead and install only SitePublisher (need to check If I need to obtain a new TS.lic file with SITEPUBLISHER=true) so as to create static and dynamic components.

But to display deployed “.page” outputs we need to have Livesite runtime environment in place, which requires a separate license…

Adam Stoller

Thank you all for wonderful posts.

Well, here is what I can figure out from above discussion… (Still lil bit confused, please correct me if I am wrong.)

If I have licensed Teamsite 7.1 version installed, I can go ahead and install only SitePublisher (need to check If I need to obtain a new TS.lic file with SITEPUBLISHER=true) so as to create static and dynamic components.

But to display deployed “.page” outputs we need to have Livesite runtime environment in place, which requires a separate license…

Actually, although certainly confusing, I think it goes something like this:

AJ_23

Thank you all, for your contribution for helping me out.
Opening up a Ticket with Autonomy Support now. Will check if they can help me to figure license we need to go for for Site Publisher only.