All of the functionality exposed in the web-based UI is available in the console mode as well.
Run the OmniLoader executable with an additional -job parameter specifying the path to the JSON file. An example (Windows variant):
By default, the console will copy all the tables from all source databases into the target database. Of course, this behavior can be changed. One can opt to specify a particular list of tables to copy, and these tables can each have their own specific customization parameters applied. More information on this is available in our documentation. If several source databases are used, instead of a single Source element, you should use Sources with an array of items.
ConsoleMode JSON files are easy to understand – and declarative. One can see all the customizations right away, as there is no need to flick through different screens to examine what has been applied.
This is especially valuable in a multi-user environment, where a colleague coming to the project can immediately grasp the requirements.
An additional benefit is that JSON project files can be put into the source control, for security and audit.
Omni Loader can be invoked as a console application to execute a job and return. This is very useful for automated migrations and migrations as part of CI/CD workflows.
A JSON job specification to use. A typical example would be:
Run Omni Loader in a distributed cluster mode. Omni Loader becomes a cluster orchestrator and awaits for agents to connect to it.
Listen for incoming connections. A typical example would be:
In cluster mode, this is a public orchestrator IP:port combination that will be sent to agents when they connect. Agents will send data to the API on specified port.
In console mode and CI/CD workflows, you can activate Omni Loader even without firing up the GUI.
Ready to get started?