Prevent catalog from loading from memory

Question

Hi experts!
I am working on B2B scenario with ERP backend and NO TREX.
I would like to prevent the catalog from loading from memory when the user logs in.
How can i achieve this????
Thank you all!!

Answer 1

Hi Pradeep,
i changed the value to -1 . And now in catalog cache statistics i see the following:
Configured expiration time: -60 min
Configured removal time: -60 min (next invalidation in -73 min)
Next check of remaining life time in 46 min (removal of catalogs with life time <= 0).
But still if another user logs in (2nd login) catalog is not read from ERP.
Is there any class i can enhance so that cache is never read?????
In R3MemCatalogBuilder class i see the code below: From my understanding it checks if there is catalog in memory and if not it connects to ERP. I have only extended Order Class so far and i do not understand how to extend this specific class.. Where should i register it???
Please help!!
Thank you in advance!!
     try {
               if (catalogTree != null) {
                    return catalogTree;
               //retrieve R/3 specific backend data
               R3BackendData backendData = ((R3CatalogServerEngine)theR3Catalog.getServerEngine()).getBackendData();
               //determine the cache key
               String configurationKey = backendData.getConfigKey();
               String catalogAndVariant = theR3Catalog.getName() + theR3Catalog.getVariant();
               String key = configurationKey + catalogAndVariant;
               //if (log.isDebugEnabled()) {
               //     log.debug("getCatalogTree started, cache key is: " + key);
               //now check the cache
               //use catalog cache, so (temporarily) all references to system cache are commented out
if (access.get(key) != null) {
if (log.isDebugEnabled()) {
log.debug("catalog already exists in cache");
catalogTree = (CatalogTree) access.get(key);
return catalogTree;
else {
the catalog tree does not exist
if (log.isDebugEnabled()) {
log.debug("creating the catalog tree");
catalogTree = createCatalog(jcoCon,
backendData,
theR3Catalog.getName() + " " + theR3Catalog.getVariant());
now put the new catalog into the cache
try {
access.put(key, catalogTree);
catch (Cache.ObjectExistsException ex) {
this is not possible,method is synchronized
log.debug("synchronization problem");
throw new CatalogBuildFailedException(ex.getMessage());
catch (Cache.Exception ex) {
this is not possible since an exception is thrown
before if the cache wasn't ready, see constructor
log.debug("cache exception");
throw new CatalogBuildFailedException(ex.getMessage());
               catalogTree = createCatalog(jcoCon,
                         backendData,
                         theR3Catalog.getName() + RFCConstants.CATALOG_GUID_SEPARATOR + theR3Catalog.getVariant());
               return catalogTree;
          catch (Exception ex) {
               log.debug("exception caught: \n", ex);
               throw new CatalogBuildFailedException(ex.getMessage());
          finally {
               jcoCon.close();