Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Current »

The MettleCI Command Line Interface has a debugging mode which is enabled by inserting entries in a configuration file:

In the root directory of your CLI installation (e.g. /opt/dm/mci/cli UNIX or C:\MettleCI\cli WINDOWS) you will see the file config.properties.

Update the file to contain the following entries:

# Setting the log level for a specific logger takes the format:
#     logger.[LOG_NAME]=[LOG_LEVEL]

logger.com.datamigrators.mettle.process.CommandRunner=DEBUG
logger.com.datamigrators.mettle.dsadmin.commands.DSParamsMergeCommand=DEBUG

These entries will create a log file in a subdirectory of where the CLI command or commands were run from. Typically this will be under your CLI install directory in the sub-directory file log/stdout.log, but it may not be located there if you are not running commands from that location (for example, pipeline agents running CLI commands will rarely be in the CLI directory). In the event of a support request you may be asked to download this file and forwarded it to MettleCI support for analysis.

Available Debug Loggers

Logger

Enhanced Logging Provided

logger.com.datamigrators.mettle.process.CommandRunner

Logs the external calls made to DataStage APIs

logger.com.datamigrators.mettle.dsadmin.commands.DSParamsMergeCommand

Logs details of differences (sections and entries) calculated by the DSParams Merge Command

logger.com.datamigrators.mettle.dsadmin.commands.DSParamsDiffCommand

Logs sections and entries merged by the DSParams Diff Command

NOTE: by default the log subdirectory is created relative to where you are now, that is, relative to the directory the process is in at the time the command is issued… that may or may not be the installation directory.

  • No labels