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 Runtime Server cluster

TeamsiteDev

Hi,

We are using 3 LSDS servers to form a cluster & loadbalanced them.  We want to keep all our website content in a shared network folder. For this we have created soft link for the "../Interwoven/LiveSiteDisplayServices/runtime/web" folder of each LSDS server in cluster to point to the common folder "/web" for all 3 servers.  We are concerned about the "WEB-INF" folder of each server which also is getting shared among all 3 LSDS servers as it lies in "../Interwoven/LiveSiteDisplayServices/runtime/web" folder. Please can you advise if this approach is fine ?

Thanks!

Find more posts tagged with

Comments

Rick Poulin

There's nothing strictly wrong with that approach, although you may run into issues later on depending on whether you use a database and/or LSCS.

The preferred approach would be to deploy to all three servers in a single transaction, instead of sharing a file system location.

nipper

The only issue I can see are the cache files. However I think you are OK, When you push a page out, it will push a cache clear file as well. That is removed (after about 20 minutes IIRC) by LSDS, but I think the cache is cleared well before. So all 3 should have cleared the cache before it is removed

I have done this with several servers, so it does work.

Rick Poulin

* Andy's point assumes that you're on LS 7.3.2 or later. Your cache would indeed get stuck on earlier versions.

TeamsiteDev

Thanks Rick & Andy !

We are using 7.4.1 LSDS & LSCS , so I think we are good.

Interwoven Support also mentioned about Caching issue as "livesite.cache" folder also lies in WEB-INF folder.

dataset parameter binding.jpg