mMC GUI
migVisor Metadata Collector (mMC) has three tabs:
The mMC global header allows switching between the tabs and contains a link to the migVisor documentation, the cog icon that opens the Scan Preferences window with the general scan settings.
On the Databases and Applications, the Actions panel above the source list contains the following buttons for performing actions with the selected sources from the list:
General Workflow
The general flow of analyzing sources consists of the following stages:
Run mMC either in online or offline mode.
Add sources manually or import their parameters from the configuration file.
Select sources to scan.
Test the availability of the selected sources.
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 a list of them and allows to add 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 to check if mMC is able to connect to sources. This helps to avoid wasting time trying to scan sources that can’t be connected.
For databases, mMC checks if connection details are valid and a database can be connected using provided credentials.
For applications, mMC checks if the application directory exists and the current user has enough permissions to access it.
Scan
Scanning sources is different for databases and applications.
For databases, 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 applications, 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.
mMC run scanning either for databases or for applications. Once scanning is finished, mMC enter uploads results to mConsole, or saves them locally to an encrypted file.