Commerce Connector Configuration for brX GraphQL Service - Bloomreach Experience - Open Source CMS

Commerce Connector Configuration for brX GraphQL Service

This Bloomreach Experience Manager feature requires a standard or premium license. Please contact Bloomreach for more information.

Introduction

As depicted in the Architecture Overview, GraphQL client applications, such as SPA or Open UI Pickers, should be able to communicate with the brX GraphQL Service.

GraphQL client applications may discover the URL of the brX GraphQL Service through the REST API for Commerce Connector Properties. That is, clients may read the apollo.server.url property of the associated Commerce Connector to find out the URL of the brX GraphQL Service.

In many cases, the GraphQL client applications would have access to only a single Commerce Backend Platform, so it is good enough to configure the apollo.server.url property in the specific Commerce Connector document. However, if you have multiple channels, each of which may have access to a different Commerce Backend Platform, then you should configure the apollo.server.url property in every Commerce Connector document because the property is read per Commerce Connector by applications.

Typical Flow with SPA in the Channel

As described in Configure Commerce Connector, a channel is configured with a specific Commerce Connector to let the SPA interact with the specific Commerce Backend Platform through the brX GraphQL Service. A typical flow looks like this:

  • SPA reads the Channel properties ("$.channel.info.props" in JSONPath format) from the Page Model API response like the following:
    • {
        //...SNIP...
        "channel": {
          "info": {
            "props": {
              "defaultSMConnector": "brsm",
              "defaultConnector": "commercetools",
              "smViewId": "12345",
              //...
            },
            //...
          },
        },
        //...SNIP...
      }
      
  • SPA reads the properties of the Commerce Connector, specified in the "defaultConnector" Channel property, through the REST API for Commerce Connector Properties to find out the URL of brX GraphQL Service.
  • SPA interacts with the brX GraphQL Service to read or update data in the Commerce Backend Platform.

Typical Flow with Open UI Pickers

Using Open UI Pickers, authors or editors select a specific Commerce Connector and associated category, product, product variant or account in the document. A typical flow looks like this:

  • An authors or editor edits a category, product or account detail document in CMS.
  • The user selects a specific Commerce Connector.
  • The user selects a specific category, product, product variant or account from the Commerce Backend Platform through the UI.
    • The Open UI Picker UI discovers the URL of the brX GraphQL Service through the REST API for Commerce Connector Properties.
    • It searches or resolves the resources through the GraphQL API set provided by the brX GraphQL Service.
    • It stores the selection in the document.
  • The user saves, unpublishes, or publishes the document.
Did you find this page helpful?
How could this documentation serve you better?
On this page
    Did you find this page helpful?
    How could this documentation serve you better?