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.
- 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
- Apply 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.
- Ensure that you have Site Administrator access.
- Ensure appropriate services and servers are running.
- Configure publish.
- Back up your WebSphere Commerce database so that you can restore your pre-published version if necessary.
About this task
- 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.
Procedure
What to do next
- 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:- 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
<jsp-property-group> <url-pattern>*.jsp</url-pattern> <el-ignored>true</el-ignored> </jsp-property-group>
- Restart your WebSphere Commerce server.
- 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.
- Edit the following two files:
- 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.
- To prevent unnecessary exceptions from displaying, delete the SendTransactionMsg job from the scheduled jobs. For more information, see Deleting a scheduled job.
- To
enable caching in the starter stores, you must merge the cachespec.xml
file from the following directory: Note: 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.
- WC_installdir/samples/dynacache/businessmodel
- 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:
- Stop the Web server.
- 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
- Start the web server.
- 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.
- 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:
- Open the Workspace Management tool.
- On the toolbar, click Work On Approved Content.
- Open the Marketing tool and select the name of the store you just published.
- In the explorer view, click the Activities folder.
- Right-click any row in the Activities - List page, and then click Select All.
- On the toolbar, click Deactivate.
- On the toolbar, click Activate.
Now, when you preview the store, all sample Web activities will display in e-Marketing Spots.