mMC GUI

mMC GUI provides a wide spectrum of data source configuration management capabilities. It allows discovering data sources, testing connectivity before scanning, and archiving data source configurations.

Overview

The mMC Top Navigation bar contains:

• Key navigation pages

• Link to the migVisor Documentation

• [mMC GUI] Scan Preferences

• Indication of an operation mode (online or offline)

In the center of the Top Navigation bar, you can navigate through key mMC tabs:

For Databases and Applications, the Actions panel contains the following buttons for performing actions with the selected sources from the list:

The Footer contains:

• End User License Agreement.
  Press the document icon in the lower-right corner of migVisor EULA to open it locally.

• Versions of query engines.

• Version of mMC.

• Copyright statement.

General Workflow

The general flow of analyzing sources consists of the following stages:

1. Run mMC either in online or offline mode.

2. Add sources manually or import their parameters from the configuration file.

3. Select sources to scan.

4. Test the availability of the selected sources.

5. Scan sources.

Discover

To find out if particular connections to databases exist at all, mMC can be run in the discovery mode.

To run mMC in the discovery mode, select DB engines and set host and port ranges to look through.

After discovering sources, mMC displays them and allows adding them as connections. The discovered data contains only the host and port. So, added connections will be incomplete. To be able to scan these sources, fill in the missing data for the discovered connections.

Test

Testing allows checking if mMC is able to connect to sources. This helps to avoid wasting time trying to scan sources that can’t be connected.

For database data sources, mMC checks if connection details are valid and a database can be connected using the provided credentials.

For application data sources, mMC checks if the application directory exists and the current user has enough permissions to access it.

Scan

Scanning is different for database and application data sources.

For database data sources, mMC runs queries or commands against the source, detecting the type and quantities of detected features, host attributes, configuration, cluster topology, schema objects, schema object types, and other size and usage statistics or metadata.

For application data sources, mMC performs term matching and linguistic analysis, detecting specific terms, syntactic structure, extraction of specific terms, and proper association of the findings to a migVisor defined feature.

For more details about scanning applications, see https://doc.migvisor.com/mdoc/application-migration-and-modernization-complexity.

Once the scanning is finished, mMC either uploads the results to mConsole, or saves them locally to an encrypted file.