Chapter 12. Reference

Data Grid Server requires JDK 11 or later.

Use the server script to run Data Grid Server instances.

$RHDG_HOME/bin/server.sh

$RHDG_HOME/bin/server.sh

$RHDG_HOME\bin\server.bat

$RHDG_HOME\bin\server.bat

Use the shutdown command with the CLI to perform a graceful shutdown.

Alternatively, enter Ctrl-C from the terminal to interrupt the server process or kill it via the TERM signal.

Server configuration extends Data Grid configuration with the following server-specific elements:

The default configuration file is $RHDG_HOME/server/conf/infinispan.xml.

Use different configuration files with the -c argument, as in the following example that starts a server without clustering capabilities:

$RHDG_HOME/bin/server.sh -c infinispan-local.xml

$RHDG_HOME/bin/server.sh -c infinispan-local.xml

$RHDG_HOME\bin\server.bat -c infinispan-local.xml

$RHDG_HOME\bin\server.bat -c infinispan-local.xml

Data Grid Server binds to the loopback IP address localhost on your network by default.

Use the -b argument to set a different IP address, as in the following example that binds to all network interfaces:

$RHDG_HOME/bin/server.sh -b 0.0.0.0

$RHDG_HOME/bin/server.sh -b 0.0.0.0

$RHDG_HOME\bin\server.bat -b 0.0.0.0

$RHDG_HOME\bin\server.bat -b 0.0.0.0

Data Grid Server listens on port 11222 by default.

Use the -p argument to set an alternative port:

$RHDG_HOME/bin/server.sh -p 30000

$RHDG_HOME/bin/server.sh -p 30000

$RHDG_HOME\bin\server.bat -p 30000

$RHDG_HOME\bin\server.bat -p 30000

Data Grid Server configuration defines cluster transport so multiple instances on the same network discover each other and automatically form clusters.

Use the -k argument to change the IP address for cluster traffic:

$RHDG_HOME/bin/server.sh -k 192.168.1.100

$RHDG_HOME/bin/server.sh -k 192.168.1.100

$RHDG_HOME\bin\server.bat -k 192.168.1.100

$RHDG_HOME\bin\server.bat -k 192.168.1.100

JGroups stacks configure the protocols for cluster transport. Data Grid Server uses the tcp stack by default.

Use alternative cluster stacks with the -j argument, as in the following example that uses UDP for cluster transport:

$RHDG_HOME/bin/server.sh -j udp

$RHDG_HOME/bin/server.sh -j udp

$RHDG_HOME\bin\server.bat -j udp

$RHDG_HOME\bin\server.bat -j udp

Data Grid Server requires authentication.

Create a username and password with the CLI as follows:

$RHDG_HOME/bin/cli.sh user create username -p "qwer1234!"

$RHDG_HOME/bin/cli.sh user create username -p "qwer1234!"

$RHDG_HOME\bin\cli.bat user create username -p "qwer1234!"

$RHDG_HOME\bin\cli.bat user create username -p "qwer1234!"

Data Grid Server uses infinispan.server.home.path to locate the contents of the server distribution on the host filesystem.

The server home directory, referred to as $RHDG_HOME, contains the following folders:

├── bin
├── boot
├── docs
├── lib
├── server
└── static

├── bin
├── boot
├── docs
├── lib
├── server
└── static

Data Grid Server uses infinispan.server.root.path to locate configuration files and data for Data Grid Server instances.

You can create multiple server root folders in the same directory or in different directories and then specify the locations with the -s or --server-root argument, as in the following example:

$RHDG_HOME/bin/server.sh -s server2

$RHDG_HOME/bin/server.sh -s server2

$RHDG_HOME\bin\server.bat -s server2

$RHDG_HOME\bin\server.bat -s server2

Each server root directory contains the following folders:

├── server
│   ├── conf
│   ├── data
│   ├── lib
│   └── log

├── server
│   ├── conf
│   ├── data
│   ├── lib
│   └── log

Configure Data Grid Server logging with the log4j2.xml file in the server/conf folder.

Use the --logging-config=<path_to_logfile> argument to use custom paths, as follows:

$RHDG_HOME/bin/server.sh --logging-config=/path/to/log4j2.xml

$RHDG_HOME/bin/server.sh --logging-config=/path/to/log4j2.xml

$RHDG_HOME\bin\server.bat --logging-config=path\to\log4j2.xml

$RHDG_HOME\bin\server.bat --logging-config=path\to\log4j2.xml