This table explains all the engine properties used to configure backing store functionality. In addition see Table 27, Cache Cluster Properties (Sheet 1 of 3) for properties that define whether a backing store is used, and if a limited cache is used.
Specifies the path from the project root to the JDBC Connection resource that defines the connection to the backing store. For example:be.oracle.dburi.0 /SharedResources/JDBC Connection.sharedjdbc be.oracle.dburi.pool.initial.0 Initial number of JDBC connections in the JDBC connection pool used for the backing store. For example:See Setting Connection Pool Size for more details. Minimum and maximum number of JDBC connections in the JDBC connection pool used for the backing store.See Setting Connection Pool Size for more details. be.oracle.dburi.pool.enforce.0 Set this property to true if you want the other be.oracle.dburi.pool properties to be enforced.By default the be.oracle.dburi.pool properties are ignored. be.engine.tangosol.oracle.prefetch be.engine.tangosol.oracle.batchSize Optional. Dumps Oracle database reads and writes to the console and log file. log file. Set to true or false (Optional setting). Specifies what Cache Only objects are loaded into the cache on system startup. See Preloading Options for Cache Only Objects for more details.all: All objects are loaded.none: No objects are loaded.include: The only objects loaded are those specified by their generated class names, in properties of the following format :be.engine.cluster.entityClassName.preload=trueexclude: No objects are loaded except those specified in properties of the following format:be.engine.cluster.entityClassName.preload=falseThe function Coherence.C_ClassName() returns the generated class, given the project path to the entity (that is, the path to the entity in the design-time project).Default is all.
Copyright © TIBCO Software Inc. All Rights Reserved.