Introduction

Developed by Akeneo, the SFCC B2C Commerce Connector is installed and maintained on the customer's eCommerce platform. It facilitates the exchange of data and streamlines operations between Akeneo and the customer's eCommerce system. Maintenance of the connector is the responsibility of the integrator, primarily performed on the eCommerce platform.

Data Storage

To interact with Akeneo's API, a token must first be retrieved. This token can be reused across all defined jobs, so it is stored in a Custom Object (AkeneoToken) with a single entry. There is no need to clear this Custom Object.

Product media files will be managed within Catalogs using WebDAV.

Each job responsible for converting Akeneo data into Salesforce-compatible XML maintains a history of imported and archived XML files.

Availability

The Akeneo service is generally available with minimal downtime. However, this solution does not include a fallback mechanism. In the event of an extended outage, please contact Akeneo support for assistance.

 Failover and Recovery

There are several potential reasons why the Akeneo SFCC cartridge may fail to function:

1. Network Issues: Connectivity problems between SFCC and the Akeneo PIM.
2. Akeneo PIM Platform Unavailability.
3. Data Issues: Blocking errors in the data received from Akeneo PIM.
4. Configuration Issues: Misconfiguration of the Akeneo SFCC Cartridge.
5. Incorrect SFCC Configuration.

When any of these issues occur, the cartridge will stop synchronizing data between Akeneo PIM and SFCC, and errors will be logged.

During this period, the SFCC "storefront" remains accessible and continues to work normally.

Only SFCC product data is no longer updated.

As soon as the problem is solved, the synchronization can be restarted normally (manually or automatically).

If an import file was being imported and was abruptly stopped, this file is automatically deleted the next time it is imported, and synchronization can be restarted normally.

Enable service communication logs

1. Go to Business Manager Menu > Administration > Operations > Services > AkeneoGetGeneral
2. Tick the checkbox “Communication Log Enabled” if you want API communication to be logged. Repeat the same for AkeneoGetToken

Enable custom info or debug logs

1. Go to Business Manager Menu > Administration > Operations > Custom Log Settings
2. Adjust the log settings by either creating a custom log category with a specific log level or modifying the root log level to Debug or Info. Additionally, ensure that the Info and/or Debug options are selected in the Log Files section. 

Finding the category of the log: 

Akeneo Support

 Akeneo supports the standard, unaltered (vanilla) version of the connector. Refer to the support section for more information.