۶Ƶ

Commerce Services Connector

Some ۶Ƶ Commerce and Magento Open Source features are powered by Commerce Services and deployed as SaaS (software as a service). To use these services, you must connect your Commerce instance using production and sandbox API keys, and specify the data space in the configuration. You only need to configure the connection one time for each instance.

Available services availableservices

The following lists the Commerce features you can access through the Commerce Services Connector:

Service
Availability
Product Recommendations powered by ۶Ƶ Sensei
۶Ƶ Commerce
Live Search powered by ۶Ƶ Sensei
۶Ƶ Commerce
Payment Services
۶Ƶ Commerce and Magento Open Source
Site-Wide Analysis Tool
۶Ƶ Commerce
Catalog Service
۶Ƶ Commerce
Data Connection
۶Ƶ Commerce

Architecture

At a high level, the Commerce Services Connector is made up of the following core elements:

Commerce Services Connector Architecture

The following sections discuss each of these elements in more detail.

Credentials apikey

The production and sandbox API keys are generated from the Commerce account of the license owner. The Commerce account is identified by a unique Commerce ID (MageID). The license owner for the merchant’s organization can generate API keys for services like Product Recommendations or Live Search, as long as the account is in good standing.

The keys can be shared on a “need-to-know” basis with the systems integrator or development team that manages projects and environments on behalf of the license holder. Developers who have been granted Shared Access by the license owner cannot generate the keys on their behalf even if the merchant’s organization is present in the Switch Accounts dropdown on their account.

Additionally, solution integrators are also entitled to use Commerce Services. If you are a solution integrator, the signer of the Commerce partner contract should generate the API keys.

NOTE
The key identifiers Production and Sandbox do not refer to your environment. You use the same set of API keys to for each of your environments, for example local, development, Staging, or Production environments.
The license owner is typically the Primary Contact on the ۶Ƶ Commerce account and is not always the same as the Project Owner of the ۶Ƶ Commerce on cloud infrastructure project.

Generate the production and sandbox API keys genapikey

  1. Log in to your Commerce account at .

  2. Under the Magento tab, select API Portal on the sidebar.

  3. From the Environment menu, select Production or Sandbox.

  4. Enter a name in the API Keys section, and click Add New to open the dialog to download the new key.

    Download private key

    note warning
    WARNING
    This dialog provides the only opportunity that you have to copy or download your keys.
  5. Click Download then click Cancel.

  6. Repeat the above steps for each environment (production and sandbox).

    The API Keys section now displays your API (Public) keys. You need all four keys (both the production and sandbox keys, Public+Private) when you select or create a SaaS project in any of the environments/installations associated with the license.

SaaS configuration saasenv

Commerce instances must be configured with a SaaS project and a SaaS data space so that Commerce Services can send data to the right location. A SaaS project groups all SaaS data spaces. The SaaS data spaces are used to collect and store data that enables Commerce Services to work. Some of this data may be exported from the Commerce instance and some may be collected from shopper behavior on the storefront. That data is then persisted to secure cloud storage.

For Product Recommendations, the SaaS data space contains catalog and behavioral data. You can point a Commerce instance to a SaaS data space by selecting it in the Commerce configuration.

WARNING
Use your production SaaS data space only on your production Commerce installation to avoid data collisions. Otherwise, you risk polluting your production site data with testing data, which causes deployment delays. For example, your production product data could be mistakenly overwritten from staging data, such as staging URLs.
If this should happen, submit a Support request to request data cleanup.

SaaS data space provisioning

All ۶Ƶ Commerce merchants can access one production data space and two testing data spaces per SaaS project.

You can use the testing data spaces in any non-production environment as long as you don’t use the same data space in multiple environments at the same time. To use the test data space in a different environment, perform a data cleanup before you select and configure the data space in that environment.

For ۶Ƶ Commerce Cloud Pro projects with multiple staging environments, you can request additional testing data spaces for each staging environment by submitting a Support request. However, if you only have one staging environment and require additional testing data spaces, you have the following options:

  • Contact the Customer Success team or your appointed Customer Success Manager to request an additional Staging environment. There is an additional cost involved.
  • Submit a Support request for an additional testing data space and indicate the business justification for the extra dataspace. This request is subject to approval.

Select or create a SaaS project createsaasenv

To select or create a SaaS project, request the Commerce API key from the Commerce license owner for your store:

NOTE
If you do not see the Commerce Services Connector section in the Commerce configuration, you must install the Commerce modules for your desired Commerce service.
  1. On the Admin sidebar, go to System > Services > Commerce Services Connector.

    If you do not see the Commerce Services Connector section in the Commerce configuration, install the Commerce modules for your desired Commerce service. Also, make sure that the magento/module-services-id package is installed.

  2. In the Sandbox API Keys and Production API Keys sections, paste your key values.

    • Private keys must include ----BEGIN PRIVATE KEY--- at the beginning of the key and ----END PRIVATE KEY---- at the end of the key.
    • If you do not have a copy of the actual keys, ask the Account Owner for them, then plug the values into the configuration.
    note warning
    WARNING
    If you add key values by querying a database backup or snapshot and pasting the values into the configuration, an additional layer of encryption is applied, and the keys will not work.
  3. Click Save.

Any SaaS projects that are associated with your keys appear in the Project field in the SaaS Identifier section.

  1. If no SaaS projects exist, click Create Project. Then in the Project field, enter a name for your SaaS project.
NOTE
To avoid confusion, do not use a specific Commerce Service as the name for your project, for example Live Search, Product Recommendations, or Data Connection. Unless your license has been provisioned for multiple SaaS projects, you can use the same SaaS project for multiple services.
  1. Select the Data Space to use for the current configuration of your Commerce store.
NOTE
If you have separate instances to integrate with Commerce Services, submit a Support ticket to request a new SaaS project for each additional instance. After support has created the SaaS project, configure the Commerce Services integration for the instance using the same API key and selecting the new SaaS project for the data space.
WARNING
If you generate new keys in the API Portal section of My Account, immediately update the API keys in the Admin configuration. If you generate new keys and do not update them in the Admin, your SaaS extensions no longer work and you lose valuable data.

To change the names of your SaaS project or data space, click Rename next to either one. Changing the name does not affect your service because the name is only a label to help you identify and differentiate between projects and data spaces.

IMS Organization (optional) organizationid

To connect your ۶Ƶ Commerce instance to the ۶Ƶ Experience Platform, sign in to your ۶Ƶ account using your ۶Ƶ ID. After you sign in, the IMS organization associated with your ۶Ƶ account is displayed in this section.

SaaS data export

When your Commerce instance successfully connects to Commerce Services, the SaaS data export process exports Commerce data from your Commerce server to Commerce SaaS Services so it can be synchronized to connected Commerce Services. In the Admin, you can check synchronization status using the Data Management dashboard. For details, see the SaaS Data Export Guide.

recommendation-more-help
3d5a1200-3287-4b90-a075-6c594f65d80e