Announcement: You can find the guides for Commerce 7.5 and later on the new Elastic Path Documentation site. This Developer Center contains the guides for Commerce 6.13.0 through 7.4.1.Visit new site

This version of Elastic Path Commerce is no longer supported or maintained. To upgrade to the latest version, contact your Elastic Path representative.

Populating the Database

Populating the Database

  • Ensure that ActiveMQ is running.
  • Ensure that the following modules in the extension module are built:
    • ext-core
    • ext-importexport
    • ext-data-population
Elastic Path Commerce contains sample data sets that can be used to test and demonstrate commerce functionality. These are located in the commerce-data module.

Schema changes, test data and production configuration data for your project should be added to the following locations in the database/ext-data module:

  • Schema changes - schema/schema-customizations.changelog.xml
  • Production configuration data - data/rel-1.0-data. This configuration data is populated in all environments.
  • Test data - data/test-data.

The data sets that are used to populate each environment are defined in that environment's data-population.properties file by the liquibase.contexts property. The sample data sets can be removed when no longer required.

Note: The liquibase.contexts property must always contain a default context.
Use these Maven commands to populate your local development database:
  1. To populate a new database or to re-populate an existing database, navigate to the extensions/database module and run the following command: 
    mvn clean install -Preset-db
  2. To update an existing database, navigate to the extensions/database module and run the following command: 
    mvn clean install -Pupdate-db