Short summary:

This document details the steps involved in Installing latest version of Apache Incubator Ranger independently on RHEL / Ubuntu / SUSE / Debian OS.

• Ranger Admin support on Apache Components 

  Component name	Version	Reference
  HDFS	2.7.0	https://hadoop.apache.org/releases.html
  HIVE	1.2.0	https://hive.apache.org/downloads.html
  HBase	1.1.0.1	http://hbase.apache.org/
  Knox	0.6.0	https://knox.apache.org/
  Storm	0.10.0­beta1	https://storm.apache.org/downloads.html
  Yarn	2.7.0	http://hadoop.apache.org/docs/current/hadoop­-yarn/hadoop­-yarn-­site/YARN.html
  Zookeeper	3.4.6	https://zookeeper.apache.org/releases.html

Prerequisites

A. JDK 7 or above needs to be installed. 

B. Install latest version of Database MySQL/ ORACLE/ Postgres/ SQL Server

Instructions

Preparing to install

Install Maven

cd /usr/local 
# Download maven latest distribution tar from apache maven site
tar -­xvf apache-­maven-­<Version>-­bin.tar.gz

export M2_HOME=/usr/local/apache-­maven-­<Version>
export M2=$M2_HOME/bin 
export PATH=$M2:$PATH 
 
#Now to test your install of Maven, enter the following command
mvn -­version 

Install git

yum install git 

Install gcc and export JAVA_HOME

yum search gcc # Select the appropriate gcc and do 'yum install gcc' 
 
export JAVA_HOME=<Java Installation Directory>

Build Ranger Admin from source 

Clone the ranger source code

mkdir ~/dev 
cd ~/dev 
git clone https://github.com/apache/incubator­-ranger.git

Build the source 

cd incubator­-ranger 
export MAVEN_OPTS="­-Xmx512M" 
mvn clean compile package assembly:assembly install

• Verify all the tar files under target dir

Install Steps for Ranger Policy Admin on  RHEL

a. Lay down the build into appropriate places. Let’s start with the Ranger web admin first.

cd /usr/local 
sudo tar zxvf ~/dev/incubator­-ranger/target/ranger-­0.5.0-­admin.tar.gz
sudo ln ­-s ranger-­0.5.0-­admin ranger-­admin 
cd /usr/local/ranger-­admin 

b. Verify the root password that you had picked while installing mysql. I had chosen root so the relevant section in my install.properties file looks as follows:

db_root_user=root 
db_root_password=root
db_host=localhost

c.The install process would create a couple of users in the database for storing administration and audit information, pick passwords for those too. With my choices here’s how the relevant sections in the install.properties file look now.

  # DB UserId used for the XASecure schema 
  #
  db_name=ranger 
  db_user=rangeradmin 
  db_password=rangeradmin 
  # DB UserId for storing auditlog infromation 
  # 
  audit_db_name=ranger 
  audit_db_user=rangerlogger 
  audit_db_password=rangerlogger

d. Ranger allows you to get fancier with security and authentication mode but for now let’s just leave rest of the things in this file as they are.

e. Once all the required properties are updated run the setup.sh script

./setup.sh

f. This will install the Ranger service.  

g. After this Start Ranger Service by typing.  

./ews/ranger-­admin-­services.sh start 

h. After this Restart the Ranger Admin should work.

i.You can verify by visiting the external URL of the server using browser, for example: 

http://<Host Address>:6080/  

• Configuring Ranger Admin Authentication Modes :
  
•  ACTIVE DIRECTORY

      To enable active directory authentication on Ranger admin, you need to configure following properties of install.properties

       When searching a directory, the server might return several search results, in addition to
       a few continuation references that show where to obtain further results. These results
       and references might be interleaved at the protocol level. When property is set to
       "follow", the AD service provider processes all the normal entries first, before following
       the continuation references. When this property is set to "throw", all of normal entries are
       returned in the enumeration first, before the ReferralException is thrown. By contrast, a
      "referral" error response is processed immediately when property is set to "follow" or
      "throw".

• LDAP

• UNIX

• Configuring Ranger Admin HA Mode 

               a. Follow the ranger admin install steps above to install it on multiple hosts 

               b. Make sure to use the same configuration and policy DB details 

               c. Configure a load balancer to load balance among ranger admin instances and note down the load balancer URL.

