 | Berkeley Database JE Java class libraries are required to utilize a bdb-store-manager, visit the Berkeley Database JE product page for additional information. |
Used in: external-scheme, paged-external-scheme, async-store-manager.
| Berkeley Database JE Java class libraries are required to utilize a bdb-store-manager, visit the Berkeley Database JE product page for additional information. |
The BDB store manager is used to define external caches which will use Berkeley Database JE on-disk embedded databases for storage.
This store manager is implemented by the com.tangosol.io.bdb.BerkeleyDBBinaryStoreManager class, and produces BinaryStore objects implemened by the com.tangosol.io.bdb.BerkeleyDBBinaryStore class.
The following table describes the elements you can define within the bdb-store-manager element.
| Element | Required/Optional | Description |
|---|---|---|
| <class-name> | Optional | Specifies a custom implementation of the Berkeley Database BinaryStoreManager.
Any custom implementation must extend the com.tangosol.io.bdb.BerkeleyDBBinaryStoreManager class and declare the exact same set of public constructors. |
| <init-params> | Optional | Specifies additional Berkeley DB configuration settings. See Berkeley DB Configuration.
Also used to specify initialization parameters, for use in custom implementations which implement the com.tangosol.run.xml.XmlConfigurable interface. |
| <directory> | Optional | Specifies the pathname for the root directory that the Berkeley Database JE store manager will use to store files in. If not specified or specifies a non-existent directory, a temporary directory in the default location will be used. |
| <store-name> | Optional | Specifies
the name for a database table that the Berkely Database JE store manager
will use to store data in. Specifying this parameter will cause the bdb-store-manager
to use non-temporary (persistent) database instances. This is intended only
for local caches that are backed by a cache loader from a non-temporary
store, so that the local cache can be pre-populated from the disk on startup.
When specified it is recommended that it utilize the {cache-name}
macro. Normally this parameter should be left unspecified, indicating that temporary storage is to be used. |