Sunday 31 August 2014

Associating a site with Catalog in ATG

Today while importing the catalog data in BCC. I faced one issue.After completion of data load into BCC I realized that site information is missing from catalog items (category,product and SKUs).

Here is the list of steps I followed from ATG documentation to resolve this issue.


Note : Before following these steps.Run a full deployment fololwoed by Catalog Update Service (This will also create project in BCC.You need to deploy the project). 

Steps to register/create a site and associate it with a catalog.
  1. In the Business Control Center, expand Site Administration, then click Manage Site Assets.
  2. Enter a name and optional description for the project and click Continue.
  3. Create a new site and assign the existing application’s catalog as the default catalog for the new site. During this step, the site ID for the new site is assigned to the existing catalog. The same ID is also assigned to any of the catalog’s categories and sub-catalogs.
  4. At this point, existing catalog folders will appear in Merchandising as unsited items. If you want to keep them, these folders also need a site ID. Follow the steps below to assign a site ID to your catalog folders:
    • In the Business Control Center, expand Merchandising, then click Manage Commerce Assets.
    • Enter a name and optional description for the project and click Continue.
    • Navigate to Site Catalogs, then to Unsited Items.
    • Click the split screen icon at the bottom left of the window.
      BCC Split Screen Icon
      BCC Split Screen Icon
    • In the bottom portion of the split screen, navigate to Site Catalogs.
    • Drag a catalog folder from the top pane to the site you want it affiliated with in the bottom pane. The catalog folder is now affiliated with the site and has that site’s ID assigned to it.
  5. Deploy the project. During deployment, the site ID you assigned to the catalog is propagated from the catalog down to its constituent products and SKUs (by the CatalogMaintenanceService, which runs automatically on deployment).

No comments:

Post a Comment