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.

Elastic Path Maven Profiles

Elastic Path Maven Profiles

Maven build profiles are sets of configuration settings for building your software in different environments. For example, if you have tomcat-developer as an active profile, Maven builds your projects according to the tomcat-developer settings, which in this case builds your web applications into a deployable Tomcat WAR.

Elastic Path provides a number of build profiles so you can build and deploy your Elastic Path Commerce platform on different application servers and databases. You can activate or deactivate the build profiles in your Maven settings.xml file that is located in your .m2 directory.

Note: Changing Profiles

If you switch to one of these profiles as you are developing, mysql-dev-db, oracle-dev-db or mssql-dev-db you must update your database with the settings associated with these profiles. To update the database, run the command shown here: ChangingProfiles

Application Server Profiles

The application server profiles are used to configure the type of WAR file generated by Maven. Choose the appropriate profile for your server.

Server Profiles Server


Tomcat 7


Weblogic 11g

Database Profiles

The database server profiles are used to configure the database the Elastic Path platform uses. Choose the appropriate profile for your database system.

Database Profiles Database


MySQL 5.1, 5.5


Oracle 11g r1, 11g r2, 11g r1 RAC, 11g r2 RAC


MSSQL 2008

Specifying your database schema

By default, the database profiles will use the following properties to access your database:






You may override these values by adding the following profile in your settings.xml and inserting your own settings.

    <id>Database Profile</id>
        <epdb.schemaname>Schema Name</epdb.schemaname>
        <epdb.username>Database Username</epdb.username>
        <epdb.password>Database Password</epdb.password>

For MySQL, your settings.xml should look similar to the following:

		<!-- Uncomment one appserver profile -->
		<!-- <activeProfile>jboss-developer</activeProfile> -->
		<!-- <activeProfile>weblogic-developer</activeProfile> -->
		<!-- <activeProfile>websphere-developer</activeProfile> -->
		<!-- Uncomment one DB profile (see grandparent POM for a full list) -->
		<!-- <activeProfile>oracle-dev-db</activeProfile> -->
		<!-- <activeProfile>mssql-dev-db</activeProfile> -->

Other Profiles

In addition to the server and database profiles, there are other profiles that configure Maven for development.

Profile Description


Builds the Commerce Manager Client whenever the core is built.

activemq-dev-jms Activates ActiveMQ JMS, sets the URL, host, and port.