WebSphere Commerce Enterprise

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 combines 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: tpbpubsa_esite_v2.html. 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. Feature Pack 4Feature Pack 2Feature Pack 5Feature Pack 3Feature Pack 1Feature Pack 6Apply interim fix for APAR JR47136. This interim fix corrects an issue where a blank page is displayed during store creation with the store creation wizard.
  2. Ensure that you have Site Administrator access.
  3. Ensure appropriate services and servers are running.
  4. SolarisLinuxAIXWindowsConfigure publish.
  5. Back up your WebSphere Commerce database so that you can restore your pre-published version if necessary.

About this task

When you complete this procedure, your environment includes the following:
  • A number of sample storefronts that shoppers can purchase from. The list of storefronts depends on which extended site composite store archive you published (see ../concepts/csmssa.html).
  • 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.
Feature Pack 5 or laterNote: To create your extended sites organization structure with a storefront asset store based on the Aurora starter store, you must first install and enable WebSphere Commerce Version 7 Feature Pack 5 or later.

Procedure

  1. Open the Administration Console, and select the Site option.
  2. From the Store Archives menu, select Publish.
  3. From the View list, select Extended sites.
  4. From the Store Archive list, select the check box beside one of the following store archives:
    • Feature Pack 5 or laterExtendedSitesV2.sar
    • Feature Pack 4Feature Pack 2Feature Pack 3Feature Pack 1ExtendedSites-FEP.sar
    • WebSphere Commerce Version 7.0.0.0ExtendedSites.sar
  5. Click Next, which displays the Parameters page.
  6. From the Sample data list, choose Housewares sample data, and then click Next.
  7. Click Next.
  8. Review the Summary page, and then click Finish.
  9. Click OK on the message that confirms the archive is submitted for publishing.

    The Publish Status page displays.

  10. Wait for the Publish Status column to change to Successful. Click Refresh to see the updated status.
  11. SolarisLinuxAIXWindowsSet 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.
  12. Launch one of the published extended site stores:
    1. Open WebSphere Commerce Accelerator.
    2. From the Store name list, select the Extended Sites Hub store, and then click OK.
    3. From the Extended Sites menu, click View Stores.
    4. Click the name of one of the following stores:
      • Feature Pack 8AuroraB2BESite
      • Feature Pack 5 or laterAuroraESite
      • Sample B2B Store
      • Feature Pack 4Feature Pack 7Feature Pack 2Feature Pack 5WebSphere Commerce Version 7.0.0.0Feature Pack 3Feature Pack 1Feature Pack 6EliteESite (deprecated in Feature Pack 8)
      • Feature Pack 4Feature Pack 2WebSphere Commerce Version 7.0.0.0Feature Pack 3Feature Pack 1MadisonsESite
    5. Copy the URL for the store, and then paste it into the address field in a browser.

      If your published store does not display the category navigation in the storefront, you must preprocess and build the search index. For more information, see Troubleshooting: Storefront categories do not display after you publish a store archive.

What to do next

  1. If you are publishing your version 7 store into the same environment as a previously migrated version 5.6.1 store, you see a warning message. The migrated version 5.6.1 environment has the JSTL Expression Language (EL) set to ignore. 
    Your application currently has the JSTL Expression Language (EL) feature disabled, any starter stores that 
are ready for this feature will not function correctly. Refer to the online documentation on how to correct this 
behavior. Do you want to continue with the store publish?
    To use the new store, first enable EL, then publish the store.
    Note: Changing this setting allows your version 7 store to function correctly, but will prevent your 5.6.1 store from working until you migrate your JSP files, described in step c.
    To enable EL:
    1. Edit the following two files:
      • WAS_installdir/profile/profile_name/installedApps/cell_name/EAR_name/Stores.war/WEB-INF/web.xml
      • WAS_installdir/profile/profile_name/config/cells/cell_name/applications/EAR_name/deployments/application_name/Stores.war/WEB-INF/web.xml
      In each of the files, remove the following XML:
      <jsp-property-group>
      <url-pattern>*.jsp</url-pattern>
      <el-ignored>true</el-ignored>
</jsp-property-group>
    2. Restart your WebSphere Commerce server.
    3. To use the old WebSphere Commerce version 5.6.1 store and the new version 7.0 store concurrently, you must migrate the old 5.6.1 store JSP files in your development environment. To migrate your JSP files, see Migrating JSP files and store properties files.
  2. 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.
  3. To prevent unnecessary exceptions from displaying, delete the SendTransactionMsg job from the scheduled jobs. For more information, see Deleting a scheduled job.
  4. SolarisLinuxAIXWindowsTo 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.

  5. 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.
  6. WebSphere Commerce EnterpriseWebSphere Commerce ProfessionalIn 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.
  7. Feature Pack 5 or laterIf 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 just 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 will display in e-Marketing Spots.