Global caches are grouped together based on common configuration requirements such as replication and disk storage. All caches in the application should be created in the default cache group. The name of the default cache group is curam-group.
In the current implementation, the default cache group is not self-replicating and does not support disk overflow and disk persistence. Because self-replication is disabled, the cache operations are only visible to the JVM where the global cache is located. However to keep all caches in the default cache group consistent throughout the application server cluster, an explicit cache invalidation mechanism is provided. The cache invalidation can only be triggered from the server code but it invalidates caches in both the server and the client containers across all JVMs in the application server cluster.