Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

12.4.3.4. JdbcStringBasedCacheStore Multiple Node Configuration (Remote Client-Server Mode)

The following is a configuration for the JdbcStringBasedCacheStore in JBoss Data Grid's Remote Client-Server mode. This configuration is used when multiple nodes must be used. 
<subsystem xmlns="urn:infinispan:server:core:5.2" default-cache-container="default">
	<cache-container ... >
		...
                <replicated-cache>
			...
	                <string-keyed-jdbc-store datasource="java:jboss/datasources/JdbcDS"
	                        		 fetch-state="true"                        
			                         passivation="false"
	                 		         preload="false" 
			                         purge="false" 
	                		         shared="false" 
			                         singleton="true"> 
				<property name="databaseType">${database.type}</property>
		                <string-keyed-table prefix="JDG">
		                            <id-column name="id" 
						       type="${id.column.type}"/>
	        	                   <data-column name="datum" 
	   						type="${data.column.type}"/>
	         	                   <timestamp-column name="version"
							     type="${timestamp.column.type}"/>
				</string-keyed-table>
			</string-keyed-jdbc-store>
                </replicated-cache>
	</cache-container>
</subsystem>
Copy to Clipboard Toggle word wrap
The string-keyed-jdbc-store Element

The string-keyed-jdbc-store element specifies the configuration for a string based keyed cache JDBC store.

  • The datasource parameter defines the name of a JNDI for the datasource.
  • The passivation parameter determines whether entries in the cache are passivated (true) or if the cache store retains a copy of the contents in memory (false).
  • The preload parameter specifies whether to load entries into the cache during start up. Valid values for this parameter are true and false.
  • The purge parameter specifies whether or not the cache store is purged when it is started. Valid values for this parameter are true and false.
  • The shared parameter is used when multiple cache instances share a cache store. This parameter can be set to prevent multiple cache instances writing the same modification multiple times. Valid values for this parameter are true and false.
  • The singleton parameter enables a singleton store that is used if a cluster interacts with the underlying store.
The property Element

The property element contains information about properties related to the cache store.

  • The name parameter specifies the name of the cache store.
  • The value ${database.type} must be replaced by a valid database type value, such as DB2_390, SQL_SERVER, MYSQL, ORACLE, POSTGRES or SYBASE.
The string-keyed-table Element

The string-keyed-table element specifies information about the database table used to store string based cache entries.

  • The prefix parameter specifies a prefix string for the database table name.
The id-column Element

The id-column element specifies information about a database column that holds cache entry IDs.

  • The name parameter specifies the name of the database column.
  • The type parameter specifies the type of the database column.
The data-column Element

The data-column element contains information about a database column that holds cache entry data.

  • The name parameter specifies the name of the database column.
  • The type parameter specifies the type of the database column.
The timestamp-column Element

The timestamp-column element specifies information about the database column that holds cache entry timestamps.

  • The name parameter specifies the name of the database column.
  • The type parameter specifies the type of the database column.
Report a bug
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat