Red Hat Summit Red Hat Summitサポートコンソール開発者トライアルの開始お問い合わせ

このコンテンツは選択した言語では利用できません。

18.8. JPA Cache Store

The JPA (Java Persistence API) Cache Store stores cache entries in the database using a formal schema, which allows other applications to read the persisted data and load data provided by other applications into Red Hat JBoss Data Grid. The database should not be used by the other applications concurrently with JBoss Data Grid.

Important

In Red Hat JBoss Data Grid, JPA cache stores are only supported in Library mode.
Report a bug

18.8.1. JPA Cache Store Sample XML Configuration (Library Mode)
リンクのコピー

To configure JPA Cache Stores using XML in Red Hat JBoss Data Grid, add the following configuration to the infinispan.xml file: 
<namedCache name="users">
  <!-- Insert additional configuration elements here -->
	<persistence passivation="false">
            <jpaStore xmlns="urn:infinispan:config:jpa:6.0"
                      shared="true"
                      preload="true"
                      persistenceUnitName="MyPersistenceUnit"
                      entityClassName="org.infinispan.loaders.jpa.entity.User" />
	</persistence>
</namedCache>
Copy to Clipboard Toggle word wrap
For details about the elements and parameters used in this sample configuration, see Section 18.2, “Cache Store Configuration Details (Library Mode)”.
Report a bug

18.8.2. JPA Cache Store Sample Programmatic Configuration
リンクのコピー

To configure JPA Cache Stores programatically in Red Hat JBoss Data Grid, use the following: 
Configuration cacheConfig = new ConfigurationBuilder().persistence().addStore(JpaStoreConfigurationBuilder.class).persistenceUnitName("org.infinispan.loaders.jpa.configurationTest")
​                .entityClass(User.class)
​                .build();
Copy to Clipboard Toggle word wrap
The parameters used in this code sample are as follows:
  • The persistenceUnitName parameter specifies the name of the JPA cache store in the configuration file (persistence.xml) that contains the JPA entity class.
  • The entityClass parameter specifies the JPA entity class that is stored in this cache. Only one class can be specified for each configuration.
Report a bug

18.8.3. Storing Metadata in the Database
リンクのコピー

When storeMetadata is set to true (default value), meta information about the entries such as expiration, creation and modification timestamps, and versioning is stored in the database. JBoss Data Grid stores the metadata in an additional table named __ispn_metadata__ because the entity table has a fixed layout that cannot accommodate the metadata.
The structure of this table depends on the database in use. Enable the automatic creation of this table using the same database as the test environment and then transfer the structure to the production database.

Procedure 18.7. Configure persistence.xml for Metadata Entities

  1. Using Hibernate as the JPA implementation allows automatic creation of these tables using the property hibernate.hbm2ddl.auto in persistence.xml as follows: 
    <property name="hibernate.hbm2ddl.auto" value="update"/>
    Copy to Clipboard Toggle word wrap
  2. Declare the metadata entity class to the JPA provider by adding the following to persistence.xml: 
    <class>org.infinispan.persistence.jpa.impl.MetadataEntity</class>
    Copy to Clipboard Toggle word wrap
As outlined, metadata is always stored in a new table. If metadata information collection and storage is not required, set the storeMetadata attribute to false in the JPA Store configuration.
Report a bug

18.8.4. Deploying JPA Cache Stores in Various Containers
リンクのコピー

Red Hat JBoss Data Grid's JPA Cache Store implementations are deployed normally for all supported containers, except Red Hat JBoss Enterprise Application Platform. JBoss Data Grid's JBoss EAP modules contain the JPA cache store and related libraries (such as Hibernate). As a result, the relevant libraries are not packaged inside the application, but instead the application refers to the libraries in the JBoss EAP modules that have them installed.
These modules are not required for containers other than JBoss EAP. As a result, all the relevant libraries are packaged in the application's WAR/EAR file.

Procedure 18.8. Deploy JPA Cache Stores in JBoss EAP

  • To add dependencies from the JBoss Data Grid modules to the application's classpath, provide the JBoss EAP deployer a list of dependencies in one of the following ways:
    1. Add a dependency configuration to the MANIFEST.MF file: 
      Manifest-Version: 1.0
Dependencies: org.infinispan:jdg-6.4 services, org.infinispan.persistence.jpa:jdg-6.4 services
      Copy to Clipboard Toggle word wrap
    2. Add a dependency configuration to the jboss-deployment-structure.xml file: 
      <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
    <deployment>
        <dependencies>
            <module name="org.infinispan" slot="jdg-6.4" services="export"/>
        </dependencies>
    </deployment>
</jboss-deployment-structure>
      Copy to Clipboard Toggle word wrap

Important

JPA Cache Store is not supported in Apache Karaf in JBoss Data Grid 6.4.
Report a bug
トップに戻る
Red Hat logoGithubredditYoutubeTwitter

詳細情報

試用、購入および販売

コミュニティー

Red Hat ドキュメントについて

Red Hat をお使いのお客様が、信頼できるコンテンツが含まれている製品やサービスを活用することで、イノベーションを行い、目標を達成できるようにします。 最新の更新を見る.

多様性を受け入れるオープンソースの強化

Red Hat では、コード、ドキュメント、Web プロパティーにおける配慮に欠ける用語の置き換えに取り組んでいます。このような変更は、段階的に実施される予定です。詳細情報: Red Hat ブログ.

会社概要

Red Hat は、企業がコアとなるデータセンターからネットワークエッジに至るまで、各種プラットフォームや環境全体で作業を簡素化できるように、強化されたソリューションを提供しています。

Theme

© 2025 Red Hat