Skip to main content
Skip table of contents

Command Constructor

mMC command is made of the following parts:

  • Command name

  • Scanning options

  • Data source type

  • Data source configuration

Each step guides through one part of the command. Only the result command presented in the final step is sufficient for running mMC for scanning.

Step 1. Launch mMC

In the command line, set the mMC location as a working directory. From there, launch mMC by running mmc-cli:

Linux
CODE
mmc-cli.sh ...
Windows
CODE
mmc-cli.bat ...

Step 2. Set Scanning Options

Configure the scanning process and the output using scanning options.

First of all, to log into migVisor provide the username (-u/--username). Setting the username is required.

By default, mMC runs in online mode and uploads the scan results directly to mConsole. To save scan results to an encrypted ZIP file locally and run mMC in offline mode, use the -l/--local option.

The query definition files are downloaded together with mMC and stored in the mMC directory. By default, mMC uses these query definition files and updates them automatically. To use other query definition files, use the -q/--query-file option and specify path(s) to file(s).

The default maximum number of threads to use for parallel execution of queries is 4. To override it, use the -t/--threads option.

The default query timeout is 4 minutes. To override it, use the --qt/--query-timeout option.

For example, the command for saving scan results to an encrypted ZIP file locally, using the older query definition files saved locally, with a maximum of 10 parallel threads and the 30-minute query timeout, begins with:

Linux
CODE
mmc-cli.sh -u migVisor_user -l -q /usr/temp/query_oracle.dat -t 10 --qt 30 ...
Windows
CODE
mmc-cli.bat -u migVisor_user -l -q D:/usr/temp/query_oracle.dat -t 10 --qt 30 ...

Step 3. Define Source Type

Enter the source keyword and the source type (database or application):

  • If a single database is being scanned, enter its DB engine name:

    • db2luw

    • hbase

    • mongodb

    • mysql

    • oracle

    • postgresql

    • sqlserver

  • If a single application is being scanned, enter its primary language:

    • java

    • csharp

  • If data source configuration(s) is(are) set in configuration file(s), enter the conf keyword.

For example, the command for scanning a single Oracle database begins with:

Linux
CODE
mmc-cli.sh -u migVisor_user -l -q /usr/temp/query_oracle.dat -t 10 --qt 30 source database oracle...
Windows
CODE
mmc-cli.bat -u migVisor_user -l -q D:/usr/temp/query_oracle.dat -t 10 --qt 30 source database oracle...

Or, for scanning multiple applications, the command begins with:

Linux
CODE
mmc-cli.sh -u migVisor_user -l source application conf ...
Windows
CODE
mmc-cli.bat -u migVisor_user -l source application conf ...

Step 4. Add Source(s)

To scan a single data source, specify the data source configuration using the arguments listed on migVisor Metadata Collector (mMC).

To scan data source(s) using configuration file(s), enter the configuration file location(s).

For example, for scanning a single Oracle database, execute:

Linux
CODE
mmc-cli.sh -u migVisor_user -l -q /usr/temp/query_oracle.dat -t 10 --qt 30 source database oracle localhost 5432 --db-user myusername --service servicename
Windows
CODE
mmc-cli.bat -u migVisor_user -l -q D:/usr/temp/query_oracle.dat -t 10 --qt 30 source database oracle localhost 5432 --db-user myusername --service servicename

Or, for scanning multiple applications, execute:

Linux
CODE
mmc-cli.sh -u migVisor_user -l source application conf /usr/temp/config.csv
Windows
CODE
mmc-cli.bat -u migVisor_user -l source application conf D:/usr/temp/config.csv
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.