4.2. Deploy JBoss Data Grid in JBoss EAP (Remote Client-Server Mode)
4.2. Deploy JBoss Data Grid in JBoss EAP (Remote Client-Server Mode) Red Hat JBoss Data Grid provides a set of modules for Red Hat JBoss Enterprise Application Platform 6.x. Using these modules means that JBoss Data Grid libraries do not need to be included in the user deployment. To avoid conflicts with the Infinispan modules that are already included with JBoss EAP, the JBoss Data Grid modules are placed within a separate slot and identified by the JBoss Data Grid version ( major . minor ). Note The JBoss EAP modules are not included in JBoss EAP. Instead, navigate to the Customer Support Portal at http://access.redhat.com to download these modules from the Red Hat JBoss Data Grid downloads page. To deploy JBoss Data grid in JBoss EAP, add dependencies from the JBoss Data Grid module to the application's classpath (the JBoss EAP deployer) in one of the following ways: Add a dependency to the jboss-deployment-structure.xml file. Add a dependency to the MANIFEST.MF file. Add a Dependency to the jboss-deployment-structure.xml File Add the following configuration to the jboss-deployment-structure.xml file: Note For details about the jboss-deployment-structure.xml file, see the Red Hat JBoss Enterprise Application Platform documentation. Add a Dependency to the MANIFEST.MF File. Add a dependency to the MANIFEST.MF files as follows: Example 4.2. Example MANIFEST.MF File The first line remains the same as the example. Depending on the dependency required, add one of the following to the second line of the file: Basic Hot Rod client: Hot Rod client with Remote Query functionality: Report a bug 4.2.1. Using Custom Classes with the Hot Rod client Either of the following two methods may be used to use custom classes with the Hot Rod client: Option 1: Reference the deployment's class loader in the configuration builder for the Hot Rod client, as seen in the below example: Example 4.3. Referencing the custom class loader in the ConfigurationBuilder instance Option 2: Install the custom classes as their own module within JBoss EAP, and add a dependency on the newly created module should be added to the JBoss Data Grid module at USD{EAP_HOME}/modules/system/layers/base/org/infinispan/commons/jdg-6.x/module.xml . Report a bug
<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2"> <deployment> <dependencies> <module name="org.infinispan.commons" slot="jdg-6.6" services="export"/> <module name="org.infinispan.client.hotrod" slot="jdg-6.6" services="export"/> </dependencies> </deployment> </jboss-deployment-structure> Manifest-Version: 1.0 Dependencies: org.infinispan.commons:jdg-6.6 services, org.infinispan.client.hotrod:jdg-6.6 services org.infinispan.commons:jdg-6.6 services, org.infinispan.client.hotrod:jdg-6.6 services org.infinispan.commons:jdg-6.6 services, org.infinispan.client.hotrod:jdg-6.6 services, org.infinispan.query.dsl:jdg-6.6 services, org.jboss.remoting3 import org.infinispan.client.hotrod.configuration.ConfigurationBuilder; [...] ConfigurationBuilder config = new ConfigurationBuilder(); config.marshaller(new GenericJBossMarshaller(Thread.currentThread().getContextClassLoader()));