Table of Contents

Search

  1. Preface
  2. Installing MDM Big Data Relationship Management
  3. Configuring MDM Big Data Relationship Management
  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 the RESTful Web Services

Packaging the RESTful Web Services

Before you use the RESTful web services, package the web services in a WAR file. Use the configuration file and the matching rules file to package the web services.
Run the
run_deployment.sh
script located in the following directory to package the web services in a WAR file:
/usr/local/mdmbdrm-<Version Number>
The
run_deployment.sh
script uses one of the following pre-installed WAR files based on the HBase version that you use:
  • For HBase version 0.94.x,
    /usr/local/mdmbdrm-<Version Number>/bin/MDMBDRMV94.war
    You must rename the
    MDMBDRMV94.war
    file to
    MDMBDRM.war
    before you run the
    run_deployment.sh
    script.
  • For HBase version 0.96.x or later,
    /usr/local/mdmbdrm-<Version Number>/bin/MDMBDRM.war
To run the
run_deployment.sh
script, use the following command:
run_deployment.sh --config=configuration_file_name --installbin=install_bin_directory [--override] [--id=configuration_matching_rules_files_identifier] [--rule=matching_rules_file_name] [--security=security_properties_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 MDM Big Data Relationship Management installation.
--override
Optional. Indicates to include the generated JAR file into the
MDMBDRM.war
file.
If you want to use multiple configuration files, you can specify the
--override
option to override the
MDMBDRM.war
file.
You must have the root privileges to override the
MDMBDRM.war
file.
By default, the script loads the generated WAR file in the local working directory.
--id
configuration_matching_rules_files_identifier
Optional. Unique identifier for the configuration file and the matching rules file. The WAR file generated in the local directory and the REST API URLs use the identifier.
The name format of the WAR file generated in the local directory is
MDMBDRM<id>
, and the format of the REST API URL is
http://<Host>:<Port>/MDMBDRM<id>/<Version Number>/<id>/<Operation Name>
.
For example, if you specify
--id=Dev20
, the name of the WAR file generated in the local directory is
MDMBDRMDev20.war
, and the format of the REST API URL is
http://<Host>:<Port>/MDMBDRMDev20/<Version Number>/Dev20/<Operation Name>
.
By default, the WAR file generated in the local directory and the REST API URLs use a system-generated identifier, which is difficult to interpret. For example,
http://localhost:8080/MDMBDRM1131329172862026293/v2.0/0fb349e3-807a-4235-a100-134a3b51ad5d
.
--rule
matching_rules_file_name
Optional. Absolute path and file name of the matching rules file that you create.
--security
security_properties_file_name
Required if you configure security for the web services. Absolute path and name of the
security.properties
file.


Updated June 27, 2019