MAK mdatamanager integration

Overview

The TMG mdatamanager (MAK) tool is integrated with DOH and can be executed as a task within a DOH chain. The required mdatamanager execution components are included in the standard DOH installation.

This tool uses validation rules defined in XML files, which are not included in the DOH distribution and must be obtained separately from the TMG product team.

This document describes the installation requirements, configuration steps, and operational procedures required to execute mdatamanager validation jobs through DOH.

Prerequisites

Before configuring mdatamanager, ensure that:

DOH has been successfully installed.
The required mdatamanager validation rule XML files have been obtained from the TMG product team.
Database connectivity information is available for the target validation database.
Required user permissions are available to execute shell scripts and access database resources.

mdatamanager directory

After DOH is installed, an app folder is created in the DOH installation directory. This folder contains the mdatamanager directory.

It contains the following subdirectories:

Directory Description

bin Contains shell scripts used to execute mdatamanager processes.

network

Directory	Description
bin	Contains shell scripts used to execute mdatamanager processes.
network	Contains Oracle network configuration files, including `tnsnames.ora`. The `tnsnames.ora` must be manually updated to specify the appropriate database connection.
web_support	Contains web resources used by mdatamanager reporting screens.

Contains Oracle network configuration files, including tnsnames.ora.

The tnsnames.ora must be manually updated to specify the appropriate database connection.

web_support Contains web resources used by mdatamanager reporting screens.

Make shell scripts executable

The shell scripts provided with mdatamanager must have execute permissions before they can be run.

Execute the following command:

chmod +x /app/mdatamanager/bin/*.sh

Verify that all required scripts have executable permissions.

Configure database connection

The mdatamanager requires database connectivity to execute validation rules.

Update app/mdatamanager/network/admin/tnsnames.ora with the appropriate database connection details:

Database service name
Host name
Port number
Connection alias

The connection details must match the database environment where validation will be executed.

Create the rules directory

Create a rules directory under the app/mdatamanager. Copy the validation rule XML files provided by the TMG product team into this directory.

The contents of the rules directory may vary depending on the implementation. It will contain one or more XML files. The ones relevant to DOH are the following highlighted validation XML files.

Update database connection properties

Each validation rule XML file contains database connection properties. Before execution, update the relevant val XML files to reference the correct validation database.

<DB_CONNECTOR
    NAME="IMPORT_AUTH"
    DESCRIPTION="Authentication server"
    DB_TYPE="IMPORT_AUTH"
    TNS_NAME="INTERNAL">
</DB_CONNECTOR>

<DB_CONNECTOR
    NAME="CCB_DBC"
    DESCRIPTION="Destination database"
    DRIVER="oracle.jdbc.driver.OracleDriver"
    URL="jdbc:oracle:thin:@localhost:1521:DIHDB"
    DB_TYPE="Oracle"
    TNS_NAME="DIHDB"
    USERNAME="CCSSTAGE"
    PASSWORD="CCSSTAGE">
</DB_CONNECTOR>

Create a task

The MDM_RUNJOB_SHELL task is used to execute the MDM validation scripts from a chain.

The XML file name to use for the validation run must be specified in the MDM_RUNJOB_SHELL task, along with the database connection properties and credentials as illustrated below.

Update the ria-boot.properties file

The ria-boot.properties file must specify the following property for the runmdm.sh script to be executable from DOH:

com.ria.converter.shell.scriptDir=<script_directory>

The directory specified here can be set to <DOH>/app/mdatamanager/bin if runmdm.sh is the only script being executed from DOH.

For a more flexible configuration, where additional custom scripts need to be managed separately from the standard mdatamanager installation files, follow these recommendations:

Create a shared script directory. For example, /app/scripts/.
Create a symbolic link to the mdatamanager execution script: ln -s /app/mdatamanager/bin/runmdm.sh /app/scripts/runmdm.sh

Run the Derby database server

The mdatamanager tool requires a Derby in-memory database to be started. Run the Derby server using the following:

<DOH>/app/mdatamanager/bin/startderby.sh

The server starts as a background process using nohup. The Derby log output is written to derby-server.out.

Ensure that the Derby server is running before submitting validation jobs.

Add the task to a chain

The MDM_RUNJOB_SHELL task must be added to a chain to enable execution. It can either be configured as a standalone chain, as shown below, or added to an existing chain to run as part of a migration process or similar workflow.