Publishing a store archive using the Publish wizard

Publishing a store archive to a WebSphere Commerce Server allows you to create a running store.

To publish a store archive from the Publish wizard:

  1. Ensure that you have Site Administrator access.
  2. Ensure appropriate services and servers are running.
  3. AIXSun Solaris Operating EnvironmentLinuxWindowsConfigure publish.
  4. (Optional) Back up your WebSphere Commerce database, so you can restore your pre-published version if necessary.
  5. Open the Administration Console, selecting the Site option.
  6. From the Store Archives menu, select Publish. The Store Archives page displays listing the store archives available for publish. By default, the page displaying composite store archives displays.
  7. Select the composite store archive you want to publish.

    Note: To publish a store archive other than a composite store archive, see Publishing a store archive using the Publish wizard - Advanced Options.

  8. Select the ConsumerDirect.sar file.
  9. Select the AdvancedB2BDirect.sar file.
  10. Select the DemandChain.sar file.
  11. Click Next. The Parameters page displays. Depending on the store archive you selected, different parameters will display. For more information, see Publish wizard parameters by store archive.
    • Business Edition onlyIf you are publishing a starter store archive for the first time, accept the default values in the parameter fields.

      If you are publishing a starter store archive other than a composite store archive, or if you want to publish a second store of the same type of a previously published store archive, see Publishing a store archive using the Publish wizard - Advanced Options.

      Important: It is not recommended that you publish more than one type of composite store archive or organization structure store archive in the same instance (for example, do not publish a ConsumerDirect.sar and DemandChain.sar in the same instance) or that you publish the same composite store archive or organization structure store archive more than once, as doing so may overwrite data previously published. For more information, see Publishing a store archive using the Publish wizard - Advanced Options.

  12. Click Next. The Summary page displays, listing the store archive and parameters selected, as well as the location to which the store archive will be published.
  13. After reviewing the summary information, click Finish. A confirmation dialog displays, telling you the number of the publishing job. Note the job number for future reference. Click Ok. The Publish Job Status page displays. The publishing state is reflected in the Publish status column. Click Refresh to update the status.
  14. To see more details about a particular publish job, select it from the list. Click Details. The Publish Details page displays. Review the publishing details.

    Tip: While the store archive is being published, the Publish Details page is automatically refreshed every 20 seconds with the latest publishing status.

  15. If the store archive has been published successfully, you can launch the store. To view and test your store, click Launch Store. A dialog box displays, asking you for the Web Application context. Accept the default. Click OK. If the store has not been published successfully, see Troubleshooting publishing.

    Notes:

    • Compiling the JavaServer Pages (JSP) files in your site or store before launching it will significantly reduce the amount of time needed to load each store page. As a result, it is recommended that you batch compile your store or sites JSP files after publishing a store archive. To batch compile the store's JSP files, see Compiling your JavaServer Page files.

    • In order to prevent unnecessary exceptions from displaying, delete the SendTransactionMsg job from the scheduled jobs. For more information, see Deleting a scheduled job.

  16. In order to enable caching in the starter stores, you must merge the cachespec.xml file from the following directory:

    WC_installdir/samples/dynacache/businessmodel
    i5/OSiSeriesWC_user_dir/Base/WAS_instance_name/installedApps/cell_name/WCServer_enterprise_archive/Stores.war/WEB-INF

    with the cachespec.xml file in the following directory:

    WC_installdir/installedApps/host_name/WCServer_enterprise_archive/Stores.war/WEB-INF
    i5/OSiSeriesWC_user_dir/InstalledApps/host_name/WCServer_enterprise_archive/Stores.war/WEB-INF

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

    WebSphere Commerce development environmentNote: In the WebSphere Commerce development environment, caching is turned on by default, so you do not need to complete this step if you are publishing in the WebSphere Commerce development environment.

  17. When you have finished viewing the store, bookmark the site, and close the browser.

Important:

  1. 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's web assets from the following directory from the WebSphere Commerce machine to the Web Server machine in the same location:
    3. Start the Web server.
  2. If you change the Web application Context path, you must ensure that it matches the path defined in the WebSphere Commerce Server.
  3. Only one store archive at a time can be published.
  4. When you launch a store based on the consumer direct starter store from Administration Console, you are logged into the store with the same user name and password that you used to log into Administration Console. If you change your password in the store, you are also changing it for Administration Console. Instead, to test the features in the store, including changing your password, save the site address, close all browser windows, then log on to the store again. For more information, see Limitations when using multiple browsers windows.
  5. If you plan to make changes to your JSP files after publishing your store, you should disable servlet caching in the WebSphere Application Server.

    WebSphere Commerce development environment If you are using the WebSphere Commerce development environment, the servlet caching is disabled by default.

Feedback