Populating Database using Maven
Ensure that you start ActiveMQ before performing the following steps. However, you can run database migration without ActiveMQ, by using the
-Dspring.profiles.active=non-xa
Maven property. For example, to run reset without ActiveMQ, run the commandmvn clean install - Preset-db -Dspring.profiles.active=non-xa
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:
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
To update an existing database, navigate to the
extensions/database
module and run the following command:mvn clean install -Pupdate-db