The Self Managed Commerce Data Population tool is used to either create a new Commerce database or to update an existing Commerce database. For more information about the tool, see Data Population Overview.
The Data Population tool is run as a job; it starts, performs the required work and runs to completion then exits.
data-pop-tool container image must be built and available. For information on building container images, see Building Container Images.
The key configuration options for this job are:
- Specify which command to run using the environment variable
update-dbcommand will determine and apply only the delta of changes, while the
reset-dbcommand will start from a clean database and apply all of the changes. The
reset-dbcommand is destructive and will first erase the database and any data contained within.
- Which data-set to apply to a given database, as specified by environment variable
EP_COMMERCE_ENVNAME. The valid options are the names of the folders under
extensions/database/ext-data/src/main/resources/environmentsin your team's
ep-commerceGit project. Your Commerce development team can confirm the correct value to use.
- The database to apply the changes to, as specified by the environment variables named like
- Whether files from a separate, secure encrypted Git repository should be applied, as specified by optional environment variables named like ``EP_COMMERCE_CONFIG_*`.
Scaling and Replicas
The tool is run as a job and not as a service. To avoid possible data conflicts and corruption, ensure that only one instance of the container is run against a given Commerce database at a given time.
The tool is configured using container environment variables. Some environment variables must be set and some are optional. The environment variables are read and consumed by the container entrypoint script.
For a list of the supported environment variables, see the README file for your release of the containerization tools. The README for the latest release is available here.