Start the Administration CLI

You have now bootstrapped all the Storage Nodes and started the Storage Node agents. You must issue administrative commands next. The runadmin utility provides a command line interface (CLI) where you can enter commands to administer your data store. The first Storage Node where you invoke the runadmin utility will contain the master copy of the administration database.

Note: You cannot change the Storage Node you use to initially configure the data store. Therefore, carefully select the Storage Node.

Before you start the runadmin utility, make sure that the SNA has been started in the storage node.

In the example below, you use $KVHOST to represent the host name of the Storage Node to which runadmin connects, and you use 5000 as the registry port.

Note: If your data store is non-secure, the -security option in the below command can be omitted.

> java -Xmx64m -Xms64m -jar $KVHOME/lib/kvstore.jar runadmin -host $KVHOST -port 5000 -security $KVROOT/security/client.security

Once running, the kv-> prompt is displayed.

kv->

If you want more than one Storage Node to support CLI commands, use the runadmin utility with -helper-hosts flag and list two or more Storage Nodes and ports as shown below. The use of multiple Storage Nodes helps in fault tolerance and load balancing.

> java -Xmx64m -Xms64m -jar $KVHOME/lib/kvstore.jar runadmin -helper-hosts <host2>:5000, <host3>:5000, <host4>:5000 -security $KVROOT/security/client.security

This command establishes a robust, secure connection point that is resilient to single-host failures by listing multiple potential connection points.

Configuring Remote Access in a Secure Store

In case of secure store, to use the runadmin utility from a remote machine, you must configure remote access using the following steps:

• Create the first admin user and grant the required readwrite privileges

• Store the password in a password file or wallet based on the password management mechanism that you have configured during the bootstrapping process.

• Take a copy of the client.security file that is present in the security folder. Name the copied file (for example, root.login). Append the user credentials (user name and password file/wallet) created in the previous steps, as security properties in this file.

• Copy the security folder to all the Storage Nodes in the cluster. The secure store will reject attempts to manage it using the runadmin utility from a remote machine until these initial user credentials have been defined.