Configure Bloomreach Commerce Accelerator
Info: Bloomreach Commerce Accelerator requires a standard or premium Bloomreach Content license. Contact Bloomreach for details.
Overview
Bloomreach Commerce Accelerator enables integration with commerce backends and supports customization through configuration.
Accelerator Configuration File
Bloomreach Commerce Accelerator loads its commerce-specific configuration from the braccelerator.properties file. By default, this uses the "Advanced Configuration for HST Container" method described in the HST-2 Container Configuration documentation.
The default distribution includes conf/platform.xml and conf/hst.xml, each referencing the braccelerator.properties file as shown below:
<?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 approach centralizes commerce-specific configuration and avoids duplication across multiple files.
The braccelerator.properties file is not included by default. To configure the accelerator, copy the example properties from conf/example-braccelerator.properties and update them for your specific commerce backend platform.
For instructions on deploying a distribution artifact with a configuration file in Bloomreach Cloud, refer to Set Environment Configuration Properties.
Use Provided Commerce Backend Configurations
Bloomreach Commerce Accelerator offers predefined configurations for several commerce backends. To use a supported backend, specify the required connection properties in the Accelerator Configuration File. Each backend's documentation provides details on the necessary configuration.
Bloomreach continues to expand support for additional commerce backends.
Configure a Custom Commerce Backend
To integrate a commerce backend that is not preconfigured, you need the following components:
- Commerce Connector Module
A software module that provides configuration and implements the interfaces defined in the Commerce Connector SDK for your specific backend. - Commerce Connector Configuration
Configuration maintained in a Connector Set document within the CMS, containing metadata required to access the backend's services. - CRISP Resource (if required by the connector)
A Spring bean configuration stored as a module configuration in the content repository, specifying the backend service's connection properties.
If you need assistance configuring your commerce backend or want updates on planned backend integrations, contact Bloomreach.