Table of Contents

Search

  1. Introduction
  2. Samples and Examples
  3. Tools and Utilities
  4. SDK Resources

Configuring the Script Files

Configuring the Script Files

To set up the script files, you must update the runtime environment variables.
For Windows, use the
mdm_exec_batch_proc_env.cmd
script file to drive the main script file
mdm_exec_batch_proc.cmd
. For UNIX, use the
mdm_exec_batch_proc_env.sh
script file to drive the main script file
mdm_exec_batch_proc.sh
.
The following table lists the runtime environment variables that the script files use:
Environment Variable
Description
Comments and Notes
MDM_SCRIPTS_HOME
Specifies the location of the Resource Kit installation directory.
Adjust to directory of the installation.
MDM_SCRIPTS_DIR
Specifies the location of the
scripts
directory.
Defaults to "
${MDM_SCRIPTS_HOME}/scripts
" , the subdirectory of the installation directory.
MDM_CONNECT_PROPS_DIR
Specifies the location of the
SiperianConnection.properties
file in the
scripts
directory.
Defaults to "
${MDM_SCRIPTS_HOME}/scripts
" , in the
scripts
directory.
MDM_ENV_SCRIPT
Specifies the location and name of the
mdm_exec_batch_proc_env.sh
file for UNIX and
mdm_exec_batch_proc_env.cmd
file for Windows.
MDM_LOGFILE_DIR
The log file directory.
MDM_LOGFILE_RETN_DAYS
Specifies the number of days to retain the log files, before you delete them.
You must delete the log files that are older than the specified number of days. To disable log file deletion, set to
0
.
MDM_EXECUTE_BATCH_CLASS
The MDMExecuteBatch Java class.
Set the MDMExecuteBatch Java class to
com.informatica.mdm.tools.MDMExecuteBatch
.
PATH
PATH
contains the Java bin directory.
Place where you can find the Java bin directory.
CLASSPATH
Must point to the location of the
MDMExecuteBatch.jar
and dependent JAR files.
If dependent JAR files are in other directories, you must include them in the
CLASSPATH
.
Dependent JAR files include the following files:
  • siperianapi.jar
  • siperian-common.jar
  • log4j.jar
  • application server client JAR
MDM_USERNAME
Specifies the registered MDM Hub user name.
Assign the
MDM_USERNAME
to the ORS with read and write privileges for batch data execution.
MDM_PASSWORD
Specifies the MDM Hub encrypted password.
You can get the encrypted password using the
get_encr_pwd
script.
MDM_PREFERRED_RETCODE
The preferred MDM Hub job execution return code,
JOB_RUN_STATUS
or
JOB_RUN_RETURN_CODE
.
If the value or environment variable is missing or mis-spelled, the default return code is
JOB_RUN_STATUS
.
In MDM Hub version 9.7.1 HotFix 1 or later, both
JOB_RUN_RETURN_CODE
and
JOB_RUN_STATUS
contain the same values as returned by ExecuteBatch APIs.
In earlier versions of MDM Hub 9.7.1, the
JOB_RUN_STATUS
and
JOB_RUN_RETURN_CODE
were inconsistent, and the
JOB_RUN_RETURN_CODE
is the preferred value to use.
The environment variable returns one of the following return code values:
  • 0 indicates the successful completion of MDM Hub job with no warnings.
  • 1 indicates the completion of MDM Hub job with warnings.
    Generates the following warning messages:
    • Completed with rejected records.
    • No action.
    • Records failed to load.
  • Greater than 1 indicates complete job failure.
MDM_CONNECTION_PROPERTIES
Specifies the environment variable used to pass the
-mdmconnectionproperties <values>
into MDMExecuteBatch class.
Specifies the path and location of the
SiperianConnection.properties
file.
Ensure that you review and change the following environment variables:
MDM_SCRIPTS_HOME
,
MDM_USERNAME
,
MDM_PASSWORD
,
MDM_CONNECT_PROPS_DIR
,
PATH
,
CLASSPATH
, and
MDM_PREFERRED_RETCODE
.

0 COMMENTS

We’d like to hear from you!