Configure Bloomreach Commerce Accelerator

Introduction

Bloomreach Commerce Accelerator allows the integration of commerce backends and the customization of behaviors through configuration.

Bloomreach Accelerator Configuration File

Bloomreach Commerce Accelerator reads its commerce-specific configurations from the braccelerator.properties file by default, using the "Advanced Configuration for HST Container" option described in HST-2 Container Configuration page. That is, it is shipped with the default conf/platform.xml and conf/hst.xml, each of which includes the braccelerator.properties file, like the following example:

<?xml version="1.0" ?>
<!--
  Aggregated Platform/HST Container configuration XML for Bloomreach Accelerator.
  This XML file is loaded before either platform.properties or hst.properties.
-->
<configuration>
  <system/>
  <!-- assuming you deploy the distribution with an uploaded configuration file which is to be renamed to 'braccelerator.properties'. -->
  <properties fileName="${brc.appconfigfiles}" />
  <!-- brc.appconfigpath will be supported for better control in the future (ref: https://documentation.bloomreach.com/bloomreach-cloud/reference-documentation/set-environment-configuration-properties.html). -->
  <!--
  <properties fileName="${brc.appconfigpath}/braccelerator.properties" />
  -->
  <!-- Or you may load it from somewhere else if not deployed on Bloomreach Cloud env: -->
  <!--
  <properties fileName="${catalina.base}/conf/braccelerator.properties" />
  -->
</configuration>

This prevents from duplicating configurations in multiple files by including the shared commerce-specific configuration file.

For details on how to deploy a distribution artifacts with a configuration file in Bloomreach Cloud, see the Set Environment Configuration Properties page.

Use Available Commerce Backend Configurations

Bloomreach Commerce Accelerator includes out-of-the-box configurations for a growing number commerce backends. Using the provided commerce backends only requires specifying the physical connection properties in the Bloomreach Accelerator Configuration File, as described on each configuration's documentation page linked from Available Commerce Backend Configurations.

The goal is for Bloomreach Commerce Accelerator to eventually provide configurations for all popular commerce backends.

Configure a Different Commerce Backend

To integrate a different commerce backend, you need the following:

• Commerce Connector Module
  Software module package, providing configurations and implementations of interfaces defined in Commere Connector SDK for a specific Commerce Backend Platform.
• Commerce Connector Configuration
  Maintained in a Connector Set document in the CMS application and containing metadata to access commerce backend's services.
• CRISP Resource (if the Commerce Connector Module uses CRISP API)
  Spring bean configuration stored inside a module configuration in the content repostory, configuring the commerce backend service physcial connection properties.

Contact Bloomreach if you require assistence configuring your commerce backend or if you want to stay up to date on which backend configurations are planned to be added to Bloomreach Commerce Accelerator.