Getting Started Guide

1. The Persistent Store is an optional component. It can permanently store the cached entries for restoration after a data grid shutdown.
2. The Level 1 Cache (or L1 Cache) stores remote cache entries after they are initially accessed, preventing unnecessary remote fetch operations for each subsequent use of the same entries.
3. The Cache Manager controls the life cycle of Cache instances and can store and retrieve them when required.
4. The Cache is the main component for storage and retrieval of the key-value entries.

Install OpenJDK on Red Hat Enterprise Linux

1. Subscribe to the Base Channel

   Obtain the OpenJDK from the RHN base channel. Your installation of Red Hat Enterprise Linux is subscribed to this channel by default.

2. Install the Package

   Use the yum utility to install OpenJDK:

   $ sudo yum install java-1.8.0-openjdk-devel

3. Verify that OpenJDK is the System Default

   Ensure that the correct JDK is set as the system default as follows:

   1. Log in as a user with root privileges and run the alternatives command:

      $ /usr/sbin/alternatives --config java

   2. Select /usr/lib/jvm/java-1.8.0-openjdk-${java-version}.x86_64/bin/java .

   3. Use the following command to set javac :

      $ /usr/sbin/alternatives --config javac

   4. Select /usr/lib/jvm/java-1.8.0-openjdk-${java-version}.x86_64/bin/javac .

1. WebLogic Server 12c.
2. JBoss Data Grid Library (Embedded) mode.

Deploying Web Applications on a WebLogic Server

1. Create Web Applications

   Create a web application and add the libraries in the WEB-INF folder.

2. Create a weblogic.xml Deployment Descriptor

   Create a weblogic.xml deployment descriptor with the following elements in it:

   <?xml version="1.0" encoding="UTF-8"?>
   <weblogic-web-app
           xmlns="http://www.bea.com/ns/weblogic/90"
           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
           xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd">
       <container-descriptor>
           <prefer-web-inf-classes>true</prefer-web-inf-classes>
       </container-descriptor>
   </weblogic-web-app>

   注記

   The prefer-web-inf-classes class indicates that the libraries and the classes in the WEB-INF/lib folder is preferred over the default libraries bundled in the WebLogic server. For example, the commons-pool.jar file in the WebLogic server has version 1.4 and is automatically loaded by the classloader, but the Hot Rod client uses a newer version of this library.

3. Pack the Web Application into a Web Archive File

   Create a web application archive (WAR) file of the web application and verify that the JBoss Data Grid libraries are in the WEB-INF folder along with the WebLogic deployment descriptor file.

4. Deploy the Application onto the WebLogic Server

   To deploy the web application using the Infinispan CDI module, stop the WebLogic server if it is running, apply the patch on it (Patch file p17424706_121200_Generic.zip ) and restart the WebLogic server. If the Infinispan CDI module is not being used, deploy the web application normally.

   For more information about applying patch to the WebLogic Server, see the Oracle patch database on the Oracle website.

Deploying Web Applications on a WebLogic Server

1. To install the WebLogic server, see http://docs.oracle.com/cd/E24329_01/doc.1211/e24492/toc.htm.
2. Configure JBoss Data Grid in Remote Client-Server mode, define cache, cache container, and endpoint configuration. After configuration, start JBoss Data Grid to confirm that the Hot Rod endpoint is listening on the configured port. For information about configuring JBoss Data Grid in Remote Client-Server, see Run Red Hat JBoss Data Grid in Remote Client-Server Mode.
3. Create a web application and add the infinispan-remote library as a dependency if Maven is used.

4. Create a weblogic.xml deployment descriptor with the following elements in it:

   <?xml version="1.0" encoding="UTF-8"?>
   <weblogic-web-app
           xmlns="http://www.bea.com/ns/weblogic/90"
           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
           xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd">
       <container-descriptor>
           <prefer-web-inf-classes>true</prefer-web-inf-classes>
       </container-descriptor>
   </weblogic-web-app>

   注記

   The prefer-web-inf-classes class indicates that the libraries and classes in the WEB-INF/lib folder are preferred over the default libraries bundled in the WebLogic server. For example, the commons-pool.jar file in the WebLogic server has version 1.4 and is automatically loaded by the classloader, however the Hot Rod client uses a newer version of this library.

