Administer > Deploy > Publish a store archive


Publish a store archive using the Publish wizard

Use the Publish wizard to create stores and store related components.

Use the Publish wizard to publish various store-related components, including...

You can also publish individual stores, or composite store archives, which include all the components listed here. For a list of the starter store archives available with WebSphere Commerce, see Starter store archives.

WebSphere Commerce also supports the following advanced publishing options:

If you change the Web application Context path, ensure that it matches the path defined in the WebSphere Commerce Server.

When you open a 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 the password in the store, you are also changing it for Administration Console. Instead, to test the features in the store, including changing the 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.


Procedure

  1. Ensure that you have Site Administrator access.

  2. Ensure appropriate services and servers are running.

  3. Configure publish.

  4. Back up the WebSphere Commerce database, so you can restore the 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. From the View list, select the type of composite store archive to publish.

    To publish an extended site composite store archive, select Extended Sites from the View list to see a complete list of applicable .SAR files

    To publish a store archive other than a composite store archive, see...

  8. Click Next.

    The Parameters page displays. Depending on the store archive you selected, different parameters display.

    • If 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 that is not a composite store archive, or to publish a second store of the same type of a previously published store archive, see Publish multiple store archives of one type per instance.

  9. Click Next.

    The Summary page displays, listing the store archive and parameters selected, and the location to which the store archive is published.

  10. 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.

  11. Optional: When you have finished viewing the store, bookmark the site, and close the browser.


What to do next

  1. If you are publishing the 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. Please refer to the online documentation on how to correct this behavior. Do to continue with the store publish?

    To use the new store, first enable EL; then publish the store.

    Changing this setting allows the version 7 store to function correctly, but will prevent the 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_HOME/profile/profile_name/installedApps/cell_name/EAR_name/Stores.war/WEB-INF/web.xml

      • WAS_HOME/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 the WebSphere Commerce server.

    3. To use the old WebSphere Commerce version 5.6.1 store and the new WebSphere Commerce, version 7.0 store concurrently, also migrate the old 5.6.1 store JSP files in the development environment.

      To migrate the JSP files, see:Migrate JSP files.

  2. Compile your JavaServer Page files. Compiling the JSPs files in the 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 the store or sites JSP files after publishing a store archive.

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

  4. To enable caching in the starter stores, merge the cachespec.xml file from the following directory:

    In the WebSphere Commerce development environment, caching is turned on by default.

    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 the 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_EAR/Stores.war

    3. Start the Web server.

  6. In a clustered environment, 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.

See also


+

Search Tips   |   Advanced Search