/
(GLUE-1812) Configuration

(GLUE-1812) Configuration

Dec 21, 2018

Connection parameters to an external HTTP server are stored within a dedicated RFC destination for Oozie service:

  1. Go to transaction SM59.

  2. Create a new RFC Connection of type ‘G’.

  3. Set the following parameters and save the RFC destination:

    • Target Host: The host name Oozie server runs on. Default value is the output of the command hostname –f on the Hadoop cluster.

    • Service No.: The port Oozie server runs. Default value 11000.

    • Path Prefix: The path must have following syntax: /oozie/v1

      • /oozie/v1 – mandatory path prefix defined by the Oozie Web Services API.

Subsequently, configure the connection customising tables:

  1. Go to the Table View Maintenance for the configuration table /DVD/OOZIE_CUS_C using the transaction SM30.

  2. Create entries with the following values for the Oozie RFC:

    1. user.name: Name of a Hadoop user on whose behalf Oozie Web Services will submit and manage jobs. Also the user is either the owner or has required privileges (read, write, delete) for the directory <hdp_usr_home_path> set in the RFC destination (see the chapter RFC Destination).

    2. queueName: Specify the queue in which should job run. Default value: default.

    3. nameNode: The host name and port of the cluster’s NameNode - [format: hdfs://${HOSTNAME}:${PORT}] , *NOTE: port number usually is 8020

    4. jobTracker: The host name and port on which the JobTracker run [format: ${HOSTNAME}:${PORT}], *NOTE: port number is usually 8032

    5. apps.default.directory: A directory where all applications will be stored. The user specified in user.name must have required privileges for the directory.

    6. oozie.default.directory: A sub-directory where all oozie applications will be stored.

    7. hcat.metastore.uri: the Hive Metastore URI. [format: thrift: ://${HOSTNAME}:${PORT}]

      1. If the Kerberos Authentication is enabled only

    8. hcat.metastore.principal: Hive Metastore principal. [format: hive/_HOST@MYREALM]

      1. If the Kerberos Authentication is enabled only

  3. Save the entry.

  4. Go to the Table View Maintenance for the configuration table /DVD/HDP_CUS_C using the transaction SM30.

  5. Create an entry with the following values:

    1. RFC Destination: RFC Destination that refers to the Oozie service (see the chapter RFC Destination)

    2. User Name: Name of a Hadoop user on whose behalf Oozie Web Services will submit and manage jobs. Also the user is either the owner or has required privileges (read, write, delete) for the directory <hdp_usr_home_path> set in the RFC destination (see the chapter RFC Destination).

    3. Authentication Method: 

      1. NO_AUTHENTICATION: No Hadoop-specific authentication is applied

      2. PSEUDO_AUTHENTICATION: The user accessing Oozie is identified only by the user name

      3. KERBEROS: Kerberos authentication 

    4. [KERBEROS ONLY] Kerberos keytab: logical file path to kerberos keytab

    5. [KERBEROS ONLY] Kerberos Config. File: logical file path to kerberos config

    6. [KERBEROS ONLY] Kerberos Auth. Service RFC: RFC connection to JAVA instance which runs Kerberos authorisation service

  6. Save the entry.