Initial Configuration

By following the steps below, you will be able to add OMS functionality to your Broadleaf site .
At the time of writing, these instructions were based on a version of the Heat Clinic sample project targeting Broadleaf version 3.1.0-GA.

Configuration Changes

1. Add the following to the dependency management section of your parent pom.xml:

   <dependency>
       <groupId>com.broadleafcommerce</groupId>
       <artifactId>broadleaf-oms</artifactId>
       <version>${broadleaf-oms.version}</version>
       <type>jar</type>
       <scope>compile</scope>
   </dependency>
   

   Note: You must have previously configured your pom to reference the Broadleaf private repositories. This information will be provided as part of your license agreement.

2. Pull these dependencies into your core/pom.xml:

   <dependency>
       <groupId>com.broadleafcommerce</groupId>
       <artifactId>broadleaf-oms</artifactId>
   </dependency>
   

Schema Changes

If you are allowing hibernate to create and modify your tables, this will be done automatically when you restart with the new configuration settings.

Otherwise, you will need to generate the SQL to customize your Broadleaf implementation. See the Broadleaf Schema Upgrade Documentation for details.

Admin Security Changes

To maintain theme configurations in the Broadleaf admin, you will need to load new permissions. The recommended changes are located in the following files:

/config/bc/sql/load_oms_admin_security.sql
/config/bc/sql/load_oms_reason_codes.sql

Note: In development, you can automatically load this SQL by adding this file to the blPU.hibernate.hbm2ddl.import_files property in the development-shared.properties file.