• • • •  Software (e.g. Apache httpd) or hardware load balancer could be used.
      •  Details outside the scope of this document.                              

                d. Update the policy manager external URL in all the clients of ranger admin (ranger user sync and ranger plugins) to point to the load balancer URL.

                e. Restart all the clients.

Installing the Ranger User-Synch Process

 a. We’ll start by extracting out build at the appropriate place. 

cd /usr/local 
sudo tar ­zxvf ~/dev/ incubator­-ranger/target/ranger-­0.5.0-­usersync.tar.gz
sudo ln ­-s ranger-­0.5.0-­usersync ranger-­usersync
sudo mkdir ­-p /var/log/ranger-­usersync 
sudo chown ranger /var/log/ranger­-usersync 
sudo chgrp ranger /var/log/ranger­-usersync 
cd ranger­usersyncb. 

• Now let’s edit the install.properties file. Here are the relevant lines that you should edit:

• POLICY_MGR_URL = http://localhost:6080
• SYNC_SOURCE = unix  
• logdir = /var/log/ranger/usersync 

c. Now install the usersync by running the setup command 

export JAVA_HOME=/usr/lib/jvm/java­-1.7.0­-openjdk-­amd64 
./setup.sh 

After installing ranger­usersync, follow the same steps to start/stop services of usersync work.
./ranger­-usersync­-services.sh start 

Configuring Ranger User-Sync process to use LDAP/AD server:

      To Sync LDAP or AD users following properties should be configured in install.properties file before executing the setup.sh.

  Table: LDAP/AD Properties with sample values 

Installing Apache  Hadoop

• • Now let’s download and install hadoop. Following the excellent instructions available on the hadoop site itself. Follow steps given in pseudo distributed mode.

  • These instructions were written for version 2.7.0. So grab that tar (hadoop-­2.7.0.tar.gz) and checksum file (hadoop-­2.7.0.tar.gz.mds).

• • Instructions on this page ask that java be installed. If java is not there, install JDK first.

sudo yum install java-­1.7.0-­openjdk­-devel

• • Make note of the location where you installed hadoop. Here I assume that you have installed it in

/usr/local/hadoop

• • Create a user under which we could install and ultimately run the various hadoop processes. And login as that user.

sudo useradd ­­--home-­dir /var/hadoop --­­create-­home --­­shell /bin/bash ­­--user-­group hadoop

• •  if you get below given message then try next command  

sudo useradd --­­home-­dir /var/hadoop ­­--create-­home --­­shell /bin/bash hadoop -­g hadoop

sudo tar ­zxvf ~/dev/hadoop-­2.7.0.tar.gz -­C /usr/local
cd /usr/local 
sudo ln ­-s hadoop­-2.7.0 hadoop 
sudo chown hadoop -­R hadoop hadoop-­2.7.0
sudo chgrp hadoop ­-R hadoop hadoop­-2.7.0 

TO ADD HDFS USER

useradd hdfs 
to check whether user hadoop login works, try: ­ -sudo su ­-hadoop

Enabling Ranger HDFS Plugins

a. We’ll start by extracting our build at the appropriate place (/usr/local).

cd /usr/local
sudo tar zxvf ~/dev/incubator-­ranger/target/ranger-­0.5.0-­hdfs­-plugin.tar.gz 
sudo ln -­s ranger-­0.5.0-­hdfs-­plugin ranger-­hdfs-­plugin
cd ranger-­hdfs-­plugin 

b. Now let’s edit the install.properties file. Here are the relevant lines that you should edit:

• • Change the install.properties file 

c. Now enable the hdfs­-plugin by running the enable-­hdfs-­plugin.sh command (Remember to set JAVA_HOME)

Note: Hadoop conf and hadoop lib folder are not found at expected locations as per the script because of which Ranger hdfs plugin installation fails. To resolve this issue create a symlink as conf dir of hadoop linking to hadoop conf dir

cd /usr/local/hadoop
ln -­s /usr/local/hadoop/etc/hadoop/ /usr/local/hadoop/conf 

• Export HADOOP_HOME to bashrc

echo "export HADOOP_HOME=/usr/local/hadoop" >> /etc/bashrc 
cd /usr/local/ranger-­hdfs-­plugin 
./ enable-­hdfs-­plugin.sh

• One more change that we need to do is copy all the jar files from ${hadoop_home}/lib

