The Bloomreach Discovery commercetools connector was created by Orium, and provides the following features:
- Ability to automatically synchronize all products from commercetools to Bloomreach Discovery through a scheduled task
This connector syncs commercetools data with both Bloomreach Discovery.
Once per day your commercetools products will be synchronized with Bloomreach Discovery.
- commercetools Account
- commercetools API keys (“Admin client”)
- Bloomreach Discovery Account
The account info looks like this:
smAccountId 7340
smAuthKey ojvyt91lkrmzy1rn
smDomainKey sandbox_orium
DataConnect API Key (staging) sandbox_orium-r5361234-ab73-4307-y47d-496369911853
DataConnect API Key (prod) sandbox_orium-r5361234-ab73-4307-y47d-496369911853
In order to install the connector in your commercetools project, you'll need to deploy it. Refer to the commercetools connect deployment documentation.
Setup the required environment variables when you create the deployment:
CTP_CLIENT_IDCTP_CLIENT_SECRETCTP_PROJECT_KEYCTP_SCOPECTP_REGIONBLOOMREACH_DISCOVERY_ACCOUNT_IDBLOOMREACH_DISCOVERY_AUTH_KEYBLOOMREACH_DISCOVERY_DOMAIN_KEYBLOOMREACH_DISCOVERY_API_KEYBLOOMREACH_DISCOVERY_CATALOG_LOCALE
Here you have an example for deployment creation: docs/03-create-deployment.md
In order to uninstall the connector, you’ll need to send the appropriate HTTP request and delete it.
- The connector runs every day at 00:00 UTC, so the products will be synced once per day. If you have just installed the connector, you'll need to wait until the next scheduled job at 00:00 UTC for the products to be synced.
- We map the commercetools products data into Bloomreach in
src/services/bloomreach-discovery-catalog-ingestion.ts.
- By default, commercetools has built-in i18n support. In order to consume the catalog data, we must specify the desired
LocalizedString.
- When deploying a connector you'll be asked to define a "deployment key". This connector also needs the deployment key to be defined as an env variable to work properly.