Publishing an extended site: one-step method

You can set up an extended site for learning purposes by publishing an extended sites composite store archive. Use this one-step method only if your environment does not already have an extended sites composite store archive published.

Important: Do not publish an extended site composite store archive in your environment if:
  • You already published another extended site composite store archive.
  • You are running WebSphere Commerce Developer (toolkit), which comes with all the store archives already published.

If you do publish an additional extended site composite store archive, data from the new store archive will combine with and overwrite the previously published extended site, potentially creating an unwanted result. In addition, any changes that are made to the previously published extended site are lost.

To add an additional extended site in your environment, follow this procedure instead: Publishing an extended site: advanced method. Alternatively, you can clean your environment by removing all previously published stores from the STORE database table. Then, you can install a new extended sites composite store archive in your clean environment.

Before you begin

  1. Ensure that you have Site Administrator access.
  2. Ensure appropriate services and servers are running.
  3. LinuxAIXWindowsConfigure publish.
  4. Back up your database so that you can restore your prepublished version if necessary.

About this task

When you complete this procedure, your environment includes:
  • A sample customer-facing storefront that shoppers can purchase from.
  • The associated asset stores and a hub store.
  • The organization structure, predefined user roles, and necessary access control policies.
You can use the environment to learn about the extended site structure and features.


  1. Open the Administration Console, and select the Site option.
  2. From the Store Archives menu, select Publish.
  3. From the Store Archive list, select ExtendedSites.sar.
  4. Click Next.
    The Parameters page displays.
  5. From the Sample data list, choose the type of sample data that you want in the catalog; then click Next.
  6. Click Next.
  7. Review the Summary page, and then click Finish.
  8. Click OK on the message that confirms the archive is submitted for publishing.

    The Publish Status page displays.

  9. Wait for the Publish Status column to change to Successful. Click Refresh to see the updated status.
  10. LinuxAIXWindows Set up WebSphere Commerce search and build the search index.
    1. Set up search index.
    2. Preprocess the search index data.
    3. Build the WebSphere Commerce search index.
  11. View the published store in a browser by using the following URLs.
    • For the Aurora consumer direct store: http://host_name/webapp/wcs/stores/servlet/auroraesite/
    • For the Aurora B2B direct store: http://host_name/webapp/wcs/stores/servlet/aurorab2besite/

What to do next

  1. Compile your JavaServer Page files. Compiling the JavaServer Pages (JSP) files in your site or store before launching it will significantly reduce the amount of time necessary to load each store page. As a result, use batch compiler to convert your store or site JSP files after publishing a store archive.
  2. To prevent unnecessary exceptions from displaying, delete the SendTransactionMsg job from the scheduled jobs. For more information, see Deleting a scheduled job.
  3. LinuxAIXWindowsTo enable caching in the starter stores, you must merge the cachespec.xml file from the following directory:
    WebSphere Commerce DeveloperNote: In the WebSphere Commerce development environment, caching is turned on by default.
    • WC_installdir/samples/dynacache/businessmodel

      with the cachespec.xml file in the following directory:

    • WC_eardir/Stores.war/WEB-INF

    Edit the existing cachespec.xml file in the WEB-INF directory with the changes in the first file, rather than replace it.

  4. If you are running your web server on a separate node than the WebSphere Commerce node, complete the following steps after publishing a store archive:
    1. Stop the web server.
    2. Copy store web assets from the following directory from the WebSphere Commerce machine to the web server machine in the same location: WC_eardir/Stores.war
    3. Start the web server.
  5. In a clustered environment, you must synchronize all cluster members after publishing any store archive. It might take some time for the newly published store assets to propagate to all of the nodes in the cluster after the store finishes publishing.
  6. If you have published a starter store in a workspace environment, complete these additional steps to deactivate and then reactivate all the sample web activities. This ensures that all web activities display correctly in e-Marketing Spots on the storefront:
    1. Open the Workspace Management tool.
    2. On the toolbar, click Work on approved content Work On Approved Content.
    3. Open the Marketing tool and select the name of the store you published.
    4. In the explorer view, click the Activities folder.
    5. Right-click any row in the Activities - List page, and then click Select All.
    6. On the toolbar, click Deactivate Deactivate.
    7. On the toolbar, click Activate Activate.

      Now, when you preview the store, all sample web activities display in e-Marketing Spots.