---
schema_version: "1"
id: 34263e529433d06e5d8681ab8c094775ec820cd8eb528d2a49bbeb962485c191
title: Using Anypoint Studio to Configure Commerce Cloud B2C Shop Connector 2.1
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/commerce-cloud-shop-api-connector/latest/shop-api-connector-studio.md
canonical_url: https://docs.mulesoft.com/commerce-cloud-shop-api-connector/latest/shop-api-connector-studio
source_site: docs.mulesoft.com
content_type: documentation
content_hash: fbff188182d14095f1cfd6efa78524b1a401d0f718f1e4d27cd7b38458429666
description: MuleSoft Documentation Site
release: "2.1"
latest: true
---
---
product: Salesforce Commerce Cloud B2C Shop API Connector
version: 2.1
is-latest-version: true
---

# Using Anypoint Studio to Configure Commerce Cloud B2C Shop Connector 2.1

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Anypoint Studio (Studio) editors help you design and update your Mule applications, properties, and
configuration files.

To add and configure a connector in Studio:

1.  [Create a Mule project](#create-mule-project).

2.  [Add the connector to your Mule project](#add-connector-to-project).

3.  [Configure an input source for the connector’s flow](#configure-input-source).

4.  [Add a connector operation to the flow](#add-connector-operation).

5.  [Configure a global element for the connector](#configure-global-element).

6.  [Configure the other connector fields](#configure-other-fields).

When you run the connector, you can view the app log to check for problems, as described in
[View the App Log](#view-app-log).

If you are new to configuring connectors in Studio, see
[Using Anypoint Studio to Configure a Connector](https://docs.mulesoft.com/connectors/introduction/intro-config-use-studio).
If, after reading this topic, you need additional information about the connector fields, see the
[Commerce Cloud B2C Shop Connector Reference](https://docs.mulesoft.com/commerce-cloud-shop-api-connector/latest/shop-api-connector-reference).

## Before You Begin

To avoid dependency errors, update your Maven `settings.xml` file if needed. See
[Maven Reference](https://docs.mulesoft.com/mule-runtime/latest/maven-reference) for more information (Ignore if already
done).

## Create a Mule Project

In Studio, create a new Mule project in which to add and configure the connector:

1.  In Studio, select **File > New > Mule Project**.

2.  Enter a name for your Mule project and click **Finish**.

## Add the Connector to Your Mule Project

Add Anypoint Connector for Salesforce Commerce Cloud B2C Shop APIs (B2C Shop Connector) to your Mule
project to automatically populate the XML code with the connector’s namespace and schema location
and add the required dependencies to the project’s `pom.xml` file:

1.  In the **Mule Palette** view, click **(X) Search in Exchange**.

2.  In **Add Modules to Project**, type `commerce cloud b2c shop` in the search field.

3.  Click Commerce Cloud B2C Shop Connector in **Available modules**.

4.  Click **Add**.

5.  Click **Finish**.

Adding a connector to a Mule project in Studio does not make that connector available to other
projects in your Studio workspace.

## Configure a Source

A source initiates a flow when a specified condition is met. You can configure one of these sources
to use with Commerce Cloud B2C Shop Connector:

- **HTTP > Listener**  
  Initiates a flow each time it receives a request on the configured host and port

- **Scheduler**  
  Initiates a flow when a time-based condition is met

For example, to configure an HTTP listener, follow these steps:

1.  In the **Mule Palette** view, select **HTTP > Listener**.

2.  Drag **Listener** to the Studio canvas.

3.  On the **Listener** configuration screen, optionally change the value of the **Display Name**
    field.

4.  Specify a value for the **Path** field.

5.  Click the plus sign (**+**) next to the **Connector configuration** field to configure a global
    element that can be used by all instances of HTTP **Listener** in the app.

6.  On the **General** tab, specify connection information for the connector.

7.  On the **TLS** tab, optionally specify the TLS information for the connector. For TLS
    configuration information, see [TLS Configuration](https://docs.mulesoft.com/mule-runtime/latest/tls-configuration).

8.  On the **Advanced** tab, optionally specify reconnection information, including a reconnection
    strategy. For Reconnection strategy details, see
    [Reconnection Strategies](https://docs.mulesoft.com/mule-runtime/latest/reconnection-strategy-about).

9.  Click **Test Connection** to confirm that Mule can connect with the specified server.

10. Click **OK**.

## Add a Connector Operation to the Flow

When you add a connector operation to your flow, you immediately define a specific operation for
that connector to perform.

To add an operation for B2C Shop Connector, follow these steps:

1.  In the **Mule Palette** view, select **Commerce Cloud B2C Shop Connector** and then select the
    desired operation.

2.  Drag the operation onto the Studio canvas to the right of the input source.

    ![Example of operation dragged to flow](/mulesoft/current/en-us/commerce-cloud-shop-api-connector/latest/_images/shop-connector-add-operation-to-flow.png)

## Configure a Global Element for the Connector

When you configure a connector, it’s best to configure a global element that all instances of that
connector in the app can use. Configuring a global element requires you to provide the
authentication credentials that the connector requires to access the target Commerce Cloud B2C Shop
Connector system. Commerce Cloud B2C Shop Connector supports two different types of connection
provider:

1.  Customer Auth Connection Provider

2.  OAuth2 Application Connection Provider

To configure the global element for Commerce Cloud B2C Shop Connector, follow these steps:

1.  Select the name of the connector in the Studio canvas.

2.  In the configuration screen for the operation, click the plus sign (**+**) next to the
    **Connector configuration** field to access the global element configuration fields.

3.  On the **General** tab, configure the connection:

    - [Customer Auth Connection Provider](#ShopConfiguration_CustomersAuth)

    - [OAuth2 Application Connection Provider](#ShopConfiguration_Oauth2Application)

Use OAuth 2.0 to delegate user authentication to the service hosting the user account. For more
information, refer to
[Configuring OAuth 2.0 for Connectors](https://docs.mulesoft.com/connectors/introduction/intro-config-oauth2),
[Configuring OAuth 2.0 for Connectors on CloudHub](https://docs.mulesoft.com/connectors/introduction/intro-config-oauth2-cloudhub),
or [OAuth Support in the SDK](https://docs.mulesoft.com/mule-sdk/latest/oauth).

\+ You can reference a configuration file that contains ANT-style property placeholders
(recommended), or you can enter your authorization credentials in the global configuration
properties. For information about the benefits of using property placeholders and how to configure
them, see
[Anypoint Connector Configuration](https://docs.mulesoft.com/connectors/introduction/intro-connector-configuration-overview).

\+ . On the **Advanced** tab, optionally specify reconnection information, including a reconnection
strategy.

1.  Click **Test Connection** to confirm that Mule can connect with the specified server.

2.  Click **OK**.

### Get the Shopper JWT Token

To get the Shopper JWT Token to use for the
[**Commerce Cloud B2C Shop Connector Customer Auth Config**](#ShopConfiguration_CustomersAuth):

1.  On the **General** tab of the **Global Element Properties** screen, select **Commerce Cloud B2C
    Shop Connector Shopper Token** and click **OK**.

2.  Configure the following parameters:

    <table><colgroup><col> <col></colgroup><thead><tr><th>Field Name</th><th>Value</th></tr></thead><tbody><tr><td><p>Base URI</p></td><td><p>Parameter base URI. Each instance or tenant gets its own base URI.</p></td></tr></tbody></table>

    ![Shopper token global elements properties config window on General tab](/mulesoft/current/en-us/commerce-cloud-shop-api-connector/latest/_images/shop-connector-shopper-token-config.jpg)

The XML configuration looks like this:

```xml
    <commerce-cloud-shopper-api:shopper-token-config name="Commerce_Cloud_B2C_Shop_Connector_Shopper_token" doc:name="Commerce Cloud B2C Shop Connector Shopper token" doc:id="9edebcff-2328-4312-88eb-d8ab4dcbd7cd" >
        <commerce-cloud-shopper-api:shopper-token-connection baseUri="${shopper.baseUri}" />
    </commerce-cloud-shopper-api:shopper-token-config>
```

### Customer Auth Connection Provider Configuration

Before you configure the connection for **Commerce Cloud B2C Shop Connector Customer Auth Config**,
[get the Shopper JWT Token](#get-shopper-jwt-token).

1.  On the **General** tab of the **Global Element Properties** screen, select **Commerce Cloud B2C
    Shop Connector Customer Auth Config** and click **OK**.

2.  Configure the following parameters:

    <table><colgroup><col> <col></colgroup><thead><tr><th>Field Name</th><th>Value</th></tr></thead><tbody><tr><td><p>Base URI</p></td><td><p>Parameter base URI. Each instance or tenant has its own base URI.</p></td></tr><tr><td><p>Authorization</p></td><td><p>Provide the Commerce Cloud B2C Shopper JWT Token as the authorization parameter.</p></td></tr></tbody></table>

    This example adds the base URI to the application properties file and references it using
    placeholders:

    ![Auth config global elements properties config window on General tab](/mulesoft/current/en-us/commerce-cloud-shop-api-connector/latest/_images/shop-connector-customer-auth-config.jpg)

3.  Click **Test Connection** to verify the configuration.

The XML configuration looks like this:

```xml
    <commerce-cloud-shopper-api:customer-auth-config name="Commerce_Cloud_Shopper_Connector_Customer_auth_config" doc:name="Commerce Cloud Shopper Connector Customer auth config" doc:id="3513fbf9-98ad-45a0-bd8e-5f01f1f340b2">
        <commerce-cloud-shopper-api:shopper-connection baseUri="${shopper.baseUri}" authorization="#[attributes.headers.Authorization]" />
    </commerce-cloud-shopper-api:customer-auth-config>
```

### OAuth2 Application Connection Provider

Use OAuth 2.0 to delegate user authentication to the service hosting the user account. For more
information, refer to
[Configuring OAuth 2.0 for Connectors](https://docs.mulesoft.com/connectors/introduction/intro-config-oauth2),
[Configuring OAuth 2.0 for Connectors on CloudHub](https://docs.mulesoft.com/connectors/introduction/intro-config-oauth2-cloudhub),
or [OAuth Support in the SDK](https://docs.mulesoft.com/mule-sdk/latest/oauth).

1.  On the **General** tab of the **Global Element Properties** screen, select **Commerce Cloud B2C
    Shop Connector Config** and click **OK**.

2.  Configure the following parameters:

    <table><colgroup><col> <col></colgroup><thead><tr><th>Field Name</th><th>Value</th></tr></thead><tbody><tr><td><p>Base Uri</p></td><td><p>Access API URL</p></td></tr><tr><td><p>Client Id</p></td><td><p>ID of the client account created with Salesforce Commerce Cloud</p></td></tr><tr><td><p>Client Secret</p></td><td><p>Secret of the client account created with Salesforce Commerce Cloud</p></td></tr><tr><td><p>Token url</p></td><td><p>Access token URL</p></td></tr><tr><td><p>Scopes</p></td><td><p>Scopes for access</p></td></tr></tbody></table>

    ![Commerce Cloud B2C Shop Connector Config with values for the OAuth 2.0 client credentials connection](/mulesoft/current/en-us/commerce-cloud-shop-api-connector/latest/_images/shop-connector-oauth2-config.jpg)

    This example adds credentials to the application properties file and references it using
    placeholders:

3.  Click **Test Connection** to verify the configuration.

The XML code for the OAuth 2.0 application connection provider configuration looks like this:

```xml
   <commerce-cloud-shopper-api:config name="Commerce_Cloud_B2C_Shop_Connector_Config" doc:name="Commerce Cloud B2C Shop Connector Config" doc:id="b487e17a-b80a-4cf4-a2f3-d24d47690844" >
		<commerce-cloud-shopper-api:am-oauth2-connection baseUri="${shopper.baseUri}" >
			<commerce-cloud-shopper-api:oauth-client-credentials clientId="${shopper.clientId}" clientSecret="${shopper.clientSecret}" tokenUrl="${shopper.tokenUrl}" scopes="${shopper.scopes}" />
		</commerce-cloud-shopper-api:am-oauth2-connection>
	</commerce-cloud-shopper-api:config>
```

## View the App Log

To check for problems, you can view the app log as follows:

- If you’re running the app from Anypoint Platform, the app log output is visible in the Anypoint
  Studio console window.

- If you’re running the app using Mule from the command line, the app log output is visible in your
  OS console.

Unless the log file path is customized in the app’s log file (`log4j2.xml`), you can also view the
app log in the default location `MULE_HOME/logs/<app-name>.log`. You can configure the location of
the log path in the app log file `log4j2.xml`.

## Configure the Other Connector Fields

After you configure a global element and connection information, configure the other fields for the
connector.

## See Also

- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)

- [Connector Reference](https://docs.mulesoft.com/commerce-cloud-shop-api-connector/latest/shop-api-connector-reference)

- [Salesforce Help](https://help.salesforce.com)