The import GUI is an add-on for the Pacemaker Professional Edition (PE) and Pacemaker Enterprise Edition (EE).
It enables shop owners or other people that work in the Magento backend to upload import files, e.g. in CSV format, creates the .ok file and start the import process.
It can exclusively be done by one of the Pipelines provided by the Pacemaker Enterprise Edition (EE).
Configure the GUI
The configuration value for
Commandline should be set to the Pacemaker CLI that has to be used to create the
.ok file that is necessary to start the import.
By default, this value should be set to
As a pipeline should it be used to import the files, the configuration value for
Working Directory has to be the
same as for the Pacemaker
, but without the leading
The configuration for
Enable CRON must be set to
No because this will probably use the default
Magento CRON to start the import and passing by the appropriate pipeline.
In general, the GUI will provide the functionality to upload CSV files and adjust the settings for the
import process itself, e.g. the mode that has to be used like
Depending on the GUI configuration and the used Pacemaker edition, the uploaded files will be imported directly or via one of the pipelines.
Keep in mind, that in combination with Pacemaker Enterprise Edition (EE) and the configuration described above, the upload GUI can only be used to upload files.
It is not possible to configure the import itself, as this will be done by the pipeline configuration that finally runs the import. Therefore, the configuration will have no impact.
Via the drop-down
Entities, the pipeline that matches the uploaded files must be selected.
If the pipeline does not match the filename, an error will be triggered.
In case the
Product pipeline has been chosen, the additional drop-down
Import Mode will be rendered.
Default import mode imports all the data that is available in the file, notwithstanding the data has
changed since the last import or not.
In contrast to this, The import mode
Change-Set Detection will compare the data (using so-called and configurable changesets)
from the database with the one found in the import files and only updates the DB if the data has been changed.
They can improve performance massively in
add-update mode, as invoking DB CRUD steps are highly expensive
in terms of performance.
It should be considered well also to activate the cache warming functionality, because this can additionally have a significant impact on performance because all the data to be compared to, will be loaded during the bootstrap process in a very efficient manner.
step provides the possibility to select the import mode. Read more about this topic in
the official Pacemaker Community Edition (CE)
The checkboxes for
Debug Mode, and
Single Transaction can activate the
To get more information about these flags' functionality, you can also look at the the official Pacemaker Community Edition (CE) Getting Started .
Cache Enabled enables the caching functionality.
In general, caching during the import is not very helpful because the main impact on the performance will have the CRUD steps that can not be cached.
In case the import is processed over a network, e.g. in the cloud, it can be helpful to lower the time necessary to load the data from the DB.
Additionally, the cache warming functionality will only work if the cache will be enabled.
Log Level defines the log level that has to be used.
By default, this is set to
warning, but can be changed to the given requirements.
The log file named
system.log will be found the directory with the import artifacts or in the archived artifact,
if the appropriate checkbox has been set.