store path

The two extended sites do not contain any catalog data, but instead they set their store path to point at the catalog asset store.

So far, we have seen how catalog data and presentation setup are shared among different stores using the store path.

The mechanism that WebSphere Commerce uses to share such data assets is called the store path.

Retrieving class store path for the system account.

Theoretically, separate asset stores may be created for each store path resource.

This article introduces the concepts of asset store and store path, which allow for sharing data among different sites.

This store defines a store path that selects the asset stores, which contain the necessary configuration data.

Each extended site defines its store path, which indicates where its configuration data comes from.

The flexibility of store path is that each resource may be created in its own asset store.

A catalog is one of many kinds of resources that are shared between stores using the store path.

Retrieving class store path for impersonated user.

The catalog store path of all customer facing stores selects the common catalog asset store.

Retrieving class store path for non-impersonated user.

A store path lists a set of resources, such as Catalog, Presentation, Campaigns, Promotions, Commands, and so on.

For example, the store path indicates that catalog data should be searched in the customer store first, and then in the catalog asset store.

Other resources shared via store path

Websphere Commerce 5. 6 enables a large number of resources that is shared using the store path