Home
User Guide
The information contained in this section applies to IBM WebSphere Commerce Version 7.0.0.9 and Feautre Pack 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in new editions.
Administering
Managing features
You can administer the features for your store and site, such as attribute, catalog, promotion, marketing, order management features, and more. The administration tasks that you can complete differ depending on the type of feature and the tool that you use to administer your store and site.
Workspaces
You can enable and manage workspace assets and determine policies such as locking rules and commit and publishing options.
Publishing workspace data
Once all workspace tasks are completed and approved, you can publish files and data from the authoring server to the production server to view the effects on your site.
Disabling post-publish for quick publish
Cache invalidation occurs during post-publish for catalog and search. You can disable the post-publish for quick publish for the catalog or search resource managers to avoid duplicate cache invalidation.

Disabling post-publish for quick publish

Cache invalidation occurs during post-publish for catalog and search. You can disable the post-publish for quick publish for the catalog or search resource managers to avoid duplicate cache invalidation.

Procedure

Update the resource-containers.xml file.
1. Go to the WC_profiledir/installedApps/cell_name/WCServer_enterprise_archive/xml/content-management directory for your site.
2. Open the wc-resource-containers.xml file for editing.
3. Find the <wc:QuickPublishConfiguration> element in the file.
4. Add the following postPublish parameter within the element:
```
<wc:QuickPublishConfiguration>
<wc:Publisher className="com.ibm.commerce.context.content.resources.publish.DefaultJDBCContentPublisherImpl"
initParameters=[other-parameters] postPublish="false" [other-parameters]/ >
</wc:QuickPublishConfiguration>
```
Save your changes and close the file.
Restart your WebSphere Commerce server to apply the changes to your site.