9. Commerce Adapter Properties

The base path of the REST API ("/ws410/rest")

Default catalog version. On preview-cae and studio the defaultCatalogVersion.preview value is used

The full qualified hostname of the Hybris system

Setting if cookies should be accepted.

Defines the overal connection limit for a connection pool.

Http Client Configuration of Rest Connector communicating with SAP Rest Services.

Http Client Configuration of Rest Connector communicating with SAP Rest Services.

Cache invalidation chunk size.

Maximum wait time for cache invalidation.

Defines a connection limit per one HTTP route.

Http Client Configuration of Rest Connector communicating with SAP Rest Services.

Http Client Configuration of Rest Connector communicating with SAP Rest Services.

Setting if client should trust all ssl certificates.

ClientID used for OAuth2 Authentication with SAP Commerce System. Used to get authorized to access protected OCC API calls.

Password used together with the clientId.

Timeout for DNS cache entries in milliseconds

Path used to request new OAuth Tokens

Port used for OAuth token requests

Protocol used for OAuth token requests

Base path of OCC Rest Services

Configure attribute names, which are transmitted to the client as customAttributes. The key corresponds to the prefix of the document for json mappgings in lowercase. For example for ProductDocument it is "product".

The value is a comma separated list of attributes, which shall be available on the client side via com.coremedia.livecontext.ecommerce.common.CommerceBean#getCustomAttributes.

The value is transmitted as String representation of the JSON Object.

Example:

hybris.occ.custom-attributes-for.product=metaKeywords,metaDescription

The password belonging to the administrative user

Port of SAP Commerce REST Services (9001)

Secure port of SAP Commerce REST Services (9002)

The preview token user passed to the Preview Token Service

The preview token usergroup passed to the Preview Token Service

Protocol used for REST communication with SAP Commerce (http)

Secure protocol used for REST communication with SAP Commerce (https)

The administrative user used to access the SAP Hybris REST Services

Base URL for assets (e.g. https://shop-hybris.yourdomain.com)

Default catalog version. On live-cae the defaultCatalogVersion.live value is used

Maximum number of search hits returned to the client.

Web context of the SAP Hybris storefront webapp

The fully qualified hostname of the storefront url.

The storefront url

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 {@link CustomAttributesFormats}.

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.

Flag if commerce adapter implementation supports multiple catalogs.