Installation Guide
- 1 Prerequisites
- 2 Create the Datameer X User
- 3 Create Directories for Application, Cache, Logs, and Temporary Files
- 4 Switch the User and Change the Working Directory
- 5 Downloading and Unzipping Datameer X
- 6 Selecting and Preparing the Data Base
- 7 Download and Install the MySQL Database JDBC Connector
- 8 Configure Datameer X for MySQL Database
- 9 Installing the License
- 10 Start Datameer
- 11 Stop Datameer
- 12 Restart Datameer
- 13 Datameer X Graceful Shutdown
- 14 Service Check
- 15 Configure Datameer X for Kerberos Secured Cluster
- 16 Secure Hadoop Distributed Filesystem (HDFS)
- 17 Start Testing
- 18 Best Practices for Installing Datameer
- 18.1 Implement frequent database backups
- 18.1.1 Backup via crontab
- 18.1.2 Verify backup
- 18.2 Change your stored data directory
- 18.3 Change the default admin password
- 18.4 Download and install plug-ins
- 18.5 Configure Datameer X for enterprise
- 18.6 Review the changes implemented by accessing the change log
- 18.7 Enable and configure transport layer security (TLS)
- 18.8 Configure bash for operations
- 18.9 Conductor.sh commands and parameters
- 18.1 Implement frequent database backups
Prerequisites
Complete the following prerequisites before installing Datameer X
Install the Hadoop client
Datameer X application server, as well all data nodes, are configured properly with host names, DNS, datetime, NTP, and other details
Datameer X application server, as well all data nodes, have Java 1.8 (Oracle recommended)
Check this installation using the following commands:
java -versionandecho $JAVA_HOME
Datameer X application server has Oracle Java Cryptography Extension (JCE) already installed. See Java SE Security for more information.
Commands such as
hadoop,yarn, andmysqlcan be executed
Install MySQL client
For Datameer's application database, the MySQL server must be prepared with necessary access
Grant administrative rights or
rootaccessEnsure Internet access to download packages and plug-ins or have necessary ZIP files downloaded and available
If using Kerberos, configure a Kerberos Secured cluster for secure impersonation
Create the Datameer X User
Administrative rights are required to create the Datameer X user on the machine where Datameer X is being installed. This can be accomplished under the root account. Make sure the user ID is above 500 and that the account has enough resources and file descriptors available.
Create the user account under which the Datameer X service will be started and running later:
Create user
./usr/sbin/groupadd --system datameer ./usr/sbin/useradd --system --create-home --gid datameer datameerThese commands also create the directory
/home/datameer.
Check the max number of open files - global level or per-user limits (or both) - and set it to 64K if it isn't set already. This configuration needs to be done on all nodes within the cluster and might require a reboot.
Create Directories for Application, Cache, Logs, and Temporary Files
For performance reasons and to have better control about where space on the file systems and on disks is used, create separate directories for application, cache, logs, and temporary files. Do this according the Linux Filesystem Hierarchy Standard (FHS). To create the directories and change the permissions you need administrative rights. Complete this task under the user account root.
Create the directories for application, cache, logs, and temporary files:
Create directories
mkdir -p /opt/datameer chown -R datameer:datameer /opt/datameer mkdir -p /var/cache/datameer chown -R datameer:datameer /var/cache/datameer mkdir -p /var/log/datameer chown -R datameer:datameer /var/log/datameer mkdir -p /tmp/datameer chown -R datameer:datameer /tmp/datameer
Switch the User and Change the Working Directory
This should be the last task to which administrative rights are necessary.
Switch to the new Datameer X user and change to the working directory where Datameer X is being installed:
Switch user and directory
su - datameer cd /opt/datameerProceed from within the Datameer X installation directory and under the user account
datameeronly.
Downloading and Unzipping Datameer X
Get in touch with Datameer Support or your Datameer representative to receive the installation package download link.
Download and unzip the appropriate Datameer X package for your Hadoop cluster distribution:
INFO: If you have already a Datameer X installation you can also start from here.
Switch user and directory
curl -s -k -o Datameer-<package>.zip "https://download.datameer.com.s3.amazonaws.com/releases/Datameer-<version>/<dist>/Datameer-<package>.zip?<AWSproperties>" ; unzip Datameer* Creating Symlinks for Future Updates
TIP
To be prepared for future upgrades, you should create symlinks to the current (or latest) package as well as for the log directory.
Create the symlink and change the working directory:
ln -s Datameer-<package> current
cd currentSelecting and Preparing the Data Base
INFO
By default, the Datameer X application runs with an HSQL file data base that is created on the local filesystem under 'das-data/database/hsql-db'.
If you are setting up Datameer X for production use, Datameer X strongly recommends MySQL instead of the HSQL file database. MariaDB is also supported as an alternative metastore database engine to MySQL.
To define which database to use, make an entry in the 'live.properties' file under 'conf/live.properties':
#Define which database to use: hsql-memory, hsql-file, mysql, mariadb
system.property.db.mode=mysqlor
#Define which database to use: hsql-memory, hsql-file, mysql, mariadb
system.property.db.mode=mariadb Download and Install the MySQL Database JDBC Connector
By default, the Datameer X application runs with an HSQL file database that is created on the local filesystem under das-data/database/hsql-db. If you are setting up Datameer X for production use, Datameer X strongly recommends using MySQL instead of the HSQL file database.
As of Datameer X 7.4: MariaDB is supported as an alternative to MySQL.
Download the official MySQL JDBC driver ZIP file, extract the driver from the archive file, and copy it into the correct destination:
Download and install JDBC
# Lookup latest JDBC driver version JDBCDRV="$(curl -s -k 'https://dev.mysql.com/downloads/connector/j/' | grep -o -m 1 'mysql-connector-java.*zip')" # Download latest JDBC driver version curl -s -L0 -k -O "https://dev.mysql.com/get/Downloads/Connector-J/${JDBCDRV}" # Unzip driver package unzip mysql-connector* -d etc/custom-jars # Move only the necessary JAR file mv etc/custom-jars/mysql-connector*/*bin.jar etc/custom-jars # Clean up rm -rf etc/custom-jars/mysql-connector-java-?.?.??Double-check if
etc/custom-jarscontain the latestmysql-connector-java-<version>-bin.jar:Check installation
echo $JDBCDRV ll etc/custom-jars
Configure Datameer X for MySQL Database
Datameer X service depends on the MySQL database. The MySQL database is used for writing to workbooks, permission changes, job execution, scheduling, and more. To function properly, a response time should be between ten and twenty milliseconds. To run the application in MySQL mode, the following changes need to be implemented. As of Datameer X 7.4: MariaDB is supported as an alternative to MySQL.
Check database connection:
Connection check
mysqladmin version mysqladmin ping mysqladmin status echo q | telnet -e q `hostname` 3306 nc -z -w1 `hostname` 3306You can follow up later with using the Check if the Datameer X Application Database is Running and Accessible article.
Initialize application database:
Initialize database
mysql -uroot -p < bin/mysql-init.sql mysql -uroot -p dap < bin/create-tables.sql