Installing the Data Fabric Client on Ubuntu (Non-FIPS)
This section describes how to install the Data Fabric client on Ubuntu.
-
Remove any previous data-fabric client software. You can use
dpkg --list | grep mapr
to get a list of installed data-fabric packages. Then type the packages separated by spaces after thedpkg -r
command. For example:dpkg -r mapr-core mapr-fileserver
-
Update your Ubuntu repositories. For example:
apt-get update
- Import the
package keys to enable signature
verification:
Optionally, you may use commands to verify the signatures before installing the software. For more information, see HPE GPG Public Keys for GPG or RPM Signature Verification.wget --user=<email> --password=<token> -O /tmp/maprgpg.key -q https://package.ezmeral.hpe.com/releases/pub/maprgpg.key && rpm --import /tmp/maprgpg.key wget --user=<email> --password=<token> -O /tmp/hpeezdf.pub -q https://package.ezmeral.hpe.com/releases/pub/hpeezdf.pub && rpm --import /tmp/hpeezdf.pub && gpg --import /tmp/hpeezdf.pub
- Make sure the
client is running JDK 11 or later:
$ echo $JAVA_HOME /Library/Java/JavaVirtualMachines/jdk-11.0.1.jdk/Contents/Home $ /Library/Java/JavaVirtualMachines/jdk-11.0.1.jdk/Contents/Home/bin/java -version openjdk version "11.0.1" 2018-10-16 OpenJDK Runtime Environment 18.9 (build 11.0.1+13) OpenJDK 64-Bit Server VM 18.9 (build 11.0.1+13, mixed mode)
-
Run the following command to install the data-fabric client:
apt-get install mapr-client
-
To use this client with a secure cluster or clusters, copy the
ssl_truststore
andssl-client.xml
files from the/opt/mapr/conf
directory on the cluster to the/opt/mapr/conf
directory on the client.If this client will connect to multiple clusters, you must merge the
ssl_truststore
files on the server by using the/opt/mapr/server/manageSSLKeys.sh
tool, and then copy the merged file to/opt/mapr/conf
on the client. For an example of merging thessl_truststore
files, see step 3 in Configuring Secure Clusters for Running Commands Remotely. -
Run
configure.sh
to configure the client. In the following examples:
To ensure that the client can connect in the event of a CLDB node failure, all CLDB nodes are specified. For more information about the syntax, parameters, and behavior of-N
(uppercase)Specifies the cluster name -c
(lowercase)Specifies a client configuration -secure
Indicates that the cluster is secure -C
(uppercase)Specifies the CLDB nodes -HS
Specifies the HistoryServer node configure.sh
, see configure.sh.Secure cluster example/opt/mapr/server/configure.sh -N my.cluster.com -c -secure -C mynode01:7222,mynode02:7222,mynode03:7222 -HS mynode02
Non-secure cluster example/opt/mapr/server/configure.sh -N my.cluster.com -c -C mynode01:7222,mynode02:7222,mynode03:7222 -HS mynode02
NOTEIf the cluster was configured with a cluster-admin
user:group
that is different from the defaultmapr:mapr
value, you must include options to specify the cluster-admin user and group information when you runconfigure.sh
to configure the client.If the cluster-admin user ID is present on the client node, include these options:-u
-g
If the cluster-admin user ID is not present on the client node, include these options:-u
-g
--create-user | -a
-U
-G
-
At the end of the client installation, run the maprlogin password command to create a valid ticket to connect to the cluster.