7. Commerce Adapter Properties

The base URL, with protocol and port (if needed), to access the commercetools API.

The absolute URL, with protocol and port (if needed), used for authorization at the commercetools system.

The unique identifier of the API client.

The confidential client secret.

Decorate the SphereClient (responsible for all call to the commercetools system) with a DeprecationExceptionSphereClientDecorator in order to throw an exception on usage of deprecated API calls.

The unique key of the commercetools project.

A comma separated list of scopes, the API client should have access to.

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

The version of the product data. Can be current for published data or staged for preview.

True if language of locale shall be used in search requests.

Maximum search result size.

List of facet keys. These facets only support single values to be selected.

Number of cache entries per cache class until cache eviction takes place. The keys must match the cache classes as defined by the cache keys. Please refer to javadoc of com.coremedia.cache.CacheKey.

TTL in seconds until certain cache entries are invalidated.

The number of request/response pairs to cache persistently. The keys must be valid cache classes as configured for the data lookup service, e.g., catalog, catalogs, category, categories, etc.

Root resource to persistently store messages. If this property is not set, no messages will be persisted. Configure a value to enable persistent caching of messages.

Controls if a parent dependency is registered for a non-base product so that it is invalidated together with its base product.

Whether to recompute entities proactively on invalidation.

Whether or not to propagate invalidations of entities to the clients.

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.

Format of the custom attribute values.

The keys are always plain strings.

Used to identify the deserialization format 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.

Name of the vendor.

Used to identify the connected vendor on the CMS side.