5. Add deployment descriptor file in the WEB-INF folder.

6. Ensure that the infinispan-remote dependency is added to the pom.xml file, then use a Maven plugin to create a web archive.

   Alternatively, create the web archive manually and add the library manually.

7. Deploy the application in the WebLogic server and verify that the Hot Rod client embedded inside the web application connects to the remote JBoss Data Grid server.

1. Add infinispan-remote dependency:

   <dependency>
      <groupId>org.infinispan</groupId>
      <artifactId>infinispan-remote</artifactId>
      <version>${infinispan.version}</version>
   </dependency>

2. For instances where a Remote Cache Store is in use also add the infinispan-embedded dependency as shown below:

   <dependency>
      <groupId>org.infinispan</groupId>
      <artifactId>infinispan-embedded</artifactId>
      <version>${infinispan.version}</version>
   </dependency>

3. For instances where JSR-107 is in use, ensure that the cache-api packages are available at runtime. Having these packages available can be accomplished by any of the following methods:

   1. Option 1: If JBoss EAP is in use, then add the JBoss Data Grid modules to this instance as described in .

      Add the javax.cache.api module to the application’s jboss-deployment-structure.xml. An example is shown below:

      <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
          <deployment>
              <dependencies>
                  <module name="javax.cache.api" slot="jdg-7.1" services="export"/>
              </dependencies>
          </deployment>
      </jboss-deployment-structure>

   2. Option 2: Download the jboss-datagrid-${jdg.version}-library file from the customer portal.

      Extract the downloaded archive.

      Embed the jboss-datagrid-${jdg.version}-library/lib/cache-api-${jcache.version}.jar file into the desired application.

   3. Option 3: If the JBoss Data Grid Maven repository is available then add an explicit dependency to the pom.xml of the project as seen below:

      <dependency>
          <groupId>javax.cache</groupId>
          <artifactId>cache-api</artifactId>
          <version>${jcache.version}</version>
      </dependency>

Find the JBoss Data Grid Sample Configuration for a Node Without Endpoints

1. Extract the JBoss Data Grid ZIP

   Extract the ZIP file for JBoss Data Grid Remote Client-Server mode. This is named jboss-datagrid-server-${version} . Add the relevant version to the file name.

2. Navigate to the Appropriate Folder

   In the extracted folder, navigate to the $JDG_HOME/docs/examples/config folder.

3. Find the Configuration File Sample

   View the clustered-storage-only.xml file, which contains the configuration for a node with no endpoints.

1. Remove the datagrid subsystem.
2. Remove the modcluster subsystem.
3. Remove the datasource definition.
4. Remove socket-bindings for mod_cluster, Hot Rod and memcached .

Run the Quickstart Class

1. Open the Quickstart.java File

   Open the file called Quickstart.java in the infinispan-quickstart/embedded-cache.

2. Add the Quickstart Class

   Examining the Quickstart.java file we can see that this class creates a DefaultCacheManager and then obtains a local reference to the default cache, as no cache name is specified:

   package org.infinispan.quickstart.embeddedcache;
   
   import org.infinispan.Cache;
   import org.infinispan.manager.DefaultCacheManager;
   
   public class Quickstart {
   
      public static void main(String args[]) throws Exception {
         Cache<Object, Object> c = new DefaultCacheManager().getCache();
      }
   
   }

3. Copy Dependencies and Compile Java Classes

   Use the following command to copy all project dependencies to a directory and compile the Java classes from your project:

   $ mvn clean compile dependency:copy-dependencies -DstripVersion

