Skip to main content

Creating a Commercetools Connection

This recipe explains how you can create a DX Engine Connection to the Commercetools Commerce Engine.

DX Engine Components can use DX Engine Connections to encapsualte the information used to connect to a system that exposes Web services. Components that access Commercetools APIs can use a Commercetools Connection created based on this recipe.

To create the value used for the Authorization HTTP header required by Commercetools, we first need to pass client credentials to the Commercetools authorization endpoint for the appropriate region to obtain an Commercetools API Client token:

The commerceTools.generateToken() function provided by Conscia abstracts this functionality, obtaining the full scope allowed by the client credential and caching that result token.

In the Commercetools Connection, we also need to specify the API endpoint, which includes a region identifier:

Finally, the Connection also needs the Commercetools project ID:

Mapping Out DX Engine Elements​

This recipe involves a DX Engine Connection, which encapsulates the information used to connect to Commercetools, and a DX Engine Secret, which stores the Commercetools client secret.

DX Engine Configuration Details​

We can store the Commercetools client secret in Conscia as a secret. To create the secret, in the Conscia UI:

  1. Click Settings in the top-nav, and then select Secrets.
  2. Click Add Secret
  3. Set Secret Code to a value such as commercetools-secret.
  4. Set Secret Name to a value such as Commercetools Secret.
  5. Set Secret Value to the Commercetool client credential.
  6. Optionally, enter a Description for the secret.
  7. Click Submit.

//TODO: screen shot

To create the Commercetools Connection, in the Conscia UI:

  1. Click Settings in the top-nav, and then select Connections.
  2. Click Add Connection.
  3. Set Connection Code to a value such as commercetools-connection.
  4. Set Connection Name to a value such as Commercetools Connection.
  5. Optionally, enter a Connection Description for the connection.
  6. Select the Universal API Connector.
  7. Click Submit.

//TODO: screen shot

To configure the Commercetools Connection, in the Conscia UI:

  1. Click the Edit button for the Commercetools Connection.
  2. Under Base URL, for Get value from, select Literal.
  3. Set the value of Base URL to the Adyen API base URL, such as https://api.us-central1.gcp.commercetools.com/{commercetools-project-id}, replacing{commercetools-project-id} with the ID of your Commercetools project, and replacing the Commercetools region (us-central1.gcp) as appropriate.
  4. Under Base Headers, click Add another item.
  5. For the new header, set Header to Authorization.
  6. For the new header, set Get value from to JS Expression.
  7. For the new header, set the value to an expression such as the following, replacing {commercetools-project-id} with the ID of your Commercetools project and {commercetools-client} with your Commercetools client ID, and replacing the Commercetools region (us-central1.gcp) as appropriate. :
commerceTools.generateToken(secret('us-central1.gcp', "{commercetools-project-id}", {commercetools-client}, secret('commercetools-secret')).then(token => 'Bearer ' + token)
  1. Click Submit.

//TODO: screen shot

Any DX Engine Component that uses this connection can specify a URL path relative to the value of Base URL and will include the Authentication HTTP header with the value determined by the commerceTools.generateToken() function.

Remember to remove the Commercetools secret from temporary storage if desired.

Note that the same Connection in a test, production, and any other Conscia Environments may use different Base URL and Authentication values than that of the Connection in Preview environment.

References​