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

LiveSite (general questions)

Adam Stoller

I figure this thread can be used for anyone with general questions regarding LiveSite

I forgot to ask this during the webcast ...

In the webcast it was mentioned that [paraphrased] "IT can enable / disable component access and features".
What kind of granularity exists for this configuration?

userid
TS role
OS group
TS group

Can you apply negative rights (e.g. all Editors except Smitty ;-)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Find more posts tagged with

Comments

Mongoose

I've just watched the webcast, and also have a few qns - mainly around deployment.

And specifically "what gets deployed?" e.g. is it HTML, JSP, XML that gets rendered by XSL at runtime?
Are all my previously compontised websites that produce quick light XHTML, now going to be deployed to app servers and run as jsps?
How does the dynamic content integrate with an appliaction already running in Websphere (for example)? Does livesite add the dynamic content into a already deployed ear file? (If so how? Is not, then how does the app pick up the dynamic content?)

These are just a few qns I have, (there are more), I have looked for documentation on the overall architecture, and what happens when etc, and what's put where but haven't spotted any (tho I guess there must be some) either on DEVnet or the support site. Anyone have any URLs to some documentation, or even some answers?

Thanks in advance
Andy

shanon

From my understanding, when you deploy a site, LiveSite uses OpenDeploy to push the XML and XSL files to the production file system and the associated meta-data to the production DB.

On the front-end, it's a java web application that uses a struts-like controller that actually does the rendering. This servlet takes the page template ( XML ), figures out which components need to be rendered, and then the components are responsible for their own rendering ( XML -> XSL -> HTML ). Additionally, each component has integrated caching which can get granular ( every x minutes, only when updated, never, every morning at 8am, etc. ), so you can definitely tune the app as necessary. Sooo, I wouldn't worry about your rendering times, although given the dynamic nature, it will most likely be a little slower than static (X)HTML.

Of course, this is only one configuration... there are other ways to deploy sites to the front-end, but I think the above is the best-practice process.

HTH,

Shanon

Shanon Levenherz
Mercer eBusiness Team
shanon.levenherz@mercer.com
http://www.mercerhr.com

shanon

I know that you can lock it down by AT LEAST ts user and ts role. I'm assuming ts group as well ... just not sure about the OS groups... I think IWOV may have gotten themselves into a bit of a pickle by supporting two types of groups ( OS and TS ). I think they're trying to figure out which one of the two they should move forward with which is why I have doubts about the OS support in LiveSite. I'll find out though and post back...

HTH,
Shanon

Shanon Levenherz
Mercer eBusiness Team
shanon.levenherz@mercer.com
http://www.mercerhr.com

boskovuk

I would like to learn more about this topic as well.

Apparently, the underlying technology is going to be different from the TS means to create the content. Is this valid statement (no JavaScript, DTDs, etc.)? What is the same and what is different between LiveSite and legacy technology to create the content?

Are there any developer/deployment available documents that would explain in more details what is under the hood?

thanks,
Bosko