cp /usr/local/hadoop/lib/*.jar /usr/local/hadoop/share/hadoop/hdfs/lib/

• Provide required permission to logs directory 

   chown root:hadoop /usr/local/hadoop/logs 
   chmod g+w /usr/local/hadoop/logs 

• Provide required permission to users in OS file system and hdfs file system according to your environment and requirement.

d.  Once these changes are done Restart hadoop.

• Stop NameNode, SecondaryNameNode and DataNode daemon: 

  su ­-l hdfs -­c "/usr/local/hadoop/sbin/hadoop­-daemon.sh stop namenode"
  su ­-l hdfs -­c "/usr/local/hadoop/sbin/hadoop-­daemon.sh stop secondarynamenode"
  su ­-l hdfs -­c "/usr/local/hadoop/sbin/hadoop-­daemon.sh stop datanode"

• Start NameNode, SecondaryNameNode and DataNode daemon: 

  su ­-l hdfs -­c "/usr/local/hadoop/sbin/hadoop­-daemon.sh start namenode"
  su -­l hdfs -­c "/usr/local/hadoop/sbin/hadoop­-daemon.sh start secondarynamenode"
  su ­-l hdfs ­-c "/usr/local/hadoop/sbin/hadoop­-daemon.sh start secondarynamenode"

e. This should start the association of ranger­hdfs­plugin with hadoop. 

• You can verify by logging into the Ranger Admin Web interface ­> Audit > Agents.

Installing Apache Hive(1.2.0)

• Let’s download and install apache hive . Following the excellent instructions available on the apache hive site itself

sudo tar xzvf ~/dev/apache-­hive-­1.2.0-­bin.tar.gz ­-C /usr/local
cd /usr/local 
sudo ln ­-s apache-­hive-­1.2.0-­bin hive
useradd hive
cd hive 
 
Export HIVE_HOME to bashrc 
echo "export HIVE_HOME=/usr/local/hive" >> /etc/bashrc  

Note:HiveServer2 doesn’t start unless HADOOP_VERSION is exported to bashrc

Enabling Ranger Hive Plugin

• We’ll start by extracting our build at the appropriate place. 
  

cd /usr/local 
sudo tar zxvf ~/dev/incubator­-ranger/target/ranger-­0.5.0-­hive­-plugin.tar.gz 
sudo ln -­s ranger-­0.5.0-­hive-­plugin ranger-­hive-­plugin
cd ranger­-hive-­plugin  

• Now let’s edit the install.properties file. Here are the relevant lines that you should edit:
• Change the insall.properties file 

•  Now enable the hive­-plugin by running the enable-­hive­-plugin.sh command (Remember to set JAVA_HOME)

cd /usr/local/ranger­-hive-­plugin
./enable­-hive-­plugin.sh 

• Once these changes are done Restart hive. This should start the association of ranger-­hive-­plugin with hive.
  1. You can verify by logging into the Ranger Admin Web interface ­> Audit Tab ­> Agents
• Provide required permission to users in OS file system and hdfs file system according to your environment and requirement..

mkdir /var/log/hive
chown -­R hive: hive /var/log/hive

• Change properties file permission for hive user.

chown -­R hive:hadoop /usr/local/apache-­hive-­1.2.0-­bin/conf/hiveserver2-­site.xml 
chown -­R hive:hadoop /usr/local/apache-­hive­-1.2.0­-bin/conf/hive-­log4j.properties
chown -­R hive:hadoop /usr/local/apache­-hive­-1.2.0­-bin/conf/hive­-site.xml

• To start hive metastore :

su ­-l hive -­c "env HADOOP_HOME=/usr/local/hadoop JAVA_HOME=/usr/lib/jvm/java-­1.7.0-­openjdk.x86_64 nohup hive --­­service metastore > /var/log/hive/hive.out 2> /var/log/hive/hive.log &”

• To start Hive server2 :

su -­l hive -­c "env HADOOP_HOME=/usr/local/hadoop JAVA_HOME=/usr/lib/jvm/java­-1.7.0-­openjdk.x86_64 nohup /usr/local/hive/bin/hiveserver2 ­hiveconf hive.metastore.uris=\" \" > /var/log/hive/hiveServer2.out 2>/var/log/hive/hiveServer2.log &”

• To Stop: 

ps aux | awk '{print $1,$2}' | grep hive | awk '{print $2}' | xargs kill >/dev/null 2>&1

• To Login in Hive shell: 

/usr/local/hive/bin/beeline ­-u "jdbc:hive2://localhost:10000" -­n rituser ­-p rituser

• If hive metastore and hiveserver2 do not start then update below given key-­values according to your environment in following files.

hiveserver2­site.xml  

hive­site.xml 

Installing Apache Hbase (1.1.0.1)

• Let’s download and install apache Hbase . Following the excellent instructions available on he apache Hbase site itself.

sudo tar xzvf ~/dev/hbase­-1.1.0.1-­bin.tar.gz -­C /usr/local
cd /usr/local
sudo ln ­-s hbase-­1.1.0.1 hbase
useradd hbase 
cd hbase 
 
Export HBASE_HOME to bashrc 
echo "export HBASE_HOME=/usr/local/hbase" >> /etc/bashrc 

• For HBase 0.98.5 and later, you are required to set the JAVA_HOME environment variable before starting HBase

Enabling Ranger Hbase Plugins

• We’ll start by extracting our build at the appropriate place.
  

cd /usr/local 
sudo tar zxvf ~/dev/incubator-­ranger/target/ranger­-0.5.0-­hbase­-plugin.tar.gz 
sudo ln -­s ranger-­0.5.0-­hbase-­plugin ranger-­hbase-­plugin
cd ranger­-hbase­-plugin 

• Now let’s edit the install.properties file. Here are the relevant lines that you should edit:
• Change the insall.properties file 

• Now enable the hbase­-plugin by running the enable­-hbase-­plugin.sh command (Remember to set JAVA_HOME)

cd /usr/local/ranger-­hbase-­plugin 
./enable-­hbase-­plugin.sh

• Once these changes are done Restart hbase. This should start the association of ranger-­hbase-­plugin with hbase.

1. 1. You can verify by logging into the Ranger Admin Web interface ­> Audit Tab ­> Agents

•  To Stop master and regionserver try: 

/usr/local/hbase/bin/hbase­-daemon.sh stop master 
/usr/local/hbase/bin/hbase­-daemon.sh stop regionserver

•  Provide required permission to users in OS file system and hdfs file system according to your environment and requirement.

Installing Apache Knox Gateway

• Let’s download and install apache Knox from Apache Mirrors.

sudo tar ­-zxvf ~/dev/knox-­0.6.0.tar.gz -C /usr/local
cd /usr/local
sudo ln -­s knox-­0.6.0 knox
cd knox

• Following the instructions available on the apache knox site itself (To install  Apache Knox Gateway). 

Knox Master Secret : knox 

Enabling Ranger Knox Plugins

• We’ll start by extracting our build at the appropriate place. 

cd /usr/local
tar ­-zxvf ~/dev/incubator-­ranger/target/ranger-­0.5.0-­knox­-plugin.tar.gz
sudo ln -­s ranger-­0.5.0-­knox­-plugin ranger-­knox-­plugin
cd ranger­-knox-­plugin 

• Now let’s edit the install.properties file. Here are the relevant lines that you should edit:
• Change the insall.properties file 

• Now enable the knox­-plugin by running the enable-­knox-­plugin.sh command (Remember to set JAVA_HOME)

cd /usr/local/ranger-­knox-­plugin
./enable-­knox-­plugin.sh

• Once these changes are done Restart Knox ( Gateway / LDAP ) 
• if you get permission denied error during knox start please provide required privileges to knox user. for example : 

chown -­R knox:knox /usr/local/knox/data 
chown ­-R knox:knox /usr/local/knox/logs
chown ­-R knox:knox /usr/local/knox/pids 
chown ­-R knox:hadoop /usr/local/knox/pids/*

• You can verify by logging into the Ranger Admin Web interface ­> Audit > Agents

Trusting Self Signed Knox Certificate

       When Knox is listening on its SSL port with self signed certificate, you have to import SSL certificate of Knox into truststore used by XA PolicyManager. Here are steps for importing Knox SSL certificate in truststore used by XA PolicyManager.

• Log in the machine running Knox
• Export knox certificate

1. 1. cd $GATEWAY_HOME/data/security/keystores 
   2. This is typically /usr/local/knox/data/security/keystores on Linux machine. 
   3. keytool -­exportcert ­-alias gateway-­identity -­keystore gateway.jks -­file knox.crt

• Copy knox.crt file onto machine running Ranger Admin/PolicyManager to a working directory, for example /usr/local/ranger-­admin
• Replicate cacerts

cd /usr/local/ranger-­admin
cp $JAVA_HOME/jre/lib/security/cacerts cacertswithknox

• Import Knox certificate into the replicated new keystore

keytool -­import -­trustcacerts -­file <knox.crt created above> -­alias knox -keystore cacertswithknox
password: changeit

• Edit /usr/local/ranger-­admin/ews/ranger-­admin-­services.sh

1. 1. Add parameter -­Djavax.net.ssl.trustStore=<path to the cacertswithknox> to the java call in the script.

• Restart Ranger Admin/PolicyManager. 

Installing Apache Storm (0.10.0)

• Let’s download and install apache Storm from Apache Mirrors

sudo tar ­-zxvf ~/dev/apache­-storm-­0.10.0-­beta1.tar.gz -C /usr/local
cd /usr/local
sudo ln ­-s apache-­storm­-0.10.0­beta1 storm 
cd storm 

• Following the instructions available on the apache storm site itself(To install Apache Storm).

Enabling Ranger Storm Plugins

• We’ll start by extracting our build at the appropriate place. 
  

cd /usr/local 
tar -­zxvf ~/dev/incubator-­ranger/target/ranger-­0.5.0-­storm-­plugin.tar.gz
sudo ln -­s ranger-­0.5.0-­storm-­plugin ranger-­storm-­plugin 
cd ranger-storm-plugin	

• Now let’s edit the install.properties file. Here are the relevant lines that you should edit:
• Change the insall.properties file 

• Now enable the storm-plugin by running the enable-­storm-plugin.sh command (Remember to set JAVA_HOME)

cd /usr/local/ranger-­storm-­plugin
./enable­-storm-­plugin.sh  

• Once these changes are done Restart Storm
• You can verify by logging into the Ranger Admin Web interface ­> Audit > Agents

Installing Apache Yarn

You can run a MapReduce job on YARN in a pseudo­distributed mode by setting a few parameters and running ResourceManager daemon and NodeManager daemon in addition

The following instructions assume that hadoop installations steps mentioned in Installing Apache Hadoop are already executed.

Enabling Ranger Yarn Plugin

• We’ll start by extracting our build at the appropriate place (/usr/local). 

cd /usr/local  
sudo tar zxvf ~/dev/incubator-­ranger/target/ranger-­0.5.0-­yarn-­plugin.tar.gz  
sudo ln -­s ranger-­0.5.0-­yarn-­plugin ranger-­yarn-­plugin
cd ranger­-yarn-­plugin

• Now let’s edit the install.properties file. Here are the relevant lines that you should edit:
• Change the install.properties file 

• Now enable the yarn­-plugin by running the enable-­yarn-­plugin.sh command.

cd /usr/local/ranger-­yarn-­plugin
./ enable-­yarn-­plugin.sh

• One more change that we need to do is copy all the jar files from  ${hadoop_home}/lib

cp /usr/local/ranger­-yarn-­plugin/lib/*.jar /usr/local/hadoop/share/hadoop/yarn/lib/

• if you get permission denied error during yarn start please provide required privileges to yarn user in local and hdfs file system. for example :

mkdir /var/log/yarn
chown ­-R yarn:yarn /var/log/yarn

• Once these changes are done Start ResourceManager daemon and NodeManager daemon.
  • Start the ResourceManager on ResourceManager hosts. 

su yarn ­-c "/usr/local/hadoop/sbin/yarn­-daemon.sh start resourcemanager"
ps ­-ef | grep -­i resourcemanager 

• • Start the NodeManager on NodeManager hosts. 

su yarn ­-c "/usr/local/hadoop/sbin/yarn-­daemon.sh start nodemanager"
ps -­ef | grep -­i nodemanager

• • Stop the ResourceManager on ResourceManager hosts. 

su yarn ­-c "/usr/local/hadoop/sbin/yarn-­daemon.sh stop resourcemanager"
ps ­-ef | grep -­i resourcemanager

• • Stop the NodeManager on NodeManager hosts. 

su yarn -­c "/usr/local/hadoop/sbin/yarn-­daemon.sh stop nodemanager"
ps ­-ef | grep -­i nodemanager 

• This should start the association of ranger-­yarn-­plugin with hadoop. 

1. 1. You can verify by logging into the Ranger Admin Web interface ­> Audit > Agents

Installing Ranger KMS (0.5.0)

• Download “Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files” zip using below link depending upon the Java version used

1. 1. http://www.oracle.com/technetwork/java/javase/downloads/jce­-7­download-­432124.html 
   2. http://www.oracle.com/technetwork/java/javase/downloads/jce8­download­2133166.html

• unzip the above downloaded zip file to java’s security folder (Depending upon the java version used)

unzip UnlimitedJCEPolicyJDK7.zip into $JDK_HOME/jre/lib/security 
unzip jce_policy-­8.zip into $JDK_HOME/jre/lib/security 

 STEPS FOR RANGER KMS:

• We’ll start by extracting our build at the appropriate place(/usr/local). 

cd /usr/local 
sudo tar ­-zxvf ~/dev/incubator­-ranger/target/ranger-­0.5.0-­kms.tar.gz  
sudo ln ­-s ranger-­0.5.0-­kms ranger-­kms 
cd ranger-­kms 

• Please note that Ranger KMS plugin is integrated with Ranger KMS and will be installed automatically when KMS is installed.
• Now let’s edit the install.properties file. Here are the relevant lines that you should edit:
• Change the install.properties file 

1. 1. DB_FLAVOR 
   2. SQL_CONNECTOR_JAR 
   3. db_root_user 
   4. db_root_password
   5. db_host 
   6. db_name
   7. db_user 
   8. db_password 

• Edit “hdfs-site.xml”( Need to give provider else it will not support hadoop commands)Replace localhost with <internal host name> 

1. 1. Go to path cd /usr/local/hadoop/conf/ 

   2. vim hdfs­site.xml 

   3. For property “dfs.encryption.key.provider.uri” ,enter the value “kms://http@<internal host name>:9292/kms”

   4. save and quit 

• Edit “core­site.xml”( Need to give provider else it will not support hadoop commands)

• Replace localhost with <internal host name> 

1. 1. Go to path cd /usr/local/hadoop/conf/ 
   2. vim core­site.xml 
   3. For property “hadoop.security.key.provider.path” ,enter the value “kms://http@<internal host name>:9292/kms”

• Once these changes are done Restart hadoop.

1. 1. Stop NameNode, SecondaryNameNode and DataNode daemon: 

su -­l hdfs -­c "/usr/local/hadoop/sbin/hadoop­daemon.sh stopnamenode"
su ­-l hdfs -­c "/usr/local/hadoop/sbin/hadoop­daemon.sh startnamenode"

• Run setup  

./setup.sh

• Start the kms server

ranger­-kms start

• You can verify the plugin is communicating to Ranger admin in Audit-­>plugins tab.
• If kmsdev service is not created in Ranger Admin then kms­-plugin will not able to connect to Ranger admin.
• To Create the Kms service 

   ENABLING AUDIT LOGGING TO HDFS:

• To enable Audit to HDFS for a plugin do the below:

1. 1. set XAAUDIT.HDFS.ENABLE = true for respective component plugin in the install.properties file which may be found in /usr/local/ranger­<component>­plugin/ directory. 
   2. configure NameNode host in the XAAUDIT.HDFS.HDFS_DIR.
   3. create a policy in HDFS service from Ranger Admin for individual component users (hive/hbase/knox/storm/yarn/kafka/kms) to give READ+ WRITE permission for the particular audit folder. i.e for enabling Hive component to log Audits to HDFS , we need to create a policy for hiveuser with READ+ WRITE permissions to respective audit directory
   4. Audit to HDFS caches logs in local directory, which can be specified in XAAUDIT.HDFS.LOCAL_BUFFER_DIRECTORY ( this can be like ‘/var/log/<component>/**), which is the path where audit is stored temporarily, likewise for archived logs we need to update XAAUDIT.HDFS.LOCAL_ARCHIVE_DIRECTORY value ( this can be like ‘/var/log/<component>/**), before enabling the plugin for the component.

    ENABLING AUDIT LOGGING TO SOLR:

1. To enable Audit report from Solr, do the below change in Ranger admin: 

• Set following properties in install.properties of ranger service to work audit to solr in Ranger

Restart Ranger.

   2. To enable Audit to Solr for a plugin do the below:

• Set following properties in install.properties of plugin to start logging audit to Solr : for eg Hbase

• Enable ranger plugin for Hbase. 
• Restart Hbase component.