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 Cached files

PayalGarg

[font=Tahoma][color=#000000][font=Arial]Hi All,

[size=2]

This is related to SitePublisher/LiveSite caching. We cache different components and publish the pages in LiveSite Runtime. There is a file cache.ccf in LiveSite Runtime that stores JCS settings. But where are actual cached files stored in LiveSite Runtime?

There is a parameter called as [color=#000000]jcs.auxiliary.DC.attributes.DiskPath that contains the location of cached files. But in our implementation I'm not able to figure it out.

Can somebody point me to the default location of cached files?

We are using Teamsite6.7.2/SitePublisher 3.1.

Thanks

[font=Tahoma][font=Arial][color=#000000]Payal

[/color][/font][/font][/color][/size][/font]
[/color][/font]

Find more posts tagged with

Comments

vpatel

What are you after? What is the goal of you trying to look for the cache directory location? Please keep in mind that the default configurations are tested and highly tuned by Interwoven. You can make changes but be careful and make sure you know exactly what you are doing.

With that said, LS caching is multi-tier caching. There are items that cached directly in the memory. When in-memory cache reaches its limit, it gets spills over to the disk. OOTB, disk cache gets stored under the WEB-INF directory.

PayalGarg

I am in process of analyzing an implementation that may need improvement. That is why i'm curious to know these details. Anyways thanks for your reply.

tec_iwov

can you explain the issues that you are seeing? we might be able to help you solve that instead of trying to read binary files

PayalGarg

I'm offcourse not trying to read the binary files..... But need to know this location for cache clearing options. Looking at the folder livesite.cache I doubt we can have some custom process (instead of invalidate cache option) to clear cache.

In our implmentation, there are three Livesite Runtime instances hosted on separate servers and are load balanced. All these three LS instances are as of now hosting one website.

We need to host multiple websites and need to analyze how we can achieve the same. Performance can be one of the major issues. Also we cannot have separate LS instances for all websites. One possible approach is to have several LS runtime instances hosting all the websites and then load balance all of the instances. Any pointers would be helpful.

We need to leverage LS runtime caching, Load balancing techniques and web server (Apache in our case) caching options. I'm going through SP dev guide, Appendix M (Performance Best Practices).

Thanks
Payal

tec_iwov

the livesite cache is used to cache internal renderings of components and page structures. it is local to the runtime instance. If you use the Livesite supplied workflow it will handle fanout of content and invalidation files. There's performance metrics available from interworven you should contact support or sales for this data.

cute_guy

I'm offcourse not trying to read the binary files..... But need to know this location for cache clearing options. Looking at the folder livesite.cache I doubt we can have some custom process (instead of invalidate cache option) to clear cache.

In our implmentation, there are three Livesite Runtime instances hosted on separate servers and are load balanced. All these three LS instances are as of now hosting one website.

We need to host multiple websites and need to analyze how we can achieve the same. Performance can be one of the major issues. Also we cannot have separate LS instances for all websites. One possible approach is to have several LS runtime instances hosting all the websites and then load balance all of the instances. Any pointers would be helpful.

We need to leverage LS runtime caching, Load balancing techniques and web server (Apache in our case) caching options. I'm going through SP dev guide, Appendix M (Performance Best Practices).

Thanks
Payal

When u have a user defined workflow instead of OOTB, try creating cache files in the workflow and deploy them to the sites directory of the LiveSite deployment directory.

The cache files should have a naming convention as cache.XXXXXXXXXXX

The cache.XXXXXXXXXX file will be consumed by the invalidation monitor every 30 sec.

PayalGarg

Thanks for your replies.