Selective/Smart Cache Invalidation

-
Enable Selective/Smart Cache Invalidation

In ATG 10 we have a feature newly added to handle the automatic cache invalidation.This feature tracks which assets are deployed and invalidate cache only for those assets.
There will be a patch provided by ATG to implement this feature in previous versions.you may need to contact ATG for further details.
Please verify how to configure selective cache invalidation on the below link.

Selective cache invalidation will works only on item descriptors with cache mode is set as simple cache.

Even if Selective cache invalidation is enabled,the method invalidateCaches() clears all caches from the target repository.

Brief

On each Production Repository pointing to atg.adapter.gsa.GSARepository,there is a property 'selectiveCacheInvalidationEnabled' which needs to set to true,default is false.To achieve this,you need to add an entry to the Repository component in your Application,if not layer the Repository component in your module config path or inside localconfig or liveconfig layer.

http://docs.oracle.com/cd/E26180_01/Platform.94/ATGCAProgGuide/ATGCAProgGuide.pdf

Advantages

1. This will drastically improves site performance as it will not
   invalidate the repository caches for the assets which is not
   being touched or changed.
2. Deployments will be much more faster
3. This results in better performance for companies, fast loading of
   pages,and a reduction of load on the database due to reloading
   the cache

Comments

  1. AnonymousApril 4, 2012 at 10:20 AM

    How can this be tested? Is there a way we can test this real time.

    ReplyDelete
  2. SebastianApril 29, 2012 at 8:03 AM

    yes,we can test this once you have done the configration,and you can experience the advantages,as it will not invalidate the repository caches for assets which is not modified

    ReplyDelete

Post a Comment

Popular posts from this blog

Weblogic Issues during EAR Deployment Exception in AppMerge flows progression

-
Unable to access the selected application Exception in AppMerge flows progression Bean already exists "weblogic.j2ee.descriptor.ModuleBeanImpl@..../Modules[weblogic.descriptor.internal.Descriptor.Beankey@....] This issue can happen in many scenarios, may be you need to check your deployment descriptors based on Application Servers used, this generally happens due to issue in XML files related to deployment. I got this issue when i mistakenly added the modules twice in the Manifest file, the module 'Store.Storefront' is added more than once in  'ATG-Required'  of my Manifest.MF file,due to this i am seeing the module 'storedocroot.war' is added twice in my application.xml which is located in the  path ATGProd.ear\META-INF\application.xml.Due to this i am not able to deploy my EAR file. I have removed the duplicate entry and deployed the application and everything working fine. ....... <module>         <web>             <web-uri>atg_
Read more

BCC site status inaccessible Agent Production in error state

-
Image
The Error Message showing in BCC T he error logs is showing the below message /atg/epub/DeploymentServer Failed to connect to agent 'Production'. This agent not allowed to be absent for  a deployment. The server will continue attempts to  intialize the connection. Set loggingDebug to true for  continued exception and stacktrace logging. Analysis This happens when the target/Production instance is down for some  reason or the RMI configuration which points to the target/Production instance may not be correct one. Fix If this is happening  due to target/Production instance down  then we can restart the target/Production Server,Other wise  correct the RMI configuration from the BCC agent configuration page and reinitialise. Verify the RMI Port in Configuration.properties file.Usually this file will be located in the path C:\ATG\ATG10.2\home\servers\ATGProduction\localconfig\atg\dynamo\Configuration.properties,make sure the
Read more

DUseSunHttpHandler=true weblogic.net.http.SOAPHttpsURLConnection Weblogic/Java HttpHandler issues

-
Verify the issue is happening due to the error throwing  from the weblogic class  SOAPHttpsURLConnection,then you need to inform the Application Server which handler implementation you need to use.  add the following option to JAVA_OPTIONS in   setDomainEnv.sh/setDomainEnv.cmd  on Unix/Windows.   -DUseSunHttpHandler=true.  eg:  set JAVA_PROPERTIES=%JAVA_PROPERTIES% %WLP_JAVA_PROPERTIES%  set JAVA_OPTIONS=%JAVA_OPTIONS% %JAVA_PROPERTIES% -  DUseSunHttpHandler=true -Dwlw.iterativeDev=%iterativeDevFlag% -  Dwlw.testConsole=%testConsoleFlag% -Dwlw.logErrorsToConsole=%  logErrorsToConsoleFlag%  This setting tells WebLogic to use the Sun's https Handler   implementation rather than the WebLogic one.  So after this,it will use the  class HttpsURLConnection from the  javax package.   See Also   SSL Handshake error   java.lang.RuntimePermission modifyThread
Read more