Installing the Tag Synchronization Module
To install the tag synchronization module:
Log in to the host machine as super-user (root).
Locate and download the ranger-tagsync package, then install it by executing
yum install ranger-tagsync
.Installing the ranger-tagsync package will unpack and create a directory (
ranger-tagsync-install-directory
) and needed sub-directories and files in theranger-tagsync
directory under the Apache installation root directory.Make the
ranger-tagsync-install-directory
your current working directory.cd ranger-tagsync-install-directory
Set up the JAVA_HOME environment variable to point to Java distribution on the installation machine.
export JAVA_HOME=location-of-java-home-on-the-installation-machine
Edit the
install.properties
file in theranger-tagsync-install-directory
to reflect the operational environment.Table 13.10. install.properties File Properties
Property Description Comments TAGADMIN_ENDPOINT URL of the destination of the tags Customize the value to reflect your deployment TAGADMIN_SSL_CONFIG_FILENAME File containing SSL configuration Customize the value to point to SSL configuration specific to your deployment. The value will be ignored in the scheme in TAGADMIN_ENDPOINT URL is "http". TAGSYNC_KEYSTORE_FILENAME File to store encrypted password for Ranger Admin user ‘rangertagsync’ that is used for communicating with TagAdmin Customize the value to suit your deployment. If there is no value specified then the password will not be encrypted. TAG_SOURCE Source of the tagging information At this time, the only supported value is ‘Atlas’. TAGSYNC_ATLAS_KAFKA_ENDPOINTS URL of the Kafka endpoint to which Atlas sends its notifications Customize the value to reflect your deployment. TAGSYNC_ATLAS_ZOOKEEPER_ENDPOINT URL of the ZooKeeper endpoint needed for Atlas Customize the value to reflect your deployment. TAGSYNC_ATLAS_CONSUMER_GROUP String representing Kafka Consumer Group ID used by Tag-Sync Customize the value to reflect your deployment. TAGSYNC_ATLAS_TO_RANGER_SERVICE_MAPPING Mapping between Atlas cluster-name, component-type, and Ranger service-name This mapping is provided as a string value in the following format.
clusterName,componentType,serviceName;clusterName2,componentType2,serviceName;..,
Customize the value to reflect your deployment.
unix_user ranger-tagsync process is run as this Unix user. There is no need to change this value (default is ‘ranger’). unix_group ranger-tagsync process is run with this Unix group-id. There is no need to change this value (default is ‘ranger’). logdir Directory where logs are store Customize the value to suit your deployment. Run the setup script to create the run-time directory structure.
./setup.sh
The run-time directory structure copies scripts into appropriate directories, creates files required for Atlas integration, creates configuration files which are used by the ranger-tagsync process to configure itself, and sets up symbolic links wherever necessary.
Table 13.11. Run-time Directory Structure
Directory File Linked to /etc/ranger/tagsync/conf ranger-tagsync-install-directory/conf /etc/ranger/tagsync/conf application.properties Properties required for Atlas interface /etc/ranger/tagsync/conf java_home.sh Shell command to set JAVA_HOME environment variable /etc/ranger/tagsync/conf log4j.xml Log4j configuration properties /etc/ranger/tagsync/conf ranger-tagsync-site.xml Ranger-tagsync process configuration properties /etc/ranger/tagsync/conf rangertagsync.jceks Encrypted password for Ranger Admin user ‘rangertagsync’ /etc/init.d ranger-tagsync Shell script to start/stop/query ranger-tagsync service /usr/bin ranger-tagsync-services.sh ranger-tagsync-install-directory/ranger-tagsync.sh /var/log/ranger/tagsync ranger-tagsync-install-directory/log Directory where logs (ranger-tagsync.log*) generated by ranger-tagsync are stored. /var/run/ranger tagsync.pid File containing process-id of the ranger-tagsync process, if it is running