Populating Database

Data Set Configuration

The following Elastic Path test and demo data sets are included in the commerce-data module:

• ep-shared-demo-data - shared data used by all data sets
• ep-mobee-demo-data - test and demo data for Cortex stores
• ep-sample-data - test data with descriptive object names
• demo-snapitup-data - legacy data used for performance testing

Configuring Test Data

To change the data sets that are loaded in your local development environment, update the liquibase-context property in the environments/local/data-population.properties file in the extensions/database/ext-data module. Remove data sets that need not to be loaded.

Populate the Database

To populate your local development database for the first time:

• MySQL or Oracle Database:

1. In a terminal window, go to the extensions/activemq-broker module.

2. Run the following command:

   mvn clean tomcat8:run-war
   

3. In a new terminal window, go to the extensions/database module.

4. Run the following command:

   mvn clean install -Preset-db
   

• H2 Database: To help troubleshoot H2-specific SQL dialect issues, enable the non-xa profile.

  mvn clean install -Preset-db -Dspring.profiles.active=non-xa
  

For more information, see the [Data Population](/commerce/docs/8.1.x/tools/data-population/index.html) section in the Data Population Tool documentation.

Configuring the Database Connection Limit

1. Download and install the latest version of MySQL Workbench.

2. Open MySQL Workbench.

3. Connect to your Elastic Path database schema.

4. Execute the following SQL statement in a new Query tab:

   set global max_connections = 300;
   

5. Validate the change with the following SQL statement:

   show variables like "max_connections"