In SAP Commerce, the seamless exchange of data between your e-commerce store is essential for maintaining a dynamic and efficient online presence. Our comprehensive synchronization and data loading capabilities empower you to connect your Akeneo PIM with your store, ensuring that your product information is consistently up-to-date. This section provides you with a deep dive into the intricacies of synchronization and data loading, enabling you to harness the full potential of SAP Commerce's integration app functionalities.
Connector Performance and scalability
#Understanding Connector Performance
Customers frequently inquire about the metrics and performance of Akeneo Connectors. Unfortunately, gauging performance is a multifaceted endeavor. In general, it's important to note that three primary criteria significantly influence the performance of the connector:
1. Catalog Volume: While catalog size is an obvious consideration, it's not the sole factor at play.
2. Catalog Complexity: Importing 500,000 products can be straightforward when the product data is minimal (comprising just a name, description, and image). However, if the products are intricate, featuring numerous attributes, reference entities, variations, and the like, importing even 2,000 products can become a laborious and time-consuming process.
3. SAP Commerce Limitations: Additionally, SAP Commerce has also its constraints, as previously discussed in the introduction.
Optimizing Connector Performance
To enhance your connector's performance, we recommend the following strategies:
1. Direct Data Mapping: Always prioritize direct data mapping between Akeneo PIM and SAP Commerce. This approach eliminates the need to rely on SAP Commerce for data conversion, thereby boosting system efficiency.
3. Data Filtering: Scrutinize the amount of data to be transferred to SAP Commerce. You may have attributes in Akeneo PIM that are unnecessary for your storefront. Eliminating irrelevant data during synchronization can expedite the import process.
Akeneo connector synchronization feature set
#Synchronization panel
The data loaded will depend of the configuration in the package. Run a structural data import, a full import, or a differential import directly in the package. The import can be scheduled or manually triggered.
Artifact |
|
|---|---|
| 0 | Main configuration parameters: Global configuration and filtering (0.0) , Global artifact (0.1), Global Family artifact (0.2) |
| 1 | Synchronization process: Full (1.1), Delta or differential import (1.2), Structural data import on family (1.3) |
Structural data import on family
1 - Setting up Monitor
In Monitor > Integrations and APIs > Manage Integration Content > All, locate the Global Family Artifact Settings for the Akeneo to SAP Commerce Cloud integration flow. Verify the required Log Level for the synchronization process. By default, the Log Level is set to Info. If detailed monitoring of each step in the integration flow is necessary, adjust the Log Level to Trace.
2 - Import Process Scheduler
In Design > Integration and APIs, navigate back to the integration package artifacts and locate the Family Import Process Scheduler.
3 - Deploy
Click the Actions button for the Family Import Process Scheduler and select Deploy to trigger the deployment.
4 - Monitor message
Navigate to Monitor > Integrations and APIs > Monitor Message Processing > All Artifacts. Locate the message associated with the artifact Global Family Artifact Settings for Akeneo to SAP Commerce Cloud.
5 - Trace
In the Logs tab, if the Trace log level is enabled, you can access the Trace data. This provides a detailed view of the integration flow steps, including message headers, exchange properties, and the payload for each step.
6 - Attachments
Under Attachments, you can view or download a summary of the OData imports. The attachments include details such as the total, created, and failed imports, along with additional information useful for analysis.
Full or Delta import
1 - Setting up Monitor
To set up monitoring, go to Monitor > Integrations and APIs > Manage Integration Content > All and locate the Global Artifact Settings for the Akeneo to SAP Commerce Cloud integration flow. Verify the required Log Level for synchronization. The default level is Info. If you need detailed monitoring of each step in the integration flow, set the Log Level to Trace.
2 - Import Process Scheduler
In Design > Integration and APIs, navigate back to the integration package artifacts and locate the Full Import Process Scheduler (if you are going to run full import) or Delta Import Process Scheduler (if you are going to run delta import).
3 - Deploy
Click on the Actions button for the import process scheduler and trigger Deploy.
4 - Monitor message
Navigate to Monitor > Integrations and APIs > Monitor Message Processing > All Artifacts. Locate the message associated with the artifact Global Artifact Settings for Akeneo to SAP Commerce Cloud.
5 - Trace
Under the Logs tab, if you enabled Trace log level, you should be able to open Trace data which shows the integration flow steps and the message headers, exchange properties, and payload for each step.
6 - Attachments
Under Attachments, you can view or download a summary of the OData imports. The attachments include details such as the total, created, and failed imports, along with additional information useful for analisys.
CPI parameters: test environment and CPI capacity
On testing environment, you can expect issues in synchronization after around 10000 products. The solution would be to pass to the pre-production environment.
Another common parameter to look at when encountering synchronization issue is the CPI capacity. When encountering synchronization limits, please reach out to SAP to check the CPI capacity.