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 questions

jihan

Hi,

I'm new to LiveSite and having trouble understanding how it works. Hoping to get some answers here.

I'm using TS, OD & LS 7.0 on Windows Server 2008 for Authoring and LSDS is installed on a Linux RedHat 5 with same LS v7.0.

So in my content center, I have a site with pages inside. At the moment we're publishing these contents to the receiver as html format. (This is done without LS). Now we have installed LS, the existing pages should it still be deployed as html? Or should I just deploy the .page and LSDS will know how to render it? Can I deploy to other location than c:\interwoven\Livesite\runtime\web\sites? How will I redirect the LSDS to read from my own folder instead of this one?

Thanks!

Find more posts tagged with

Comments

vpatel

Now we have installed LS, the existing pages should it still be deployed as html? Or should I just deploy the .page and LSDS will know how to render it?

If you want to leverage the LSDS features and functions then deploy .page file and LSDS knows how to handle them.

Can I deploy to other location than c:\interwoven\Livesite\runtime\web\sites? How will I redirect the LSDS to read from my own folder instead of this one?

In the current version, it has to be at that location.

Rick Poulin

How will I redirect the LSDS to read from my own folder instead of this one?

You can use your web server (IIS / Apache) to route requests differently. For example, it's common practice to have the web server serve the static assets (css, js, img) rather than having the extra weight from Tomcat stream the binary data.

Viewer OS.png

BVT.png

vpatel

You can use your web server (IIS / Apache) to route requests differently. For example, it's common practice to have the web server serve the static assets (css, js, img) rather than having the extra weight from Tomcat stream the binary data.

You are correct in terms of where and how the static assets get served up from...However, I think his questions was to whether LSDS can serve up pages from a different location than the lsds-home/runtime/web/sites...The answer to that, as I previously stated, is no in the current version.

jihan

Hi,

Thanks for the reply.

About the config files.. actually how many config files do I need for LSCS deployment?

What I'm editing now is

1) deployment-source.properties from C:\Interwoven\LiveSiteCSAuth\authoring\etc\deployment\config
2) lscs-authoring.xml
3) opendeploy.properties from iw-home\local\config\lib\content_center\livesite_customer_src\etc\conf\livesite_customer
4) content.properties

Are there any other files?

I found that it requires a StartDeploy_OverrideManifest property. By default it's empty. What should be the location for this? I found the manifest file being created in

C:\Interwoven\LiveSiteCSAuth\authoring\tmp\\payload\

There's a manifest folder here, along with content & idx folder. Should this \tmp be the location that I should point to?

Thanks!