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
  8. Troubleshooting

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. You can use the configuration file, the matching rules file, and the relationship configuration file to package the web services. If you want to package the relationship graph user interface, you must specify the properties file for the relationship graph.
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 --rule=matching_rules_file_name --installbin=install_bin_directory [--relationship=relationship_configuration_file_name] [--uiconfig=ui_properties_file] [--override] [--id=configuration_matching_rules_files_identifier] [--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.
--rule
matching_rules_file_name
Optional. Absolute path and file name of the matching rules file that you create.
--installbin
install_bin_directory
Absolute path to the
bin
directory of the
Relate 360
installation.
--relationship
relationship_configuration_file_name
Optional. Absolute path and file name of the relationship configuration file.
If you plan to create relationships between the processed data, you must specify the relationship configuration file.
--uiconfig
ui_properties_file
Optional. Absolute path and file name of the properties file that you create for the relationship graph user interface.
If you want to package the relationship graph user interface in a WAR file, specify the properties file.
You require only one relationship graph user interface WAR file for your environment.
The default package name for the relationship graph user interface is
bdrm-ui.war
.
--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/
v5.0
/0fb349e3-807a-4235-a100-134a3b51ad5d
.
--security
security_properties_file_name
Required if you configure security for the web services. Absolute path and name of the
security.properties
file.
For example, the following sample command generates a WAR file for the RESTful web services and another WAR file for the relationship graph user interface:
run_deployment.sh --config=/usr/local/conf/config_big.xml --rule=/usr/local/conf/matching_rules.xml --relationship=/usr/local/conf/relconfig.xml --installbin=/usr/local/mdmbdrm-10.0/bin --id=Customer360 --security=/usr/local/conf/security.properties --uiconfig=/usr/local/conf/ui.properties


Updated June 27, 2019