Page level caching..?

Hi all

How to do page level and component level caching in site publisher...
As if i new to sitepublisher i dono how to do it.

i can able to set the caching time in component properties but not sure where to check whether it is cached or not...

please advice me on this.

Also it will be helpfull if any share docs abt it to this mail id : hary.krzna@in.com

thanks in advance
Hary

Find more posts tagged with

Comments

santosh013

Hi all

How to do page level and component level caching in site publisher...
As if i new to sitepublisher i dono how to do it.

i can able to set the caching time in component properties but not sure where to check whether it is cached or not...

please advice me on this.

Also it will be helpfull if any share docs abt it to this mail id : hary.krzna@in.com

thanks in advance
Hary

Hi,
You can update the contents related to the specific component and can check it.
Are your fetching contents from DCR or DataBase?

Thanks.

Harykrzna

Hi,
You can update the contents related to the specific component and can check it.
Are your fetching contents from DCR or DataBase?

Thanks.

thanks for the reply..

I am using content from both DCR and DB.. how to check this in DB... what kind of update is done in db side...
do you relacted doc for this caching... if you hav pls share it...

thanks
HARY

santosh013

thanks for the reply..

I am using content from both DCR and DB.. how to check this in DB... what kind of update is done in db side...
do you relacted doc for this caching... if you hav pls share it...

thanks
HARY

Hi,
I hope you are working in dev. environment.
Assuming that and going forward what is the problem in changing the contents in DCR as well as in DataBase.
I hope you are updating DB through DCR only or even if the DB is not updated through DCR, what is the problem in changing some of the values in DB through some update query.
Regarding related doc:you can get the information about cache in Sitepublisher Developer Guide.

HTH.

Rick Poulin

Not sure how the conversation went into updating databases from DCRs when it started with caching, but to the original question...

i can able to set the caching time in component properties but not sure where to check whether it is cached or not...

On your LiveSite runtime, you can access the Java Caching System (JCS) console at http://yourserver: port/iw/admin/JCS.jsp. From there, you can inspect the contents of the cache to some degree, and also clear the cache. Note that pages/components aren't cached at publish time -- they're cached after the first request.

Harykrzna

Not sure how the conversation went into updating databases from DCRs when it started with caching, but to the original question...

On your LiveSite runtime, you can access the Java Caching System (JCS) console at http://yourserver: port/iw/admin/JCS.jsp. From there, you can inspect the contents of the cache to some degree, and also clear the cache. Note that pages/components aren't cached at publish time -- they're cached after the first request.

Thanks for the reply

Please corect me if i am wrong.
So i have to set the cache time in the component properties and have to check it in runtime by making request from the site which we develope.........

pls specify where to check this.....
bcos our ultimate goal is to avoid webservice hit each n everytime... and to make cached data to be hit everytime from the website which we develope rather hitting a webservice call everytime..

thanks
HARY

Rick Poulin

So i have to set the cache time in the component properties and have to check it in runtime by making request from the site which we develope.........

That's correct.

pls specify where to check this.....

The URL I gave you above is on your LiveSite (Display Services) Runtime server.

bcos our ultimate goal is to avoid webservice hit each n everytime... and to make cached data to be hit everytime from the website which we develope rather hitting a webservice call everytime..

Seems to me like if you want to test this for real, don't rely on the cache console. Have your component cache configured the way you want it, have your webservice log every call it receives, then hit your page a dozen times and make sure you only get one log message on the webservice end.