4. Run the Main Method

   Use the following command to run the main method:

   $ java -cp target/classes/:target/dependency/* package org.infinispan.quickstart.embeddedcache.Quickstart

Monitor JBoss Data Grid Applications in JBoss Enterprise Application Platform

1. Configure RHQ/JBoss Operations Network

   Add an RHQ/JBoss Operations Network specific property (named org.rhq.resourceKey) to the /bin/[path]standalone.conf file as follows:

   JAVA_OPTS="$JAVA_OPTS -Dorg.rhq.resourceKey=MyEAP"

   This command adds the property to the JBoss Enterprise Application Platform’s command line indirectly.

2. Check RHQ/JBoss Operations Network is Running Using a Full JDK

   Ensure that the RHQ/JBoss Operations Network agent started using a full JDK instead of a JRE. This is because the agent requires access to the JDK’s tools.jar file.

   To configure your RHQ/JBoss Operations Network agent to use the JDK, follow the instructions relevant to your operating system:

   1. For Linux users, set the RHQ_AGENT_JAVA_HOME environment variable to the JDK home directory in the agent’s rhq-agent-env.sh file.
   2. For Windows users, set the RHQ_AGENT_JAVA_HOME environment variable to the JDK home directory in the agent’s rhq-agent-env.bat file.

3. Ensure the Agent is Local to the JBoss Enterprise Application Platform Instance

   Ensure that the RHQ/JBoss Operations Network agent runs locally to and under the same user as the JBoss Application Platform instance. This is required for the Java Attach API to connect to the process.

4. Import Resources to the Agent Inventory

   RHQ/JBoss Operations Network can now discover resources. These resources can subsequently be imported into the agent inventory.

   When a JBoss Data Grid user deployment enables JMX statistics to expose JBoss Data Grid Cache Managers or caches, the resources appear as children resources of the JBoss Enterprise Application Platform instance.

Start the First Application Server Instance

1. Navigate to the Root Directory

   In the command line terminal, navigate to the root for your JBoss server directory.

2. Start the First Application Server

   Depending on your operating system, use the appropriate command from the following to start the first instance of your selected application server:

   1. For Linux:

      $JBOSS_HOME/bin/standalone.sh

   2. For Windows:

      $JBOSS_HOME\bin\standalone.bat

Start the Second Application Server Instance

1. Clone the Application Server

   Create a copy of the selected JBoss Server to create a second instance.

2. Navigate to the Root Directory

   In the command line terminal, navigate to the root for your JBoss server directory.

3. Start the Second Application Server

   Use the appropriate command for your operating system from the following commands. This command starts the server with the provided port offset to ensure that both the server instances run on the same host.

   1. For Linux:

      $JBOSS_HOME2/bin/standalone.sh -Djboss.socket.binding.port-offset=100

   2. For Windows:

      $JBOSS_HOME2\bin\standalone.bat -Djboss.socket.binding.port-offset=100

Build and Deploy the Hello World Quickstart

1. Navigate to the Required Directory

   In the command line terminal, navigate to the root directory of the quickstart on the command line interface.

2. Build and Deploy to the First Application Server Instance

   Use the following command to build and deploy the quickstart to the first application server instance as follows:

   # mvn clean package wildfly:deploy

   This command deploys target/[path]jboss-helloworld-jdg.war to the first running server instance.

3. Build and Deploy the Second Application Server Instance

   Use the following command to build and deploy the quickstart to the second application server instance with the specified ports as follows:

   # mvn clean package wildfly:deploy -Dwildfly.port=10090

   This command deploys target/[path]jboss-helloworld-jdg.war to the second running server instance.

Test Replication on the Application

1. Access the First Server

   Access the first application server and enter the key and value.

   1. Access the first application server in a browser window using the following URL:

      http://localhost:8080/jboss-helloworld-jdg

   2. Insert the key foo.
   3. Insert the value bar.

2. Access the Second Server

   Access the second application server and enter the key and value.

   1. Access the second application server in a browser window using the following URL:

      http://localhost:8180/jboss-helloworld-jdg

   2. Click Get Some.
   3. Get the key foo.
   4. Click Put Some More.
   5. Insert the key mykey.
   6. Insert the value myvalue.

3. Get All Keys and Values

   Access the first server and request all keys.

   1. Access the first application server in a browser window using the following URL:

      http://localhost:8080/jboss-helloworld-jdg

   2. Click Get Some.
   3. Click Get All to request all key and values.

Remove the Application

1. Start the Application Servers

   Ensure that both server instances are running.

2. Navigate to the Root

   In the command line terminal, navigate to the root directory of the quickstart.

3. Remove the Archive

   Use the following commands to remove the archive from both the server instances.

   1. Remove the archive from the first server as follows:

      mvn wildfly:undeploy

   2. Remove the archive from the second server as follows:

      mvn wildfly:undeploy -Dwildfly.port=10090

1. Obtain the most recent supported JBoss Data Grid Remote Client-Server Mode distribution files from Red Hat.
2. Ensure that the JBoss Data Grid and JBoss Enterprise Application Platform Maven repositories are installed and configured. For details, see Install and Use the Maven Repositories.

Build the Football Application

1. Add Configurations

   Edit the standalone.xml file (located at $JDG_HOME/standalone/configuration/ ) to add definitions for the datasource and infinispan subsystems.

   1. Add the following subsystem definition for the datasource:

      <subsystem xmlns="urn:jboss:domain:datasources:4.0">
      
      <!-- Define this Datasource with jndi
      name java:jboss/datasources/ExampleDS -->
      
          <datasources>
              <datasource jndi-name="java:jboss/datasources/ExampleDS"
      		    pool-name="ExampleDS"
      		    enabled="true"
      		    use-java-context="true">
      
                  <!-- The connection URL uses H2 Database
      		Engine with in-memory database called test -->
      
                  <connection-url>jdbc:h2:mem:test;DB_CLOSE_DELAY=-1</connection-url>
      
                  <!-- JDBC driver name -->
                  <driver>h2</driver>
      
                  <!-- Credentials -->
                  <security>
                      <user-name>sa</user-name>
                      <password>sa</password>
                  </security>
              </datasource>
      
              <!-- Define the JDBC driver called 'h2' -->
              <drivers>
                  <driver name="h2" module="com.h2database.h2">
                      <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>
                  </driver>
              </drivers>
      
          </datasources>
      </subsystem>

   2. Add the following subsystem definition for infinispan:

      <subsystem xmlns="urn:infinispan:server:core:8.0"
      	     default-cache-container="local">
      
      	<cache-container name="local"
      			 default-cache="default"
      			 statistics="true">
      
      	        <local-cache name="default"
      			     statistics="true">
      			<locking isolation="NONE"
      				 acquire-timeout="30000"
      				 concurrency-level="1000"
      				 striping="false"/>
      		</local-cache>
      
      		<local-cache name="memcachedCache"
      			     statistics="true">
      			<locking isolation="NONE"
      				 acquire-timeout="30000"
      				 concurrency-level="1000"
      				 striping="false"/>
      		</local-cache>
      
      	        <local-cache name="namedCache"
      			     statistics="true"/>
      
      	        <!-- ADD a local cache called 'teams' -->
      
      		<local-cache name="teams"
      	         	     statistics="true">
      
      	            <!-- Define the JdbcBinaryStores
      			to point to the ExampleDS previously
      			defined -->
      
      			<string-keyed-jdbc-store
      				datasource="java:jboss/datasources/ExampleDS"
       				passivation="false"
      				preload="false"
      				purge="false">
      
      		                <!-- Define the database dialect -->
      		                <property name="databaseType">H2</property>
      
      	                <!-- specifies information about
      			     database table/column names
      			     and data types -->
      
      				<string-keyed-table prefix="JDG">
      		                   <id-column name="id"
      				              type="VARCHAR"/>
      				   <data-column name="datum"
      				                type="BINARY"/>
      				   <timestamp-column name="version"
      				                     type="BIGINT"/>
      				</string-keyed-table>
      			</string-keyed-jdbc-store>
      	        </local-cache>
      
      	        <!-- End of local cache called 'teams' definition -->
      	</cache-container>
      </subsystem>

   注記

   The Hot Rod and REST endpoints use the cache named teams and memcached endpoint uses memcachedCache as a default.

2. Disable REST Security

   As a default, the standalone.xml configuration file protects the REST endpoint with BASIC authentication. This quickstart cannot perform authentication, therefore the REST authentication must be disabled in the REST connector by removing the security-domain and auth-method parameters. The resulting configuration (with REST authentication disabled) is as follows:

   <rest-connector virtual-server="default-host"
                   cache-container="local" />

   For more details about security, see the REST Authentication Chapter in JBoss Data Grid’s Developer Guide .

3. Edit the Submodule Configuration File

   Each submodule (specifically hotrod-endpoint, rest-endpoint and memcached-endpoint) contains a configuration file (located at $JDG_QUICKSTART/src/main/resources/[path]jdg.properties ). Modify the default values in the configuration file to set the values required for your specific JBoss Data Grid installation.

4. Navigate to the Root Directory

   Open a command line and navigate to the root directory of this quickstart.

5. Build the Application

   Use the following command to build the example application in its directory:

   mvn clean package

   This step results in the use of Maven’s shade plugin, which bundles all dependencies into a single jar file for ease of use. This file is named {PROTOCOL}-endpoint-quickstart.jar , for example rest-endpoint-quickstart.jar for the REST version.

6. Start JBoss Data Grid

   Run the following script to run JBoss Data Grid:

   $JDG_HOME/bin/standalone.sh

7. Run the Application

   Run the example application in its directory with the following command:

   mvn exec:java

Rapid Stock Market Quickstart Server-side Configuration

1. Navigate to the Root Directory

   Open a command line and navigate to the root directory of this quickstart.

2. Build a server module for the JBoss Data Grid Server by packaging a class that is common for the client and server in a jar file:

   $ mvn clean package -Pprepare-server-module

   Place the new jar file in a directory structure that is similar to the server module.

3. Install the server module into the server.

   1. Copy the prepared module to the server:

      $ cp -r target/modules ${JDG_SERVER_HOME}/

   2. Add the new module as a dependency of the org.infinispan.commons module by adding the following into the modules/system/layers/base/org/infinispan/commons/main/module.xml file:

      <module name="org.infinispan.quickstart.compatibility.common"/>

4. Build the application:

   $ mvn clean package

5. Configure the JBoss Data Grid to use the appropriate configuration file.

   1. Copy the example configuration file for compatibility mode to a location where the JBoss Data Grid Server can locate and use it:

      $ cp ${JDG_SERVER_HOME}/docs/examples/configs/standalone-compatibility-mode.xml ${JDG_SERVER_HOME}/standalone/configuration

   2. Remove the security-domain and auth-method attributes from the rest-connector element to disable REST security.

6. Start the JBoss Data Grid Server in compatibility mode:

   $ ${JDG_SERVER_HOME}/bin/standalone.sh -c standalone-compatibility-mode.xml

Rapid Stock Market Quickstart Client-side Configuration

1. In a new command line terminal window, start the client-side application:

   $ mvn exec:java -Pclient

2. Use the instructions in the help menu for the client application.

Configure and Start the Servers in standalone mode

1. Prepare an instance of JBoss EAP for copying:

   1. Unzip jboss-datagrid-${version}-eap-modules-library.zip.

   2. Copy the modules to the server modules directory:

      • For Linux:

        cp -a jboss-datagrid-${version}-eap-modules-library/modules EAP_HOME

        For Windows:

         xcopy /e/i/f jboss-datagrid-${version}-eap-modules-library/modules EAP_HOME\modules

   3. Add a user to each server for EJB access:

      • For Linux: EAP_HOME/bin/add-user.sh -a -u quickuser -p quick-123
      • For Windows: EAP_HOME\bin\add-user.bat -a -u quickuser -p quick-123
2. Copy the prepared JBoss EAP server to 4 different directories labeled EAP_HOME[1-4].
3. Open a command line for each of the 4 nodes and navigate to the root of the JBoss EAP server directory.

4. Start all four of the JBoss EAP servers using the following commands:

   • For Linux:

     EAP_HOME1/bin/standalone.sh -Djboss.node.name=node1
     EAP_HOME2/bin/standalone.sh -Djboss.node.name=node2 -Djboss.socket.binding.port-offset=100
     EAP_HOME3/bin/standalone.sh -Djboss.node.name=node3 -Djboss.socket.binding.port-offset=200 -c standalone-ha.xml
     EAP_HOME4/bin/standalone.sh -Djboss.node.name=node4 -Djboss.socket.binding.port-offset=300 -c standalone-ha.xml

   • For Windows:

     EAP_HOME1\bin\standalone.bat -Djboss.node.name=node1
     EAP_HOME2\bin\standalone.bat -Djboss.node.name=node2 -Djboss.socket.binding.port-offset=100
     EAP_HOME3\bin\standalone.bat -Djboss.node.name=node3 -Djboss.socket.binding.port-offset=200 -c standalone-ha.xml
     EAP_HOME4\bin\standalone.bat -Djboss.node.name=node4 -Djboss.socket.binding.port-offset=300 -c standalone-ha.xml

5. Add the configuration for node2 (AppOne) to use EJB server-to-server invocation:

   • For Linux:

     EAP_HOME2/bin/jboss-cli.sh -c --controller=localhost:10099 --file=QUICKSTART_HOME/install-appOne-standalone.cli

     For Windows:

     EAP_HOME2\bin\jboss-cli.bat -c --controller=localhost:10099 --file=QUICKSTART_HOME/install-appOne-standalone.cli

Configure and Start the Servers in domain mode

1. Copy a fresh JBoss EAP installation to EAP_HOME:

   1. Unzip jboss-datagrid-${version}-eap-modules-library.zip.

   2. Copy the modules to the server modules directory:

      • For Linux:

        cp -a jboss-datagrid-${version}-eap-modules-library/modules EAP_HOME

      • For Windows:

        xcopy /e/i/f jboss-datagrid-${version}-eap-modules-library/modules EAP_HOME\modules

2. Open a command line and navigate to the root of JBoss EAP.

3. Add a user:

   • For Linux:

     EAP_HOME/bin/add-user.sh -a -u quickuser -p quick-123

   • For Windows:

     EAP_HOME\bin\add-user.bat -a -u quickuser -p quick-123

4. The following shows the command to start the domain:

   • For Linux:

     EAP_HOME/bin/domain.sh

   • For Windows:

     EAP_HOME\bin\domain.bat

5. Apply the configuration for the quickstart, the domain will contain 4 nodes:

   • For Linux:

     EAP_HOME/bin/jboss-cli.sh -c --file=QUICKSTART_HOME/install-domain.cli

   • For Windows:

     EAP_HOME\bin\jboss-cli.bat -c --file=QUICKSTART_HOME/install-domain.cli

Build the Application

1. Open a command line and navigate to the root directory of this quickstart.

2. Execute the following command to build the archive:

   mvn clean install

3. Copy the application to the appropriate server:

   • For Linux:

     cp adminApp/ear/target/jboss-eap-application-adminApp.ear EAP_HOME1/standalone/deployments
     cp appOne/ear/target/jboss-eap-application-AppOne.ear EAP_HOME2/standalone/deployments
     cp appTwo/ear/target/jboss-eap-application-AppTwo.ear EAP_HOME3/standalone/deployments
     cp appTwo/ear/target/jboss-eap-application-AppTwo.ear EAP_HOME4/standalone/deployments

   • For Windows:

     copy adminApp\ear\target\jboss-eap-application-adminApp.ear EAP_HOME1\standalone\deployments
     copy appOne\ear\target\jboss-eap-application-AppOne.ear EAP_HOME2\standalone\deployments
     copy appTwo\ear\target\jboss-eap-application-AppTwo.ear EAP_HOME3\standalone\deployments
     copy appTwo\ear\target\jboss-eap-application-AppTwo.ear EAP_HOME4\standalone\deployments

4. When domain mode is used, deploy the applications in the following way:

   • For Linux:

     EAP_HOME/bin/jboss-cli.sh -c --file=QUICKSTART_HOME/deploy-domain.cli

   • For Windows:

     EAP_HOME\bin\jboss-cli.bat -c --file=QUICKSTART_HOME/deploy-domain.cli

Procedure: Execute the AdminClient application

1. Open a command line and navigate to the $QUICKSTART_HOME/client/ directory.

2. Execute the following command:

   mvn -Dexec.mainClass=org.jboss.as.quickstarts.datagrid.eap.app.AdminClient exec:java

   注記

   By default the application will attempt to access localhost:4447 and localhost:4547 for the AdminHost and AppOneHost. This may be changed by adding the following parameter to the mvn command:

   -Dexec.args="AdminHost AdminPort AppOneHost AppOnePort"

3. Confirm that the following text appears in the console; any unexpected results will raise an Exception:

   Add a value to App1Cache with the AdminApp and check on the same instance that the value is correct added
       success
   Check the previous added value of App1Cache by accessing the AppOne Server
       success
   Add a value to App2Cache and check on the same instance that the value is correct added
       success
   Check whether changes to a cache are rollbacked if the transaction fail
       The cache App2 work as expected on rollback

Execute the AppOneClient

1. Open a command line and navigate to the $QUICKSTART_HOME/client/ directory.

2. Execute the following command:

   mvn -Dexec.mainClass=org.jboss.as.quickstarts.datagrid.eap.app.AppOneClient exec:java

   注記

   By default the application will attempt to access localhost:4447 and localhost:4547 for the AdminHost and AppOneHost. This may be changed by adding the following parameter to the mvn command:

   -Dexec.args="AdminHost AdminPort AppOneHost AppOnePort"

3. Confirm that the following text appears in the console; any unexpected results will raise an Exception:

   Add a value to App2Cache with the AdminApp
   Access the App2Cache from the AppOneServer by using the clustered EJB@AppTwoServer
       success : received the following node names for EJB invocation : [node3, node4]

1. Download the Fuse Full Install binary from the Red Hat Customer Portal.

2. Export the path to the folder where the CSV files will be placed by running the command:

   export incomingFolderPath=[Full path to the CSV folder]

3. Run the following command in the root directory of the quickstart:

   mvn clean install -DincomingFolderPath=$incomingFolderPath

4. Set the FUSE_INSTALL_PATH and FUSE_BINARY_PATH variables in the same shell:

   export FUSE_INSTALL_PATH = [Full path to the folder where Fuse will be installed]
   export FUSE_BINARY_PATH = [Full path to the Fuse zip file downloaded in step 1]

5. If running the camel-jbossdatagrid-fuse quickstart in JBoss Fuse 6.2.1 the following changes to the setupEverythingOnFuse.sh script must be made; otherwise proceed to the next step:

   1. Change the version of Fuse being exported to reference the 6.2.1 component.
   2. Update the container name to child1.

   # Original line with old version
   # export FUSE_VERSION=jboss-fuse-6.2.0.redhat-133
   # Updated line for Fuse 6.2.1:
   export FUSE_VERSION=jboss-fuse-6.2.1.redhat-084
   
   [...]
   
   # Original line exporting the profile
   #sh client -r 2 -d 10 "fabric:container-add-profile child demo-local_producer" > /dev/null 2>&1
   # Updated line for Fuse 6.2.1:
   sh client -r 2 -d 10 "fabric:container-add-profile child1 demo-local_producer" > /dev/null 2>&1

6. Once the environment variables are set run the following from the root directory of the quickstart:

   ./setupEverythingOnFuse.sh

7. After the script completes confirm that the Fuse Hawtio Console may be accessed without error. This console, by default, runs at http://127.0.0.1:8181/hawtio/index.html#/login; the username and password are both admin.
8. Confirm that both the child1 and child2 containers were created by accessing Fuse Fabric at http://127.0.0.1:8181/hawtio/index.html#/fabric/containers . Both containers should be highlighted in green to indicate they are ready.

Remove JBoss Data Grid from Your Linux System

1. Shut Down Server

   Ensure that the JBoss Data Grid server is shut down.

2. Navigate to the JBoss Data Grid Home Directory

   Use the command line to change into the level above the $JDG_HOME folder.

3. Delete the JBoss Data Grid Home Directory

   Enter the following command in the terminal to remove JBoss Data Grid, replacing $JDG_HOME with the name of your JBoss Data Grid home directory:

   $ rm -Rf $JDG_HOME

Remove JBoss Data Grid from Your Windows System

1. Shut Down Server

   Ensure that the JBoss Data Grid server is shut down.

2. Navigate to the JBoss Data Grid Home Directory

   Use the Windows Explorer to navigate to the directory in which the $JDG_HOME folder is located.

3. Delete the JBoss Data Grid Home Directory

   Select the $JDG_HOME folder and delete it.