use of multiple distributed same caches scheme, what about config dumps?

Hello

If a distributed system is configured with the reading-writing-support-map, all caches will be required to set the configuration of dumps if the caches use the same distributed schema? For example, we have two caches 'ExpireSessions' and 'Client' who are using distributed system. But only "ExpiredSession" cache must have the reading-writing-support-map (for transaction lite) AND the "ExpiredSession" must be persistent at DB. For cache 'Customer', there NO need to have the reading-writing-support-map AND there is NO need to be persistent in DB. We currently have the following configuration, which also has the "write-delay" and "cache-store' configurations for the cache of 'customer '.

Is it possible has no cache to store configuration configuration (writing / time, cache-store) for the cache of the client even if it uses the same schema distributed as "ExpiredSession" (who needs the configuration of the cache store?) We think that he can probably remove some of the load and improve efficiency) for the 'client' cache operations.

Or is it necessary to have a separate distributed system for cache 'Customer' without right cache store configuration? But then pools of separate/additional threads to use for the service?

Any suggestions?

Thanks in advance for your help.


< name-cache > ExpiredSessions < / cache-name >
< scheme name > distributed by default < / system-name >
< init-params >
< init-param >
timeout < param-name > < / param-name >
< param-value > 2 s < / param-value >
< / init-param >
< init-param >
< param-name > writing-delay < / param-name >
< param-value > 1 s < / param-value >
< / init-param >
< init-param >
cache-store < param name > < / param-name >
xxx.xxx.DBCacheStore < param-value > < / param-value >
< / param-value >
< / init-param >
< / init-params >




<>cache-mapping
< name of cache - > customer < / cache-name >
< scheme name > distributed by default < / system-name >
< init-params >
< init-param >
cache-store < param name > < / param-name >
xxx.xxx.EmptyCacheStore < param-value > < / param-value >
< / init-param >
< init-param >
< param-name > writing-delay < / param-name >
< param-value > 24 h < / param-value >
< / init-param >
< / init-params >
< / cache-mapping >


<!--
The scheme of pricing-distributedcaching distributed by default.
->
< distributed plan >
< scheme name > distributed by default < / system-name >
< service name > XXXDistributedCache < / service-name >
< number > 16 threads < / thread count >
< support-map-plan >
< reading-writing-support-map-plan >
<>plan-Ref rw - bm < / plan-ref >
< / reading-writing-support-map-plan >
< / support-map-plan >
< autostart > true < / autostart >
< / distributed plan >

user621063 wrote:
Thank you, Robert/NJ

It's when people usually press the [OK] button to assign some points...

Best regards

Robert

Tags: Fusion Middleware

Similar Questions

Maybe you are looking for