Tuesday, 4 November 2014

Websphere Commerce Default Catalog (Websphere Commerce 7 feature pack 5)

Websphere Commerce Default Catalog





In Feature Pack 5, business users can specify which catalog to display on the storefront through the catalogs tool in Commerce Management Center. The default catalog is the catalog which is exposed to shoppers at store front if there is no catalog specified in store URLs. If the catalog is specified in the URL, then that is the one that is used. Your site can only have one default catalog for a particular store. The default Catalog can be either the master catalog or one of sales catalogs. By default the master catalog is the set default catalog until a different catalog is selected in the Catalogs tool. If your store has more than one catalog, you can specify a catalog to use as a default catalog. The default catalog is language independent, and supports the Aurora, Elite, Mobile and Android Native Application stores.

If site uses an extended site store model and plans to use the default catalog, your site can have multiple default catalogs set. You can have a default catalog for your asset store and potentially a separate default catalog for each of your extended site stores. If your site does not set a default catalog for its asset store or extended site stores, the master catalog is set as the default catalog. If your site has a default catalog specified for your asset store, but not your extended site stores, your extended site stores uses the default catalog specified for the asset store. The asset store default catalog can only be set and changed in the asset store. When working in an extended site store, you can set the default catalog for that store, including overriding an asset store default catalog that is set as the extended site store default catalog.

STOREDEFCAT table is created for storing information about which catalog is the default for each storefront store. The existing Catalog noun is updated to add a new attribute called “default”. A new service call Get Active Catalog service should return thedefault catalog. The OnlineStore noun is updated to add defaultCatalog element. The default catalog is set through the ChangeOnlineStore services. A new Get Default Catalog service will return the default catalog. This service is used by RuntimeServletFilter to get the default catalog. This service is customizable so that you can customize the logic of how to determine which catalog is default. GetOnlineStore Service is updated to return default catalog configurations

If store does not use the SEO URLs introduced in WebSphere Commerce Feature Pack 3, there is no impact on your store URLs when using default catalog. Existing SEO URLs or non-SEO URLs continue to forward visiting shoppers to the store catalog identified by the catalog ID specified in the URL. If your site plans to use the default catalog, remove the hardcoded catalog ids from the URLs. Removing the hard-coded ids cause the RuntimeServletFilter to call the get default catalog service and retrieve the default catalog ID, which ensures content from the default catalog displays. If your site uses or plans to use the SEO URLs introduced in WebSphere Commerce Feature Pack 3, the URLs continue to work, however the URLs do not return the default catalog. You must run a migration script to migrate the URLs in order to have the SEO URLs introduced inWebSphere Commerce Feature Pack 3 to use the default catalog

The default catalog is supported for the Aurora and Elite store models, including the Aurora Mobile store model, and the Android Native Application Store. The default catalog settings are only managed using Management Center. You cannot data load the default catalog. The default catalog function is not supported for any other store model, and is not supported for Portal, Sales Center, or WebSphere Commerce Accelerator

No comments:

Post a Comment