Configuring Secured and Unsecured Repositories

An administrator secures a repository in order to control user access to assets, asset properties, and asset types. For example, you can make all products visible to a user, but prevent the same user from editing product properties.

Merchandising uses three versioned Commerce repositories.

The following table lists the names and paths of the secured and unsecured versions of the versioned Commerce repositories that are provided with Merchandising. The paths of the Secured Repository and XML Repository definitions are also shown.

Merchandising
Product Catalog

Price List

Claimable Repository

Unsecured Repository

<ATG10dir>/DCS/config/config.jar/atg/
commerce/catalog/
ProductCatalog

<ATG10dir>/DCS/
config/config.jar/
atg/commerce/
pricing/priceLists/PriceLists

<ATG10dir>/DCS/
config/config.jar/
atg/commerce/
claimable/Claimable
Repository

Secured Repository

<ATG10dir>/B2BCommerce/config/config.jar/atg/commerce/catalog/SecureProductCatalog.properties

<ATG10dir>/DCS/config/config.jar/atg/commerce/pricing/priceLists/SecurePriceLists.properties

none

Secured Repository
XML Repository Definition

<ATG10dir>/DCS/Versioned/config/config.jar/atg/commerce/catalog/custom/secureCustomCatalog.xml

<ATG10dir>/DCS/Versioned/config/config.jar/atg/commerce/pricing/priceLists/securePriceLists.xml

none

Notes: