Data Grid Command Line Interface
Access data and manage Data Grid with the CLI
Abstract
Red Hat Data Grid Copy linkLink copied to clipboard!
Data Grid is a high-performance, distributed in-memory data store.
- Schemaless data structure
- Flexibility to store different objects as key-value pairs.
- Grid-based data storage
- Designed to distribute and replicate data across clusters.
- Elastic scaling
- Dynamically adjust the number of nodes to meet demand without service disruption.
- Data interoperability
- Store, retrieve, and query data in the grid from different endpoints.
Data Grid documentation Copy linkLink copied to clipboard!
Documentation for Data Grid is available on the Red Hat customer portal.
Data Grid downloads Copy linkLink copied to clipboard!
Access the Data Grid Software Downloads on the Red Hat customer portal.
You must have a Red Hat account to access and download Data Grid software.
Making open source more inclusive Copy linkLink copied to clipboard!
Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.
Chapter 1. Getting Started with the Data Grid CLI Copy linkLink copied to clipboard!
The command line interface (CLI) lets you remotely connect to Data Grid servers to access data and perform administrative functions.
1.1. Creating and Modifying Users Copy linkLink copied to clipboard!
Data Grid Server requires users to authenticate against a default property realm. Before you can access Data Grid Server, you must add credentials by creating at least one user and a password. You can also add and modify the security authorization groups to which users belong.
Procedure
-
Open a terminal in
$RHDG_HOME. -
Create and modify Data Grid users with the
usercommand.
Run help user for more details about using the command.
Creating users and passwords
Linux
bin/cli.sh user create myuser -p "qwer1234!"
$ bin/cli.sh user create myuser -p "qwer1234!"Copy to Clipboard Copied! Toggle word wrap Toggle overflow Microsoft Windows
bin\cli.bat user create myuser -p "qwer1234!"
$ bin\cli.bat user create myuser -p "qwer1234!"Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Creating users with group membership
Linux
bin/cli.sh user create myuser -p "qwer1234!" -g supervisor,reader,writer
$ bin/cli.sh user create myuser -p "qwer1234!" -g supervisor,reader,writerCopy to Clipboard Copied! Toggle word wrap Toggle overflow Microsoft Windows
bin\cli.bat user create myuser -p "qwer1234!" -g supervisor,reader,writer
$ bin\cli.bat user create myuser -p "qwer1234!" -g supervisor,reader,writerCopy to Clipboard Copied! Toggle word wrap Toggle overflow
1.2. Connecting to Data Grid Servers Copy linkLink copied to clipboard!
Establish CLI connections to Data Grid.
Prerequisites
Add user credentials and have at least one running Data Grid server instance.
Procedure
-
Open a terminal in
$RHDG_HOME. Start the CLI.
Linux:
bin/cli.sh
$ bin/cli.shCopy to Clipboard Copied! Toggle word wrap Toggle overflow Microsoft Windows:
bin\cli.bat
$ bin\cli.batCopy to Clipboard Copied! Toggle word wrap Toggle overflow
Run the
connectcommand and enter your username and password when prompted.Data Grid Server on the default port of
11222:[disconnected]> connect
[disconnected]> connectCopy to Clipboard Copied! Toggle word wrap Toggle overflow Data Grid Server with a port offset of
100:[disconnected]> connect 127.0.0.1:11322
[disconnected]> connect 127.0.0.1:11322Copy to Clipboard Copied! Toggle word wrap Toggle overflow
1.4. Shutting Down Data Grid Server Copy linkLink copied to clipboard!
Stop individually running servers or bring down clusters gracefully.
Procedure
- Create a CLI connection to Data Grid.
Shut down Data Grid Server in one of the following ways:
Stop all nodes in a cluster with the
shutdown clustercommand, for example:[//containers/default]> shutdown cluster
[//containers/default]> shutdown clusterCopy to Clipboard Copied! Toggle word wrap Toggle overflow This command saves cluster state to the
datafolder for each node in the cluster. If you use a cache store, theshutdown clustercommand also persists all data in the cache.Stop individual server instances with the
shutdown servercommand and the server hostname, for example:[//containers/default]> shutdown server <my_server01>
[//containers/default]> shutdown server <my_server01>Copy to Clipboard Copied! Toggle word wrap Toggle overflow
The shutdown server command does not wait for rebalancing operations to complete, which can lead to data loss if you specify multiple hostnames at the same time.
Run help shutdown for more details about using the command.
Verification
Data Grid logs the following messages when you shut down servers:
ISPN080002: Data Grid Server stopping ISPN000080: Disconnecting JGroups channel cluster ISPN000390: Persisted state, version=<$version> timestamp=YYYY-MM-DDTHH:MM:SS ISPN080003: Data Grid Server stopped
ISPN080002: Data Grid Server stopping
ISPN000080: Disconnecting JGroups channel cluster
ISPN000390: Persisted state, version=<$version> timestamp=YYYY-MM-DDTHH:MM:SS
ISPN080003: Data Grid Server stopped
1.4.1. Restarting Data Grid Clusters Copy linkLink copied to clipboard!
When you bring Data Grid clusters back online after shutting them down, you should wait for the cluster to be available before adding or removing nodes or modifying cluster state.
If you shutdown clustered nodes with the shutdown server command, you must restart each server in reverse order.
For example, if you shutdown server1 and then shutdown server2, you should first start server2 and then start server1.
If you shutdown a cluster with the shutdown cluster command, clusters become fully operational only after all nodes rejoin.
You can restart nodes in any order but the cluster remains in DEGRADED state until all nodes that were joined before shutdown are running.
Chapter 2. Performing Cache Operations with the Data Grid CLI Copy linkLink copied to clipboard!
The command line interface (CLI) lets you remotely connect to Data Grid servers to access data and perform administrative functions.
2.1. Creating Caches with the Data Grid Command Line Interface (CLI) Copy linkLink copied to clipboard!
Use the Data Grid CLI to add caches from templates or configuration files in XML or JSON format.
Prerequisites
Create a user and start at least one Data Grid server instance.
Procedure
- Create a CLI connection to Data Grid.
Add cache definitions with the
create cachecommand.Add a cache definition from an XML or JSON file with the
--fileoption.[//containers/default]> create cache --file=configuration.xml mycache
[//containers/default]> create cache --file=configuration.xml mycacheCopy to Clipboard Copied! Toggle word wrap Toggle overflow Add a cache definition from a template with the
--templateoption.[//containers/default]> create cache --template=org.infinispan.DIST_SYNC mycache
[//containers/default]> create cache --template=org.infinispan.DIST_SYNC mycacheCopy to Clipboard Copied! Toggle word wrap Toggle overflow TipPress the tab key after the
--template=argument to list available cache templates.
Verify the cache exists with the
lscommand.[//containers/default]> ls caches mycache
[//containers/default]> ls caches mycacheCopy to Clipboard Copied! Toggle word wrap Toggle overflow Retrieve the cache configuration with the
describecommand.[//containers/default]> describe caches/mycache
[//containers/default]> describe caches/mycacheCopy to Clipboard Copied! Toggle word wrap Toggle overflow
2.1.1. XML Configuration Copy linkLink copied to clipboard!
Data Grid configuration in XML format must conform to the schema and include:
-
<infinispan>root element. -
<cache-container>definition.
Example XML Configuration
2.1.2. JSON Configuration Copy linkLink copied to clipboard!
Data Grid configuration in JSON format:
- Requires the cache definition only.
Must follow the structure of an XML configuration.
- XML elements become JSON objects.
- XML attributes become JSON fields.
Example JSON Configuration
2.2. Adding Cache Entries Copy linkLink copied to clipboard!
Create key:value pair entries in the data container.
Prerequisites
Create a Data Grid cache that can store your data.
Procedure
- Create a CLI connection to Data Grid.
Add entries into your cache as follows:
Use the
putcommand from the context of a cache:[//containers/default/caches/mycache]> put hello world
[//containers/default/caches/mycache]> put hello worldCopy to Clipboard Copied! Toggle word wrap Toggle overflow Use the
--cache=with theputcommand:[//containers/default]> put --cache=mycache hello world
[//containers/default]> put --cache=mycache hello worldCopy to Clipboard Copied! Toggle word wrap Toggle overflow
Use the
getcommand to verify entries.[//containers/default/caches/mycache]> get hello world
[//containers/default/caches/mycache]> get hello worldCopy to Clipboard Copied! Toggle word wrap Toggle overflow
2.3. Clearing Caches and Deleting Entries Copy linkLink copied to clipboard!
Remove data from caches with the Data Grid CLI.
Procedure
- Create a CLI connection to Data Grid.
Do one of the following:
Delete all entries with the
clearcachecommand.[//containers/default]> clearcache mycache
[//containers/default]> clearcache mycacheCopy to Clipboard Copied! Toggle word wrap Toggle overflow Remove specific entries with the
removecommand.[//containers/default]> remove --cache=mycache hello
[//containers/default]> remove --cache=mycache helloCopy to Clipboard Copied! Toggle word wrap Toggle overflow
2.4. Deleting Caches Copy linkLink copied to clipboard!
Drop caches to remove them and delete all data they contain.
Procedure
- Create a CLI connection to Data Grid.
Remove caches with the
dropcommand.[//containers/default]> drop cache mycache
[//containers/default]> drop cache mycacheCopy to Clipboard Copied! Toggle word wrap Toggle overflow
Chapter 3. Performing Batch Operations Copy linkLink copied to clipboard!
Process operations in groups, either interactively or using batch files.
Prerequisites
- A running Data Grid cluster.
3.1. Performing Batch Operations with Files Copy linkLink copied to clipboard!
Create files that contain a set of operations and then pass them to the Data Grid CLI.
Procedure
Create a file that contains a set of operations.
For example, create a file named
batchthat creates a cache namedmybatch, adds two entries to the cache, and disconnects from the CLI.Copy to Clipboard Copied! Toggle word wrap Toggle overflow Run the CLI and specify the file as input.
bin/cli.sh -c localhost:11222 -f batch
$ bin/cli.sh -c localhost:11222 -f batchCopy to Clipboard Copied! Toggle word wrap Toggle overflow Create a new Data Grid CLI connection and verify
mybatch.Copy to Clipboard Copied! Toggle word wrap Toggle overflow
CLI batch files support system property expansion. Strings that use the ${property} format are replaced with the value of the property system property.
3.2. Performing Batch Operations Interactively Copy linkLink copied to clipboard!
Use the standard input stream, stdin, to perform batch operations interactively.
Procedure
Start the Data Grid CLI in interactive mode.
bin/cli.sh -c localhost:11222 -f -
$ bin/cli.sh -c localhost:11222 -f -Copy to Clipboard Copied! Toggle word wrap Toggle overflow NoteIf you do not use the
-cflag, you must run theconnectcommand.bin/cli.sh -f -
$ bin/cli.sh -f - connectCopy to Clipboard Copied! Toggle word wrap Toggle overflow Run batch operations, for example:
create cache --template=org.infinispan.DIST_SYNC mybatch put --cache=mybatch hello world put --cache=mybatch hola mundo disconnect quit
create cache --template=org.infinispan.DIST_SYNC mybatch put --cache=mybatch hello world put --cache=mybatch hola mundo disconnect quitCopy to Clipboard Copied! Toggle word wrap Toggle overflow
Use echo to add commands in interactive mode.
The following example shows how to use echo describe to get cluster information:
Chapter 4. Configuring the Data Grid CLI Copy linkLink copied to clipboard!
Define configuration properties for the Data Grid CLI.
4.1. Setting Data Grid CLI Properties and Persistent Storage Copy linkLink copied to clipboard!
Configure Data Grid CLI startup operations and customize the location for persistent storage.
Prerequisites
Create at least one Data Grid user.
Procedure
Optionally set a custom path to the Data Grid CLI storage directory in one of the following ways:
Using the
cli.dirsystem property:bin/cli.sh -Dcli.dir=/path/to/cli/storage ...
$ bin/cli.sh -Dcli.dir=/path/to/cli/storage ...Copy to Clipboard Copied! Toggle word wrap Toggle overflow Using the
ISPN_CLI_DIRenvironment variable:export ISPN_CLI_DIR=/path/to/cli/storage $ bin/cli.sh ...
export ISPN_CLI_DIR=/path/to/cli/storage $ bin/cli.sh ...Copy to Clipboard Copied! Toggle word wrap Toggle overflow
-
Set values for configuration properties with the
config setcommand. Verify configuration properties with the
config getcommand.TipRun
help configto review available configuration properties and get example usage.
4.2. Creating Command Aliases Copy linkLink copied to clipboard!
Create aliases for Data Grid CLI commands to define custom shortcuts.
Procedure
Create aliases with the
alias <alias>=<command>command.For example, set
qas an alias for thequitcommand:[//containers/default]> alias q=quit
[//containers/default]> alias q=quitCopy to Clipboard Copied! Toggle word wrap Toggle overflow Run the
aliascommand to check the defined aliases.[//containers/default]> alias alias q='quit'
[//containers/default]> alias alias q='quit'Copy to Clipboard Copied! Toggle word wrap Toggle overflow Delete aliases with the
unaliascommand, for example:[//containers/default]> unalias q
[//containers/default]> unalias qCopy to Clipboard Copied! Toggle word wrap Toggle overflow
4.3. Trusting Data Grid Server Connections Copy linkLink copied to clipboard!
Secure Data Grid CLI connections to Data Grid Server with SSL/TLS certificates. If you create a key store as an SSL identity for Data Grid Server, the CLI can validate server certificates to verify the identity.
Prerequisites
- Set up an SSL identity for Data Grid Server.
- Create at least one Data Grid user.
Procedure
Specify the location of the server key store, as in the following example:
bin/cli.sh config set truststore /home/user/my-trust-store.jks
$ bin/cli.sh config set truststore /home/user/my-trust-store.jksCopy to Clipboard Copied! Toggle word wrap Toggle overflow Define the key store password, if necessary, as follows:
bin/cli.sh config set truststore-password secret
$ bin/cli.sh config set truststore-password secretCopy to Clipboard Copied! Toggle word wrap Toggle overflow Verify your CLI configuration.
bin/cli.sh config get truststore bin/cli.sh config get truststore-password
$ bin/cli.sh config get truststore truststore=/home/user/my-trust-store.jks $ bin/cli.sh config get truststore-password truststore-password=secretCopy to Clipboard Copied! Toggle word wrap Toggle overflow
4.4. Data Grid CLI Storage Directory Copy linkLink copied to clipboard!
Data Grid CLI stores configuration in the following default directory:
| Operating System | Default Path |
|---|---|
| Linux/Unix |
|
| Microsoft Windows |
|
| Mac OS |
|
This directory contains the following files:
cli.properties- Stores values for CLI configuration properties.
aliases- Stores command aliases.
history- Stores CLI history.
Chapter 5. Working with Counters Copy linkLink copied to clipboard!
Counters provide atomic increment and decrement operations that record the count of objects.
Prerequisites
- Start the Data Grid CLI.
- Connect to a running Data Grid cluster.
5.1. Creating Counters Copy linkLink copied to clipboard!
Create strong and weak counters with the Data Grid CLI.
Procedure
- Create a CLI connection to Data Grid.
Run the
create countercommand with the appropriate arguments.Create
my-weak-counter.[//containers/default]> create counter --concurrency-level=1 --initial-value=5 --storage=PERSISTENT --type=weak my-weak-counter
[//containers/default]> create counter --concurrency-level=1 --initial-value=5 --storage=PERSISTENT --type=weak my-weak-counterCopy to Clipboard Copied! Toggle word wrap Toggle overflow Create
my-strong-counter.[//containers/default]> create counter --initial-value=3 --storage=PERSISTENT --type=strong my-strong-counter
[//containers/default]> create counter --initial-value=3 --storage=PERSISTENT --type=strong my-strong-counterCopy to Clipboard Copied! Toggle word wrap Toggle overflow
List available counters.
[//containers/default]> ls counters my-strong-counter my-weak-counter
[//containers/default]> ls counters my-strong-counter my-weak-counterCopy to Clipboard Copied! Toggle word wrap Toggle overflow Verify counter configurations.
Describe
my-weak-counter.Copy to Clipboard Copied! Toggle word wrap Toggle overflow Describe
my-strong-counter.Copy to Clipboard Copied! Toggle word wrap Toggle overflow
5.2. Adding Deltas to Counters Copy linkLink copied to clipboard!
Increment or decrement counters with arbitrary values.
Procedure
Select a counter.
[//containers/default]> counter my-weak-counter
[//containers/default]> counter my-weak-counterCopy to Clipboard Copied! Toggle word wrap Toggle overflow List the current count.
[//containers/default/counters/my-weak-counter]> ls 5
[//containers/default/counters/my-weak-counter]> ls 5Copy to Clipboard Copied! Toggle word wrap Toggle overflow Increment the counter value by
2.[//containers/default/counters/my-weak-counter]> add --delta=2
[//containers/default/counters/my-weak-counter]> add --delta=2Copy to Clipboard Copied! Toggle word wrap Toggle overflow Decrement the counter value by
-4.[//containers/default/counters/my-weak-counter]> add --delta=-4
[//containers/default/counters/my-weak-counter]> add --delta=-4Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Strong counters return values after the operation is applied. Use --quiet=true to hide the return value.
For example, my-strong-counter]> add --delta=3 --quiet=true.
Weak counters return empty responses.
Chapter 6. Querying Caches with Protobuf Metadata Copy linkLink copied to clipboard!
Data Grid supports using Protocol Buffers (Protobuf) to structure data in the cache so that you can query it.
Prerequisites
- Start the Data Grid CLI.
- Connect to a running Data Grid cluster.
6.1. Configuring Media Types Copy linkLink copied to clipboard!
Encode cache entries with different media types to store data in a format that best suits your requirements.
For example, the following procedure shows you how to configure the application/x-protostream media type.
Procedure
Create a Data Grid configuration file that adds a distributed cache named
qcacheand configures the media type, for example:Copy to Clipboard Copied! Toggle word wrap Toggle overflow Create
qcachefrompcache.xmlwith the--file=option.[//containers/default]> create cache --file=pcache.xml pcache
[//containers/default]> create cache --file=pcache.xml pcacheCopy to Clipboard Copied! Toggle word wrap Toggle overflow Verify
pcache.Copy to Clipboard Copied! Toggle word wrap Toggle overflow Add an entry to
pcacheand check the encoding.Copy to Clipboard Copied! Toggle word wrap Toggle overflow
6.2. Registering Protobuf Schemas Copy linkLink copied to clipboard!
Protobuf schemas contain data structures known as messages in .proto definition files.
Procedure
Create a schema file named
person.protowith the following messages:Copy to Clipboard Copied! Toggle word wrap Toggle overflow Register
person.proto.[//containers/default]> schema --upload=person.proto person.proto
[//containers/default]> schema --upload=person.proto person.protoCopy to Clipboard Copied! Toggle word wrap Toggle overflow Verify
person.proto.[//containers/default]> cd caches/___protobuf_metadata [//containers/default/caches/___protobuf_metadata]> ls person.proto [//containers/default/caches/___protobuf_metadata]> get person.proto
[//containers/default]> cd caches/___protobuf_metadata [//containers/default/caches/___protobuf_metadata]> ls person.proto [//containers/default/caches/___protobuf_metadata]> get person.protoCopy to Clipboard Copied! Toggle word wrap Toggle overflow
6.3. Querying Caches with Protobuf Schemas Copy linkLink copied to clipboard!
Data Grid automatically converts JSON to Protobuf so that you can read and write cache entries in JSON format and use Protobuf schemas to query them.
For example, consider the following JSON documents:
lukecage.json
jessicajones.json
matthewmurdock.json
Each of the preceding JSON documents contains:
-
A
_typefield that identifies the Protobuf message to which the JSON document corresponds. -
Several fields that correspond to datatypes in the
person.protoschema.
Procedure
Navigate to the
pcachecache.[//containers/default/caches]> cd pcache
[//containers/default/caches]> cd pcacheCopy to Clipboard Copied! Toggle word wrap Toggle overflow Add each JSON document as an entry to the cache, for example:
[//containers/default/caches/pcache]> put --encoding=application/json --file=jessicajones.json jessicajones [//containers/default/caches/pcache]> put --encoding=application/json --file=matthewmurdock.json matthewmurdock [//containers/default/caches/pcache]> put --encoding=application/json --file=lukecage.json lukecage
[//containers/default/caches/pcache]> put --encoding=application/json --file=jessicajones.json jessicajones [//containers/default/caches/pcache]> put --encoding=application/json --file=matthewmurdock.json matthewmurdock [//containers/default/caches/pcache]> put --encoding=application/json --file=lukecage.json lukecageCopy to Clipboard Copied! Toggle word wrap Toggle overflow Verify that the entries exist.
[//containers/default/caches/pcache]> ls lukecage matthewmurdock jessicajones
[//containers/default/caches/pcache]> ls lukecage matthewmurdock jessicajonesCopy to Clipboard Copied! Toggle word wrap Toggle overflow Query the cache to return entries from the Protobuf
Personentity where the gender datatype isMALE.Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Chapter 7. Performing Cross-Site Replication Operations Copy linkLink copied to clipboard!
Data Grid clusters running in different locations can discover and communicate with each other to backup data.
Prerequisites
- Start the Data Grid CLI.
- Connect to a running Data Grid cluster.
7.1. Bringing Backup Locations Offline and Online Copy linkLink copied to clipboard!
Take backup locations offline manually and bring them back online.
Procedure
- Create a CLI connection to Data Grid.
Check if backup locations are online or offline with the
site statuscommand://containers/default]> site status --cache=cacheName --site=NYC
//containers/default]> site status --cache=cacheName --site=NYCCopy to Clipboard Copied! Toggle word wrap Toggle overflow Note--siteis an optional argument. If not set, the CLI returns all backup locations.Manage backup locations as follows:
Bring backup locations online with the
bring-onlinecommand://containers/default]> site bring-online --cache=customers --site=NYC
//containers/default]> site bring-online --cache=customers --site=NYCCopy to Clipboard Copied! Toggle word wrap Toggle overflow Take backup locations offline with the
take-offlinecommand://containers/default]> site take-offline --cache=customers --site=NYC
//containers/default]> site take-offline --cache=customers --site=NYCCopy to Clipboard Copied! Toggle word wrap Toggle overflow
For more information and examples, run the help site command.
7.2. Pushing State to Backup Locations Copy linkLink copied to clipboard!
Transfer cache state to remote backup locations.
Procedure
- Create a CLI connection to Data Grid.
Use the
sitecommand to push state transfer, as in the following example://containers/default]> site push-site-state --cache=cacheName --site=NYC
//containers/default]> site push-site-state --cache=cacheName --site=NYCCopy to Clipboard Copied! Toggle word wrap Toggle overflow
For more information and examples, run the help site command.
Chapter 8. Command Reference Copy linkLink copied to clipboard!
Review manual pages for Data Grid CLI commands.
Use help command to access manual pages directly from your CLI session.
For example, to view the manual page for the get command do the following:
help get
$ help get
8.1. ADD(1) Copy linkLink copied to clipboard!
8.1.1. NAME Copy linkLink copied to clipboard!
add - increments and decrements counters with arbitrary values.
8.1.2. SYNOPSIS Copy linkLink copied to clipboard!
add ['OPTIONS'] ['COUNTER_NAME']
8.1.3. OPTIONS Copy linkLink copied to clipboard!
- --delta='nnn'
-
Sets a delta to increment or decrement the counter value. Defaults to
1. - -q, --quiet='[true|false]'
-
Hides return values for strong counters. The default is
false.
8.1.4. EXAMPLES Copy linkLink copied to clipboard!
add --delta=10 cnt_a
Increments the value of cnt_a by 10.
add --delta=-5 cnt_a
Decrements the value of cnt_a by 5.
8.1.5. SEE ALSO Copy linkLink copied to clipboard!
cas(1), reset(1)
8.2. ALIAS(1) Copy linkLink copied to clipboard!
8.2.1. NAME Copy linkLink copied to clipboard!
alias - creates or displays aliases.
8.2.2. SYNOPSIS Copy linkLink copied to clipboard!
alias ['ALIAS-NAME'='COMMAND']
8.2.3. EXAMPLES Copy linkLink copied to clipboard!
alias q=quit
Creates q as an alias for the quit command.
alias
Lists all defined aliases.
8.2.4. SEE ALSO Copy linkLink copied to clipboard!
config(1), unalias(1)
8.3. CACHE(1) Copy linkLink copied to clipboard!
8.3.1. NAME Copy linkLink copied to clipboard!
cache - selects the default cache for subsequent commands.
8.3.2. SYNOPSIS Copy linkLink copied to clipboard!
cache ['CACHE_NAME']
8.3.3. EXAMPLE Copy linkLink copied to clipboard!
cache mycache
Selects mycache and is the same as navigating the resource tree using cd caches/mycache.
8.3.4. SEE ALSO Copy linkLink copied to clipboard!
cd(1), clear(1), container(1), get(1), put(1), remove(1)
8.4. CAS(1) Copy linkLink copied to clipboard!
8.4.1. NAME Copy linkLink copied to clipboard!
cas - performs 'compare-and-swap' operations on strong counters.
8.4.2. SYNOPSIS Copy linkLink copied to clipboard!
cas ['OPTIONS'] ['COUNTER_NAME']
8.4.3. OPTIONS Copy linkLink copied to clipboard!
- --expect='nnn'
- Specifies the expected value of the counter.
- --value='nnn'
- Sets a new value for the counter.
- -q, --quiet='[true|false]'
- Hides return values. The default is false.
8.4.4. EXAMPLE Copy linkLink copied to clipboard!
cas --expect=10 --value=20 cnt_a
Sets the value of cnt_a to 20 only if the current value is 10
8.4.5. SEE ALSO Copy linkLink copied to clipboard!
add(1), cas(1), reset(1)
8.5. CD(1) Copy linkLink copied to clipboard!
8.5.1. NAME Copy linkLink copied to clipboard!
cd - navigates the server resource tree.
8.5.2. DESCRIPTION Copy linkLink copied to clipboard!
PATH can be absolute or relative to the current resource. ../ specifies parent resources.
8.5.3. SYNOPSIS Copy linkLink copied to clipboard!
cd ['PATH']
8.5.4. EXAMPLE Copy linkLink copied to clipboard!
cd caches
Changes to the caches path in the resource tree.
8.5.5. SEE ALSO Copy linkLink copied to clipboard!
cache(1), ls(1), container(1)
8.6. CLEARCACHE(1) Copy linkLink copied to clipboard!
8.6.1. NAME Copy linkLink copied to clipboard!
clearcache - removes all entries from a cache.
8.6.2. SYNOPSIS Copy linkLink copied to clipboard!
clearcache ['CACHE_NAME']
8.6.3. EXAMPLES Copy linkLink copied to clipboard!
clearcache mycache
Removes all entries from mycache.
8.6.4. SEE ALSO Copy linkLink copied to clipboard!
cache(1), drop(1), remove(1)
8.7. CONFIG(1) Copy linkLink copied to clipboard!
8.7.1. NAME Copy linkLink copied to clipboard!
config - manages CLI configuration properties.
8.7.2. SYNOPSIS Copy linkLink copied to clipboard!
config
config set 'name' 'value'
config get 'name'
8.7.3. DESCRIPTION Copy linkLink copied to clipboard!
Manage (list, set, get) CLI configuration properties.
8.7.4. COMMAND SYNOPSIS Copy linkLink copied to clipboard!
- config
- Lists all configuration properties that are set.
- config set 'name' ['value']
- Sets the value of a specific property. If you do not specify a value, the property is not set.
- config get 'name'
- Retrieves the value of a specific property.
8.7.5. COMMON OPTIONS Copy linkLink copied to clipboard!
These options apply to all commands:
- -h, --help
- Displays a help page for the command or sub-command.
8.7.6. PROPERTIES Copy linkLink copied to clipboard!
- autoconnect-url
- Specifies the URL to which the CLI automatically connects on startup.
- autoexec
- Specifies the path of a CLI batch file to execute on startup.
- trustall
-
Specifies whether to trust all server certificates. Values are
false(default) andtrue. - truststore
- Defines the path to a keystore that contains a certificate chain that verifies server identity.
- truststore-password
- Specifies a password to access the keystore.
8.7.7. EXAMPLES Copy linkLink copied to clipboard!
config set autoconnect-url http://192.0.2.0:11222
Connects to a server at a custom IP address when you start the CLI.
config get autoconnect-url
Returns the value for the autoconnect-url configuration property.
config set autoexec /path/to/mybatchfile
Runs a batch file named "mybatchfile" when you start the CLI.
config set trustall true
Trusts all server certificates.
config set truststore /home/user/my-trust-store.jks
Specifies the path of a keystore named "my-trust-store.jks".
config set truststore-password secret
Sets the keystore password, if required.
8.7.8. SEE ALSO Copy linkLink copied to clipboard!
alias(1), unalias(1)
8.8. CONNECT(1) Copy linkLink copied to clipboard!
8.8.1. NAME Copy linkLink copied to clipboard!
connect - connects to running Data Grid servers.
8.8.2. DESCRIPTION Copy linkLink copied to clipboard!
Defaults to http://localhost:11222 and prompts for credentials if authentication is required.
8.8.3. SYNOPSIS Copy linkLink copied to clipboard!
connect ['OPTIONS'] ['SERVER_LOCATION']
8.8.4. OPTIONS Copy linkLink copied to clipboard!
- -u, --username='USERNAME'
- Specifies a username to authenticate with Data Grid servers.
- -p, --password='PASSWORD'
- Specifies passwords.
8.8.5. EXAMPLE Copy linkLink copied to clipboard!
connect 127.0.0.1:11322 -u test -p changeme
Connects to a locally running server using a port offset of 100 and example credentials.
8.8.6. SEE ALSO Copy linkLink copied to clipboard!
disconnect(1)
8.9. CONTAINER(1) Copy linkLink copied to clipboard!
8.9.1. NAME Copy linkLink copied to clipboard!
container - selects the container for running subsequent commands.
8.9.2. SYNOPSIS Copy linkLink copied to clipboard!
container ['CONTAINER_NAME']
8.9.3. EXAMPLE Copy linkLink copied to clipboard!
container default
Selects the default container and is the same as navigating the resource tree using cd containers/default.
8.9.4. SEE ALSO Copy linkLink copied to clipboard!
cd(1), clear(1), container(1), get(1), put(1), remove(1)
8.10. COUNTER(1) Copy linkLink copied to clipboard!
8.10.1. NAME Copy linkLink copied to clipboard!
counter - selects the default counter for subsequent commands.
8.10.2. SYNOPSIS Copy linkLink copied to clipboard!
counter ['COUNTER_NAME']
8.10.3. EXAMPLE Copy linkLink copied to clipboard!
counter cnt_a
Selects cnt_a and is the same as navigating the resource tree using cd counters/cnt_a.
8.10.4. SEE ALSO Copy linkLink copied to clipboard!
add(1), cas(1)
8.11. CREATE(1) Copy linkLink copied to clipboard!
8.11.1. NAME Copy linkLink copied to clipboard!
create - creates caches and counters on Data Grid servers.
8.11.2. SYNOPSIS Copy linkLink copied to clipboard!
create cache ['OPTIONS'] CACHE_NAME
create counter ['OPTIONS'] COUNTER_NAME
8.11.3. CREATE CACHE OPTIONS Copy linkLink copied to clipboard!
- -f, --file='FILE'
- Specifies a configuration file in JSON or XML format.
- -t, --template='TEMPLATE'
- Specifies a configuration template. Use tab autocompletion to see available templates.
- -v, --volatile='[true|false]'
- Specifies whether the cache is persistent or volatile. The default is false.
8.11.4. CREATE COUNTER OPTIONS Copy linkLink copied to clipboard!
- -t, --type='[weak|strong]'
- Specifies if the counter is weak or strong.
- -s, --storage='[PERSISTENT|VOLATILE]'
- Specifies whether the counter is persistent or volatile.
- -c, --concurrency-level='nnn'
- Sets the concurrency level of the counter.
- -i, --initial-value='nnn'
- Sets the initial value of the counter.
- -l, --lower-bound='nnn'
- Sets the lower bound of a strong counter.
- -u, --upper-bound='nnn'
- Sets the upper bound of a strong counter.
8.11.5. EXAMPLES Copy linkLink copied to clipboard!
create cache --template=org.infinispan.DIST_SYNC mycache
Creates a cache named mycache from the DIST_SYNC template.
create counter --initial-value=3 --storage=PERSISTENT --type=strong cnt_a
Creates a strong counter named cnt_a.
8.11.6. SEE ALSO Copy linkLink copied to clipboard!
drop(1)
8.12. DESCRIBE(1) Copy linkLink copied to clipboard!
8.12.1. NAME Copy linkLink copied to clipboard!
describe - displays information about resources.
8.12.2. SYNOPSIS Copy linkLink copied to clipboard!
describe ['PATH']
8.12.3. EXAMPLES Copy linkLink copied to clipboard!
describe //containers/default
Displays information about the default container.
describe //containers/default/caches/mycache
Displays information about the mycache cache.
describe //containers/default/caches/mycache/k1
Displays information about the k1 key.
describe //containers/default/counters/cnt1
Displays information about the cnt1 counter.
8.12.4. SEE ALSO Copy linkLink copied to clipboard!
cd(1), ls(1)
8.13. DISCONNECT(1) Copy linkLink copied to clipboard!
8.13.1. NAME Copy linkLink copied to clipboard!
disconnect - ends CLI sessions with Data Grid servers.
8.13.2. SYNOPSIS Copy linkLink copied to clipboard!
disconnect
8.13.3. EXAMPLE Copy linkLink copied to clipboard!
disconnect
Ends the current CLI session.
8.13.4. SEE ALSO Copy linkLink copied to clipboard!
connect(1)
8.14. DROP(1) Copy linkLink copied to clipboard!
8.14.1. NAME Copy linkLink copied to clipboard!
drop - deletes caches and counters.
8.14.2. SYNOPSIS Copy linkLink copied to clipboard!
drop cache CACHE_NAME
drop counter COUNTER_NAME
8.14.3. EXAMPLES Copy linkLink copied to clipboard!
drop cache mycache
Deletes the mycache cache.
drop counter cnt_a
Deletes the cnt_a counter.
8.14.4. SEE ALSO Copy linkLink copied to clipboard!
create(1), clearcache(1)
8.15. ENCODING(1) Copy linkLink copied to clipboard!
8.15.1. NAME Copy linkLink copied to clipboard!
encoding - displays and sets the encoding for cache entries.
8.15.2. DESCRIPTION Copy linkLink copied to clipboard!
Sets a default encoding for put and get operations on a cache. If no argument is specified, the encoding command displays the current encoding.
Valid encodings use standard MIME type (IANA media types) naming conventions, such as the following:
-
text/plain -
application/json -
application/xml -
application/octet-stream
8.15.3. SYNOPSIS Copy linkLink copied to clipboard!
encoding ['ENCODING']
8.15.4. EXAMPLE Copy linkLink copied to clipboard!
encoding application/json
Configures the currently selected cache to encode entries as application/json.
8.15.5. SEE ALSO Copy linkLink copied to clipboard!
get(1), put(1)
8.16. GET(1) Copy linkLink copied to clipboard!
8.16.1. NAME Copy linkLink copied to clipboard!
get - retrieves entries from a cache.
8.16.2. SYNOPSIS Copy linkLink copied to clipboard!
get ['OPTIONS'] KEY
8.16.3. OPTIONS Copy linkLink copied to clipboard!
- -c, --cache='NAME'
- Specifies the cache from which to retrieve entries. Defaults to the currently selected cache.
8.16.4. EXAMPLE Copy linkLink copied to clipboard!
get hello -c mycache
Retrieves the value of the key named hello from mycache.
8.16.5. SEE ALSO Copy linkLink copied to clipboard!
query(1), put(1)
8.17. HELP(1) Copy linkLink copied to clipboard!
8.17.1. NAME Copy linkLink copied to clipboard!
help - prints manual pages for commands.
8.17.2. SYNOPSIS Copy linkLink copied to clipboard!
help ['COMMAND']
8.17.3. EXAMPLE Copy linkLink copied to clipboard!
help get
Prints the manual page for the get command.
8.17.4. SEE ALSO Copy linkLink copied to clipboard!
version(1)
8.18. LOGGING(1) Copy linkLink copied to clipboard!
8.18.1. NAME Copy linkLink copied to clipboard!
logging - inspects and manipulates the Data Grid server runtime logging configuration.
8.18.2. SYNOPSIS Copy linkLink copied to clipboard!
logging list-loggers
logging list-appenders
logging set ['OPTIONS'] [LOGGER_NAME]
logging remove LOGGER_NAME
8.18.3. LOGGING SET OPTIONS Copy linkLink copied to clipboard!
- -l, --level='OFF|TRACE|DEBUG|INFO|WARN|ERROR|ALL'
- Specifies the logging level for the specific logger.
- -a, --appender='APPENDER'
- Specifies an appenders to set on the specific logger. The option can be repeated for multiple appenders.
calling logging set without a logger name will modify the root logger.
8.18.4. EXAMPLES Copy linkLink copied to clipboard!
logging list-loggers
Lists all available loggers
logging set --level=DEBUG --appenders=FILE org.infinispan
Sets the log level for the org.infinispan logger to DEBUG and configures it to use the FILE appender.
8.19. LS(1) Copy linkLink copied to clipboard!
8.19.1. NAME Copy linkLink copied to clipboard!
ls - lists resources for the current path or a given path.
8.19.2. SYNOPSIS Copy linkLink copied to clipboard!
ls ['PATH']
8.19.3. EXAMPLES Copy linkLink copied to clipboard!
ls caches
Lists the available caches.
ls ../
Lists parent resources.
8.19.4. SEE ALSO Copy linkLink copied to clipboard!
cd(1)
8.20. MIGRATE(1) Copy linkLink copied to clipboard!
8.20.1. NAME Copy linkLink copied to clipboard!
migrate - migrates data from one version of Data Grid to another.
8.20.2. SYNOPSIS Copy linkLink copied to clipboard!
migrate cluster synchronize
migrate cluster disconnect
8.20.3. DESCRIPTION Copy linkLink copied to clipboard!
Use the migrate command to migrate data from one version of Data Grid to another.
8.20.4. COMMAND SYNOPSIS Copy linkLink copied to clipboard!
Migrate clusters
- migrate cluster synchronize
- Synchronize data between the source cluster and the target cluster.
- migrate cluster disconnect
- Disconnects the target cluster from the source cluster.
8.20.5. COMMON OPTIONS Copy linkLink copied to clipboard!
These options apply to all commands:
- -h, --help
- Displays a help page for the command or sub-command.
8.20.6. CLUSTER SYNCHRONIZE OPTIONS Copy linkLink copied to clipboard!
- -c, --cache='name'
- The name of the cache to synchronize.
- -b, --read-batch='num'
- The amount of entries to process in a batch. Defaults to 10000.
- -t, --threads='num'
- The number of threads to use. Defaults to the number of cores on the server.
8.20.7. CLUSTER DISCONNECT OPTIONS Copy linkLink copied to clipboard!
- -c, --cache='name'
- The name of the cache to disconnect from the source.
8.21. PATCH(1) Copy linkLink copied to clipboard!
8.21.1. NAME Copy linkLink copied to clipboard!
patch - manages server patches.
8.21.2. DESCRIPTION Copy linkLink copied to clipboard!
List, describe, install, rollback, and create server patches.
Patches are zip archive files that contain artifacts to upgrade servers and resolve issues or add new features. Patches can apply target versions to multiple server installations with different versions.
8.21.3. SYNOPSIS Copy linkLink copied to clipboard!
patch ls
patch install 'patch-file'
patch describe 'patch-file'
patch rollback
patch create 'patch-file' 'target-server' 'source-server-1' ['source-server-2'…]
8.21.4. PATCH LIST OPTIONS Copy linkLink copied to clipboard!
- --server='path/to/server'
- Sets the path to a target server outside the current server home directory.
- -v, --verbose
- Shows the content of each installed patch, including information about individual files.
8.21.5. PATCH INSTALL OPTIONS Copy linkLink copied to clipboard!
- --dry-run
- Shows the operations that the patch peforms without applying any changes.
- --server='path/to/server'
- Sets the path to a target server outside the current server home directory.
8.21.6. PATCH DESCRIBE OPTIONS Copy linkLink copied to clipboard!
- -v, --verbose
- Shows the content of the patch, including information about individual files
8.21.7. PATCH ROLLBACK OPTIONS Copy linkLink copied to clipboard!
- --dry-run
- Shows the operations that the patch peforms without applying any changes.
- --server='path/to/server'
- Sets the path to a target server outside the current server home directory.
8.21.8. PATCH CREATE OPTIONS Copy linkLink copied to clipboard!
- -q, --qualifier='name'
- Specifies a descriptive qualifier string for the patch; for example, 'one-off for issue nnnn'.
8.21.9. EXAMPLES Copy linkLink copied to clipboard!
patch ls
Lists the patches currently installed on a server in order of installation.
patch install mypatch.zip
Installs "mypatch.zip" on a server in the current directory.
patch install mypatch.zip --server=/path/to/server/home
Installs "mypatch.zip" on a server in a different directory.
patch describe mypatch.zip
Displays the target version and list of source versions for "mypatch.zip".
patch create mypatch.zip 'target-server' 'source-server-1' ['source-server-2'…]
Creates a patch file named "mypatch.zip" that uses the version of the target server and applies to the source server versions.
patch rollback
Rolls back the last patch that was applied to a server and restores the previous version.
8.22. PUT(1) Copy linkLink copied to clipboard!
8.22.1. NAME Copy linkLink copied to clipboard!
put - adds or updates cache entries.
8.22.2. DESCRIPTION Copy linkLink copied to clipboard!
Creates entries for new keys. Replaces values for existing keys.
8.22.3. SYNOPSIS Copy linkLink copied to clipboard!
put ['OPTIONS'] KEY [VALUE]
8.22.4. OPTIONS Copy linkLink copied to clipboard!
- -c, --cache='NAME'
- Specifies the name of the cache. Defaults to the currently selected cache.
- -e, --encoding='ENCODING'
- Sets the media type for the value.
- -f, --file='FILE'
- Specifies a file that contains the value for the entry.
- -l, --ttl='TTL'
-
Sets the number of seconds before the entry is automatically deleted (time-to-live). Defaults to the value for
lifespanin the cache configuration if0or not specified. If you set a negative value, the entry is never deleted. - -i, --max-idle='MAXIDLE'
-
Sets the number of seconds that the entry can be idle. If a read or write operation does not occur for an entry after the maximum idle time elapses, the entry is automatically deleted. Defaults to the value for
maxIdlein the cache configuration if0or not specified. If you set a negative value, the entry is never deleted. - -a, --if-absent=[true|false]
- Puts an entry only if it does not exist.
8.22.5. EXAMPLES Copy linkLink copied to clipboard!
put -c mycache hello world
Adds the hello key with a value of world to the mycache cache.
put -c mycache -f myfile -i 500 hola
Adds the hola key with the value from the contents of myfile. Also sets a maximum idle of 500 seconds.
8.22.6. SEE ALSO Copy linkLink copied to clipboard!
get(1), remove(1)
8.23. QUERY(1) Copy linkLink copied to clipboard!
8.23.1. NAME Copy linkLink copied to clipboard!
query - retrieves entries that match Ickle query strings.
8.23.2. SYNOPSIS Copy linkLink copied to clipboard!
query ['OPTIONS'] QUERY_STRING
8.23.3. OPTIONS Copy linkLink copied to clipboard!
- -c, --cache='NAME'
- Specifies the cache to query. Defaults to the currently selected cache.
- --max-results='MAX_RESULTS'
-
Sets the number of results to return. The default is
10. - -o, --offset='OFFSET'
-
Specifies the index of the first result to return. The default is
0. - --query-mode='QUERY_MODE'
-
Specifies how the server executes the query. Values are
FETCHand BROADCAST. The default isFETCH.
8.23.4. EXAMPLES Copy linkLink copied to clipboard!
query "from org.infinispan.rest.search.entity.Person p where p.gender = 'MALE'"
Queries the currently selected cache to return entries from a Protobuf Person entity where the gender datatype is MALE.
8.23.5. SEE ALSO Copy linkLink copied to clipboard!
schema(1)
8.24. QUIT(1) Copy linkLink copied to clipboard!
8.24.1. NAME Copy linkLink copied to clipboard!
quit - exits the command line interface.
8.24.2. SYNOPSIS Copy linkLink copied to clipboard!
quit
8.24.3. EXAMPLE Copy linkLink copied to clipboard!
quit
Exits the CLI.
8.24.4. SEE ALSO Copy linkLink copied to clipboard!
disconnect(1), shutdown(1)
8.25. REMOVE(1) Copy linkLink copied to clipboard!
8.25.1. NAME Copy linkLink copied to clipboard!
remove - deletes entries from a cache.
8.25.2. SYNOPSIS Copy linkLink copied to clipboard!
remove KEY ['OPTIONS']
8.25.3. OPTIONS Copy linkLink copied to clipboard!
- --cache='NAME'
- Specifies the cache from which to remove entries. Defaults to the currently selected cache.
8.25.4. EXAMPLE Copy linkLink copied to clipboard!
remove --cache=mycache hola
Deletes the hola entry from the mycache cache.
8.25.5. SEE ALSO Copy linkLink copied to clipboard!
cache(1), drop(1), clearcache(1)
8.26. RESET(1) Copy linkLink copied to clipboard!
8.26.1. NAME Copy linkLink copied to clipboard!
reset - restores the initial values of counters.
8.26.2. SYNOPSIS Copy linkLink copied to clipboard!
reset ['COUNTER_NAME']
8.26.3. EXAMPLE Copy linkLink copied to clipboard!
reset cnt_a
Resets the cnt_a counter.
8.26.4. SEE ALSO Copy linkLink copied to clipboard!
add(1), cas(1), drop(1)
8.27. SCHEMA(1) Copy linkLink copied to clipboard!
8.27.1. NAME Copy linkLink copied to clipboard!
schema - uploads and registers protobuf schemas.
8.27.2. SYNOPSIS Copy linkLink copied to clipboard!
schema ['OPTIONS'] SCHEMA_NAME
8.27.3. OPTIONS Copy linkLink copied to clipboard!
- -u, --upload='FILE'
- Uploads a file as a protobuf schema with the given name.
8.27.4. EXAMPLE Copy linkLink copied to clipboard!
schema --upload=person.proto person.proto
Registers a person.proto Protobuf schema.
8.27.5. SEE ALSO Copy linkLink copied to clipboard!
query(1)
8.28. SHUTDOWN(1) Copy linkLink copied to clipboard!
8.28.1. NAME Copy linkLink copied to clipboard!
shutdown - stops running servers or brings clusters down gracefully.
8.28.2. SYNOPSIS Copy linkLink copied to clipboard!
shutdown server ['SERVERS']
shutdown cluster
8.28.3. EXAMPLES Copy linkLink copied to clipboard!
shutdown server
Stops the server to which the CLI is connected.
shutdown server my_server01
Stops the server with hostname my_server01.
shutdown cluster
Stores cluster state, persists entries if you use a cache store, and stops all nodes.
8.28.4. SEE ALSO Copy linkLink copied to clipboard!
connect(1), disconnect(1), quit(1)
8.29. SITE(1) Copy linkLink copied to clipboard!
8.29.1. NAME Copy linkLink copied to clipboard!
site - manages backup locations and performs cross-site replication operations.
8.29.2. SYNOPSIS Copy linkLink copied to clipboard!
site status ['OPTIONS']
site bring-online ['OPTIONS']
site take-offline ['OPTIONS']
site push-site-state ['OPTIONS']
site cancel-push-state ['OPTIONS']
site cancel-receive-state ['OPTIONS']
site push-site-status ['OPTIONS']
8.29.3. OPTIONS Copy linkLink copied to clipboard!
- --cache='CACHE_NAME'
- Specifies a cache.
- --site='SITE_NAME'
- Specifies a backup location.
8.29.4. EXAMPLES Copy linkLink copied to clipboard!
site status --cache=mycache
Returns the status of all backup locations for mycache.
site status --cache=mycache --site=NYC
Returns the status of NYC for mycache.
site bring-online --cache=mycache --site=NYC
Brings the site NYC online for mycache.
site take-offline --cache=mycache --site=NYC
Takes the site NYC offline for mycache.
site push-site-state --cache=mycache --site=NYC
Backs up caches to remote backup locations.
site push-site-status --cache=mycache
Displays the status of the operation to backup mycache.
site cancel-push-state --cache=mycache --site=NYC
Cancels the operation to backup mycache to NYC.
site cancel-receive-state --cache=mycache --site=NYC
Cancels the operation to receive state from NYC.
site clear-push-state-status --cache=myCache
Clears the status of the push state operation for mycache.
8.30. STATS(1) Copy linkLink copied to clipboard!
8.30.1. NAME Copy linkLink copied to clipboard!
stats - displays statistics about resources.
8.30.2. SYNOPSIS Copy linkLink copied to clipboard!
stats ['PATH']
8.30.3. EXAMPLES Copy linkLink copied to clipboard!
stats //containers/default
Displays statistics about the default container.
stats //containers/default/caches/mycache
Displays statistics about the mycache cache.
8.30.4. SEE ALSO Copy linkLink copied to clipboard!
cd(1), ls(1), describe(1)
8.31. TASK(1) Copy linkLink copied to clipboard!
8.31.1. NAME Copy linkLink copied to clipboard!
task - executes and uploads server-side tasks and scripts
8.31.2. SYNOPSIS Copy linkLink copied to clipboard!
task upload --file='script' 'TASK_NAME'
task exec ['TASK_NAME']
8.31.3. EXAMPLES Copy linkLink copied to clipboard!
task upload --file=hello.js hello
Uploads a script from a hello.js file and names it hello.
task exec @@cache@names
Runs a task that returns available cache names.
task exec hello -Pgreetee=world
Runs a script named hello and specifies the greetee parameter with a value of world.
8.31.4. OPTIONS Copy linkLink copied to clipboard!
- -P, --parameters='PARAMETERS'
- Passes parameter values to tasks and scripts.
- -f, --file='FILE'
- Uploads script files with the given names.
8.31.5. SEE ALSO Copy linkLink copied to clipboard!
ls(1)
8.32. UNALIAS(1) Copy linkLink copied to clipboard!
8.32.1. NAME Copy linkLink copied to clipboard!
unalias - deletes aliases.
8.32.2. SYNOPSIS Copy linkLink copied to clipboard!
unalias 'ALIAS-NAME'
8.32.3. EXAMPLES Copy linkLink copied to clipboard!
unalias q
Deletes the q alias.
8.32.4. SEE ALSO Copy linkLink copied to clipboard!
config(1), alias(1)
8.33. USER(1) Copy linkLink copied to clipboard!
8.33.1. NAME Copy linkLink copied to clipboard!
user - manages Data Grid users in property security realms.
8.33.2. SYNOPSIS Copy linkLink copied to clipboard!
user ls
user create 'username'
user describe 'username'
user remove 'username'
user password 'username'
user groups 'username'
user encrypt-all
8.33.3. DESCRIPTION Copy linkLink copied to clipboard!
Manage (list, create, describe, remove, modify) users stored in a property security realm. Note: You can use this command only with property realms.
8.33.4. COMMAND SYNOPSIS Copy linkLink copied to clipboard!
- user ls
- Lists the users or groups which are present in the property file.
- user create 'username'
- Creates a user after prompting for a password.
- user describe 'username'
- Describes a user, including its username, realm and any groups it belongs to.
- user remove 'username'
- Removes the specified user from the property file.
- user password 'username'
- Changes the password for a user.
- user groups 'username'
- Sets the groups to which a user belongs.
- user encrypt-all
- Encrypt all passwords in a plain-text user property file.
8.33.5. COMMON OPTIONS Copy linkLink copied to clipboard!
These options apply to all commands:
- -h, --help
- Displays a help page for the command or sub-command.
- -s, --server-root='path-to-server-root'
-
The path to the server root. Defaults to
server. - -f, --users-file='users.properties'
-
The name of the property file which contains the user passwords. Defaults to
users.properties. - -w, --groups-file='groups.properties'
-
The name of the property file which contains the user to groups mapping. Defaults to
groups.properties.
8.33.6. USER CREATE/MODIFY OPTIONS Copy linkLink copied to clipboard!
- -a, --algorithms
- Specifies the algorithms used to hash the password.
- -g, --groups='group1,group2,…'
- Specifies the groups to which the user belongs.
- -p, --password='password'
- Specifies the user’s password.
- -r, --realm='realm'
- Specifies the realm name.
- --plain-text
- Whether passwords should be stored in plain-text (not recommended).
8.33.7. USER LS OPTIONS Copy linkLink copied to clipboard!
- --groups
- Shows a list of groups instead of the users.
8.33.8. USER ENCRYPT-ALL OPTIONS Copy linkLink copied to clipboard!
- -a, --algorithms
- Specifies the algorithms used to hash the password.
8.34. VERSION(1) Copy linkLink copied to clipboard!
8.34.1. NAME Copy linkLink copied to clipboard!
version - displays the server version and CLI version.
8.34.2. SYNOPSIS Copy linkLink copied to clipboard!
version
8.34.3. EXAMPLE Copy linkLink copied to clipboard!
version
Returns the version for the server and the CLI.
8.34.4. SEE ALSO Copy linkLink copied to clipboard!
help(1)