---
schema_version: "1"
id: e70ac899a87c10feaf0597082ed31b9e7f28a4b362bcf5a88d4426a644ff7651
title: Accelerator Setup Guide
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/retail/latest/rcg-setup-guide.md
canonical_url: https://docs.mulesoft.com/retail/latest/rcg-setup-guide
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 475b3d2d52c8562dbdfe7c96df5612460e61ddd8cae5d49af63c1de3a37e48b5
description: MuleSoft Documentation Site
release: "3.2"
latest: true
---
---
product: Retail
version: 3.2
is-latest-version: true
---

# Accelerator Setup Guide

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

This page provides guidance on configuring the various systems and products required to implement
the use cases provided by this solution.

## Service Accounts

Service accounts are needed for the applications below, with the versions used during Accelerator
development noted:

- Salesforce B2C Commerce (Version 20.6, Compatibility Mode 19.10)

- Salesforce Marketing Cloud (April 2021)

- Salesforce (Spring '21)

- SAP (ECC 7.5)

Additional resources used:

- Global Data Management System (GDM) - MariaDB used as GDM

- Order Management System (OMS) - Apache OFBiz used as OMS

- Product Information Management (PIM) - Oracle 11g used as PIM

## Required Configuration

In addition to configuring individual applications to suit your target deployment environment, the
following will be required to implement the use cases described:

- B2C Commerce Configuration: Open Commerce and Salesforce Commerce API access in addition to
  deployment and configuration of the B2C Commerce Sync Cartridge.

- Salesforce Configuration: Addition of custom fields and enabling Person Accounts in addition to
  creating a push topic on Account object with appropriate filters.

- Salesforce Marketing Cloud: A custom Data Extension will need to be created along with an
  Installed Package to make API requests.

- SAP Configuration: Deployment of the custom SAP BAPI code required.

## Optional Configuration

The accelerator includes some additional common components, which can be configured to suit your
needs. These are all optional:

- Configurable properties in the common core library

- Notification APIs for sending error notifications via email, SMS or Slack

- Common scheduler for executing jobs on a schedule

Please refer to the [Accelerators Common Services](https://docs.mulesoft.com/accelerators-home/common-services)
documentation for more details on configuring optional components.

## See Also

- [Prerequisites](https://docs.mulesoft.com/retail/latest/prerequisites)

- [MuleSoft Accelerator for Retail](https://docs.mulesoft.com/retail/latest/)