Table of Contents

Search

  1. Preface
  2. Installing Informatica MDM - Relate 360
  3. Configuring Relate 360
  4. Configuring Security
  5. Setting Up the Environment to Process Streaming Data
  6. Configuring Distributed Search
  7. Packaging and Deploying the RESTful Web Services

Installation and Configuration Guide

Installation and Configuration Guide

Packaging and Deploying the Coprocessor JAR File

Packaging and Deploying the Coprocessor JAR File

For the region servers to perform searches, you must package the search logic in a JAR file. You can then deploy the generated JAR file to a directory in HDFS so that the region servers can access the search logic.
To package the search logic in a JAR file, run the
run_deployment.sh
script located in the following directory:
/usr/local/mdmbdrm-<Version Number>
  1. Use the following command to run the
    run_deployment.sh
    command:
    run_deployment.sh --config=configuration_file_name --installbin=install_bin_directory --coprocessor --id=identifier_for_the_JAR_file [--rule=matching_rules_file_name]
    The following table describes the options and arguments that you must specify to run the
    run_deployment.sh
    script:
    Option
    Argument
    Description
    --config
    configuration_file_name
    Absolute path and file name of the configuration file that you create.
    --installbin
    install_bin_directory
    Absolute path to the
    bin
    directory of the
    Relate 360
    installation.
    --id
    identifier_for_the_JAR_file
    Unique identifier for the coprocessor JAR file.
    The name format of the generated JAR file is
    db-hbase-coprocessor<id>
    . For example, if
    id=Deploy
    , the generated JAR file name is
    db-hbase-coprocessorDeploy.jar
    .
    Ensure that you use the same identifier that you used in the
    CoprocessorPath
    parameter of the configuration file.
    --rule
    matching_rules_file_name
    Optional. Absolute path and file name of the matching rules file that you create.
    --coprocessor
    Indicates that the script generates the coprocessor JAR file.
  2. Deploy the generated JAR file to the directory that you configured for the
    CoprocessorPath
    parameter in the configuration file.
    For example, the following command deploys a JAR file to an HDFS directory:
    hadoop fs -put -f db-hbase-coprocessorDeploy.jar /user/cloudera/


Updated June 27, 2019