9. Commerce Adapter Properties

Number of cache entries per cache key, until cache eviction takes place.

Example: sfcc.cache.capacities.product=50000

Enable or disable caching.

TTL in seconds until certain cache entries are invalidated.

Example: sfcc.cache.timeout-seconds.product=300

The default locale for accessing the commerce system if no locale parameter was passed into request.

The full qualified hostname of the SFCC instance.

Link template for links to product detail pages (PDPs).

Used to link to PDPs in the CoreMedia CMS. Template string is usually post processed on the commerce side.

Link template for AJAX URLs.

For example used to include personalized contents/fragments. Template String is usually post processed on the commerce side.

Link template for links to CoreMedia content.

Template string is usually post processed on the commerce side.

Link template for links to product detail pages (PDPs).

Used to link to PDPs in the CoreMedia CMS. Template string is usually post processed on the commerce side.

Link template for links to shop pages.

Shop pages are represented with "Augmented Pages" in the CoreMedia CMS. Template string is usually post processed on the commerce side.

Base URL of the commerce storefront

Storefront URLs, which are used to build storefront links to shop pages and resources for different environments. The structure of the Map should be: key=environment, value=url. The environment is the hardcoded name of the entity param which must be configured on the CM App side e.g. `commerce.hub.data.customEntityParams.environment=US|DE``

IMPORTANT! The keys used here, must match those used on the CM App side via metadata.custom-entity-param-names={environment}

Use this property if the adapter needs to distinguish environments. In this case it is required to set the above mentioned custom entity param.

Examples:

sfcc.link.storefront-url-for.us=https://sandbox-us.demandware.net/on/demandware.store/

sfcc.link.storefront-url-for.us=https://sandbox-de.demandware.net/on/demandware.store/

ClientID used for all Data and Shop REST API Calls to the Salesforce Commerce System. Used to set permissions for the ClientID on Shop and Data API - for example, which resources the ClientID is allowed to access

Password used together with the clientId.

Host name of central SFCC endpoint for authentication.

No need to customize.

Path to retrieve access token.

Protocol used to request access token.

Optional count for retrieving only a subset of all customer groups. If not set, the default behaviour of the salesforce Data API will apply.

Host name (FQDN) of your SFCC Instance.

Setting if cookies should be accepted.

Defines the overal connection limit for a connection pool.

Http Client Configuration for Rest communication with SFCC OCAPI Services.

Http Client Configuration for Rest communication with SFCC OCAPI Services.

Defines a connection limit per one HTTP route.

Http Client Configuration for Rest communication with SFCC OCAPI Services.

Http Client Configuration for Rest communication with SFCC OCAPI Services.

Setting if client should trust all ssl certificates.

Protocol used for OCAPI REST communication.

Set to true if integrating with a sandbox instance. Adjust base paths for REST API requests

On sandbox instances the base paths must be prefixed with '/s/{siteId}' see: https://documentation.demandware.com/DOC2/topic/com.demandware.dochelp/OCAPI/16.4/usage/UrlSchema.html

Version of Rest Service used.

URI path variant of {@link SfccConfigurationProperties#SFCC_VENDOR_VERSION}

REST API Version used for REST communication with the commerce system.

Map of additional metadata.

Can be used as customization hook. All properties starting with "metadata.additional-metadata.*" are transmitted to the generic client on the CMS side.

List of parameter names, which values need to be transmitted with every entity request from the CMS side.

Map of key value pairs.

Used as replacement map for example for link building in the generic client on the CMS side.

Flag if commerce adapter implementation supports multiple catalogs.

Name of the vendor.

Used to identify the connected vendor on the CMS side.