Data Grid Server Guide

Procedure

1. Access the Red Hat customer portal.
2. Download Red Hat Data Grid 8.1 Server from the software downloads section.

3. Run the md5sum or sha256sum command with the server download archive as the argument, for example:

   $ sha256sum jboss-datagrid-${version}-server.zip

   Copy to Clipboard Toggle word wrap
4. Compare with the MD5 or SHA-256 checksum value on the Data Grid Software Details page.

Procedure

1. Open a terminal in $RHDG_HOME.
2. Create and modify Data Grid users with the user command.

Procedure

1. Open a terminal in $RHDG_HOME.

2. Run Data Grid Server with the server script.

   Linux

   $ bin/server.sh

   Copy to Clipboard Toggle word wrap

   Microsoft Windows

   bin\server.bat

   Copy to Clipboard Toggle word wrap

Verification

1. Open 127.0.0.1:11222/console/ in any browser.
2. Enter your credentials at the prompt then continue to Data Grid Console.

Procedure

1. Open a terminal in $RHDG_HOME.

2. Copy the root directory to server2.

   $ cp -r server server2

   Copy to Clipboard Toggle word wrap

3. Specify a port offset and the server2 directory.

   $ bin/server.sh -o 100 -s server2

   Copy to Clipboard Toggle word wrap

Procedure

1. Create a CLI connection to Data Grid.

