migVisor Metadata Collector (mMC) is a tool that scans data sources and collects their metadata. At the end of scanning, mMC produces file(s) with scan results. Then, mMC either uploads them to mConsole or saves them locally. Finally, mConsole performs analysis based on these scan results.
Data source is either a database or an application. mMC accesses data sources by the data source configuration.
mMC can be run using a single executable, allowing utilizing either the command-line interface (CLI) or the graphical user interface (GUI):
mMC CLI offers a more straightforward approach. It allows inputting the data source configurations and scanning the data sources immediately.
mMC GUI provides a wider spectrum of data source configuration management capabilities. It allows discovering data sources, testing connectivity before scanning, and archiving data source configurations.
For the scanning operation to succeed, the host running mMC must be able to connect to each one of the sources via the network.
In case the source is a cluster, all members of the cluster must be reachable on their respective ports.
For automatic uploading scan results to mConsole, the host running mMC must have outbound internet access to https://console.migvisor.com/ on TCP port 443. This option is required for using mMC GUI or mMC CLI in Online mode for automatic uploading.
mMC must connect and authenticate to sources or databases in order to execute various commands during a scan. The database access requirements are:
Credentials for a single database user that can be used to log in to all of the source servers.
Permissions given to the database user to run all scan commands for that source type.
For more details and help creating a user with sufficient privileges on the various sources, see https://doc.migvisor.com/mdoc/resources .
The current version of mMC requires Java 17 version. To ensure the uninterruptable start of the application, provide the following configurations:
Install Java 17 on your endpoint.
Define the way to the bin folder of the respected Java version:
Open the folder of the Java 17 version.
Open the bin folder.
Copy the path to the folder.
Open the extracted
At the beginning of the file, replace
path to the folder\java.
Save and close the file.
Command Prompt window must remain open while running mMC.
Do not run more than one instance of mMC at the same time.
mMC has two operation modes:
Online. If you provide valid migVisor credentials before scanning, mMC uploads the scan results directly to mConsole for analysis.
Offline. If you don’t log in to migVisor before scanning, mMC runs in offline mode. Then, mMC saves scan results locally.
mMC is able to scan either single sources or a set of sources set in the configuration file:
Scanning single sources is available both in GUI and CLI modes but it’s more reasonable to use it in the GUI mode. The GUI mode allows filling in the source parameters in a separate window tailored for each source type.
Scanning a set of sources from the configuration file(s) is also available in both modes but it’s more reasonable to use it in the CLI mode. CLI mode allows passing in one command a whole set of configuration files of all supported formats, and the scanning parameters.
mMC connects to sources using the network interfaces or hosts you supply to it.
Supported source types include:
SQL Server - Windows Authentication (optional)
If you run mMC on Windows, you can apply your Windows Authentication credentials to scan SQL Server sources.
To enable Windows Authentication for SQL Server sources connection:
Extract the archive and open the folder sqljdbc_11.2\enu → auth.
mssql-jdbc_auth-11.2.2.x86.dllbased on the architecture of your OS.
Copy the extracted .dll file to
SQL Server - TLS support
Java 1.8 uses TLS 1.2 by default. If your source does not support TLS 1.2, please consider upgrading its TLS version (you can use the following Microsoft KB article for reference).
TLS version 1.2 or above is recommended.
The workaround below should only be exercised upon careful consideration and in accordance with your organization’s security policies.
You can reenable the older TLS version on the host running mMC by removing it from the list of disabled algorithms in Java’s security settings:
Open the file
Locate the entry
Remove the specific named TLS version you want to allow.
Save the file.
For example, if your source only allows TLSv1.1:
jdk.tls.disabledAlgorithms=... TLSv1.1, RC4, DES ...
jdk.tls.disabledAlgorithms=... RC4, DES...