Creating Database in MySQL 5.x
Creating the Database
In the command prompt, open MySQL:
mysql -u root -p
In MySQL, enter the following command to create a database:
create database COMMERCEDB character set utf8;
When starting fresh with Elastic Path 7.5.0, it is recommended you name the database schema
COMMERCEDB. This will make configuring Liquibase simpler, as this has been set as the default.
Enter the following command to create a user that has complete access to
grant all privileges on COMMERCEDB.* to ep@'localhost' identified by 'ep';
ep/epis the default username/password combination used by Elastic Path.
Table Name Case Sensitivity
On Unix systems, table names in SQL (Structured Query Language) queries may be case sensitive. To turn off case sensitivity, refer to the MySQL reference manual. Most cases this means adding the line
lower_case_table_names under the section
Setting Transaction Isolation Level
This setting is available as of version
You must change the transaction isolation level of MySQL database from the current default setting
READ_COMMITTED to avoid optimistic locks.
To change the level, add
transaction_isolation=READ-COMMITTED line under the section
[mysqld] in the
/etc/mysql/my.cnf file and restart the database server.
Creating the Database in Oracle 11g
Creating a Database User Account
In Oracle databases, a database schema is mapped to a user account, so we only need to create a user account for the Elastic Path system.
Start the SQL*Plus database client by entering the following command:
Connect to the database as the
conn / as sysdba
In SQL*Plus, create a database user account.
create user COMMERCEDB identified by ep;
When starting fresh with Elastic Path 7.5.0, it is recommended you use the name/password combination of
COMMERCEDB/ep. This will make configuring Liquibase simpler, as this has been set as the default.
Grant the user appropriate permissions.
grant connect, resource, dba to COMMERCEDB;
Exit SQL*Plus by running:
Creating the Database in Oracle 12c
Creating a Pluggable Database
New in Oracle 12c is the concept of pluggable databases. We will create one along with a user account for the Elastic Path system.
Open the DBCA Utility:
cd $ORACLE_HOME/bin && ./dbca
Delete the default
- Select "Delete Database" and click "Next"
orcldatabase (if not already selected) and click "Next"
- Skip "Management Options" by clicking "Next", and then finally, click "Finish"
Re-create the database
orcland specify a pluggable database name of
Rerun the DBCA Utility
Select "Create Database" and click "Next"
Fill in the following fields and use the default values for other fields not specified:
Property Value Global Database Name
Create as Container Database Checked ON Pluggable Database Name
Click "Next" and then "Finish"
You can connect to the pluggable db, eppdb, by it’s service name
eppdband using a slash in the URL like:
Pushing Database Changes
Elastic Path recommends using the Data Population Command Line Interface (CLI) to push schema changes and catalog data updates to the production database. This tool is built in the
The deployment package created by the
extensions/packager/ext-deployment-package project contains the Data Population CLI as well as all the Liquibase change sets and the Import/Export data sets needed for deployment. For each target database, the following configuration files are required:
|Defines database connection properties and the data population environment name itself for this environment.|
|Defines properties required by the Data Population tool for execution in this environment; e.g. Liquibase contexts to activate for this environment.|
|Defines the values used when overriding property placeholders in data files for this environment.|