2. Shut down Data Grid Server in one of the following ways:

   • Stop all nodes in a cluster with the shutdown cluster command, for example:

     [//containers/default]> shutdown cluster

     Copy to Clipboard Toggle word wrap

     This command saves cluster state to the data folder for each node in the cluster. If you use a cache store, the shutdown cluster command also persists all data in the cache.

   • Stop individual server instances with the shutdown server command and the server hostname, for example:

     [//containers/default]> shutdown server <my_server01>

     Copy to Clipboard Toggle word wrap

Procedure

1. Remove any security-realm attributes from the endpoints configuration.
2. Ensure that the Hot Rod and REST connectors do not include any authentication definitions.

Procedure

1. Locate the default JGroups stacks, default-jgroups-*.xml, in the default-configs directory inside the infinispan-core-11.0.9.Final-redhat-00001.jar file.

   The jar file is in the $RHDG_HOME/lib directory.

2. Do one of the following:

   • Use the stack attribute in your infinispan.xml file.

     <infinispan>
       <cache-container default-cache="replicatedCache">
         <transport cluster="${infinispan.cluster.name}"
                    stack="udp" 

     1

     
                    node-name="${infinispan.node.name:}"/>
       </cache-container>
     </infinispan>

     Copy to Clipboard Toggle word wrap

     1

     Uses default-jgroups-udp.xml for cluster transport.

   • Use the cluster-stack argument when you start the server:

     $ bin/server.sh --cluster-stack=udp

     Copy to Clipboard Toggle word wrap

Procedure

1. Create a new JGroups stack declaration in your infinispan.xml file.

   <infinispan>
     <jgroups>
       <stack name="my-stack"> 

   1

   
       </stack>
     </jgroups>
   </infinispan>

   Copy to Clipboard Toggle word wrap

   1

   Creates a custom JGroups stack named "my-stack".

2. Add the extends attribute and specify a JGroups stack to inherit properties from.

   <infinispan>
     <jgroups>
       <stack name="my-stack" extends="tcp"> 

   1

   
       </stack>
     </jgroups>
   </infinispan>

   Copy to Clipboard Toggle word wrap

   1

   Inherits from the default TCP stack.

3. Use the stack.combine attribute to modify properties for protocols configured in the inherited stack.

4. Use the stack.position attribute to define the location for your custom stack.

   For example, you might evaluate using a Gossip router and symmetric encryption with the default TCP stack as follows:

   <jgroups>
     <stack name="my-stack" extends="tcp">
       <TCPGOSSIP initial_hosts="${jgroups.tunnel.gossip_router_hosts:localhost[12001]}"
                stack.combine="REPLACE"
                stack.position="MPING" /> 

   1

   
       <FD_SOCK stack.combine="REMOVE"/> 

   2

   
       <VERIFY_SUSPECT timeout="2000"/> 

   3

   
       <SYM_ENCRYPT sym_algorithm="AES"
                    keystore_name="mykeystore.p12"
                    keystore_type="PKCS12"
                    store_password="changeit"
                    key_password="changeit"
                    alias="myKey"
                    stack.combine="INSERT_AFTER"
                    stack.position="VERIFY_SUSPECT" /> 

   4

   
     </stack>
   </jgroups>

   Copy to Clipboard Toggle word wrap

   1

   Uses the TCPGOSSIP protocol as the discovery mechanism instead of MPING.

   2

   Removes the FD_SOCK protocol from the stack.

   3

   Modifies the timeout value for the VERIFY_SUSPECT protocol.

   4

   Adds the SYM_ENCRYPT protocol to the stack after the VERIFY_SUSPECT protocol.

5. Specify the stack name as the value for the stack attribute in the transport configuration.

   <infinispan>
     <jgroups>
       <stack name="my-stack" extends="tcp">
        ...
       </stack>
       <cache-container name="default" statistics="true">
         <transport cluster="${infinispan.cluster.name}"
                    stack="my-stack" 

   1

   
                    node-name="${infinispan.node.name:}"/>
      </cache-container>
     </jgroups>
   </infinispan>

   Copy to Clipboard Toggle word wrap

   1

   Configures Data Grid to use "my-stack" for cluster transport.

6. Check Data Grid logs to ensure it uses the stack.

   [org.infinispan.CLUSTER] ISPN000078: Starting JGroups channel cluster with stack my-stack

   Copy to Clipboard Toggle word wrap

Procedure

1. Add custom JGroups stack files to the $RHDG_HOME/server/conf directory.

   Alternatively you can specify an absolute path when you declare the external stack file.

2. Reference the external stack file with the stack-file element.

   <infinispan>
     <jgroups>
        <stack-file name="prod-tcp" path="prod-jgroups-tcp.xml"/> 

   1

   
     </jgroups>
     <cache-container default-cache="replicatedCache">
       <transport stack="prod-tcp" /> 

   2

   
       <replicated-cache name="replicatedCache"/>
     </cache-container>
     ...
   </infinispan>

   Copy to Clipboard Toggle word wrap

   1

   Creates a stack named "prod-tcp" that uses the "prod-jgroups-tcp.xml" definition.

   2

   Configures Data Grid to use "prod-tcp" for cluster transport.

Procedure

1. Navigate to <server_hostname>:11222/console/ in any browser.
2. Log in to the console.
3. Open the Data Container view.
4. Select Create Cache and then add a cache from a template or with Data Grid configuration in XML or JSON format.
5. Return to the Data Container view and verify your Data Grid cache.

Procedure

1. Create a CLI connection to Data Grid.

2. Add cache definitions with the create cache command.

   • Add a cache definition from an XML or JSON file with the --file option.

     [//containers/default]> create cache --file=configuration.xml mycache

     Copy to Clipboard Toggle word wrap

   • Add a cache definition from a template with the --template option.

     [//containers/default]> create cache --template=org.infinispan.DIST_SYNC mycache

     Copy to Clipboard Toggle word wrap
     Tip

     Press the tab key after the --template= argument to list available cache templates.

3. Verify the cache exists with the ls command.

   [//containers/default]> ls caches
   mycache

   Copy to Clipboard Toggle word wrap

4. Retrieve the cache configuration with the describe command.

   [//containers/default]> describe caches/mycache

   Copy to Clipboard Toggle word wrap

Procedure

1. Configure your client with the ConfigurationBuilder class.

   import org.infinispan.client.hotrod.RemoteCacheManager;
   import org.infinispan.client.hotrod.DefaultTemplate;
   import org.infinispan.client.hotrod.configuration.ConfigurationBuilder;
   import org.infinispan.commons.configuration.XMLStringConfiguration;
   ...
   
   ConfigurationBuilder builder = new ConfigurationBuilder();
   builder.addServer()
            .host("127.0.0.1")
            .port(11222)
          .security().authentication()
             .enable()
             .username("username")
             .password("password")
             .realm("default")
             .saslMechanism("DIGEST-MD5");
   
   manager = new RemoteCacheManager(builder.build());

   Copy to Clipboard Toggle word wrap
2. Use the XMLStringConfiguration class to add cache definitions in XML format.

3. Call the getOrCreateCache() method to add the cache if it already exists or create it if not.

   private void createCacheWithXMLConfiguration() {
       String cacheName = "CacheWithXMLConfiguration";
       String xml = String.format("<infinispan>" +
                                     "<cache-container>" +
                                     "<distributed-cache name=\"%s\" mode=\"SYNC\"
                                     statistics=\"true\">" +
                                       "<locking isolation=\"READ_COMMITTED\"/>" +
                                       "<transaction mode=\"NON_XA\"/>" +
                                       "<expiration lifespan=\"60000\" interval=\"20000\"/>" +
                                     "</distributed-cache>" +
                                     "</cache-container>" +
                                   "</infinispan>"
                                   , cacheName);
       manager.administration().getOrCreateCache(cacheName, new XMLStringConfiguration(xml));
       System.out.println("Cache created or already exists.");
   }

   Copy to Clipboard Toggle word wrap

4. Create caches with org.infinispan templates as in the following example with the createCache() invocation:

   private void createCacheWithTemplate() {
       manager.administration().createCache("myCache", "org.infinispan.DIST_SYNC");
       System.out.println("Cache created.");
   }

   Copy to Clipboard Toggle word wrap