Tips to propagate the data using stageprop in a short amount of time.

The value for the batch size and transaction size parameters can help to propagate large amounts of data in a short amount of time in comparison to the OOB StagingProp utility from WCS 7 Fixpack 5 and prior.

However, we can make use of the STAGLOG.STGFILTER column to mark particular rows in the STAGLOG table to be propagated. When you run the StagingProp utility, you specify the filter parameter with the filter value and only records in the STAGLOG table with the associated filter value will be propagated to production.  Even the oracle streaming concept can be of much help with this approach. 

Another option is to use of the scope parameter. The parameter can be used to propagate changes for specific tables.

Business Context Service instead of Http session or Cookies

Apart from the Http session or cookies, You can also take a look at using the Business Context Service option which is available for maintaining the information throughout the user activity and invalidating it when the user logs out or the browser is closed.

The context data will be available in tables, CTXMGMT and CTXDATA

To create a Custom Business Context Service -

• Create a new Interface for the custom context  by extending the com.ibm.commerce.context.base.Context interface.
• Create a context implementation class that implements the custom interface created before extending the com.ibm.commerce.context.baseimpl.AbstractContextImpl.
• Registering new Business Context by making an entry in businessContext.xml or Create a new businessContext.xml. Register this new businessContext.xml in the wc-server.xml under the BusinessContextService element and then use it.
• You can then push the values from the controller command into the context and then use it across the application.

Troubleshooting DynaCache invalidation fails to clear the cache

When:
1) Running the DynaCacheInvalidation scheduled job with the 'clearall' value specified in the CACHEIVL table.
2) Calling the DynaCacheInvalidation URL directly with clear=true passed as a parameter value.
(https://<domainname>:8000/webapp/wcs/tools/servlet/DynaCacheInvalidation?clear=true)

No errors are thrown in the logs and using the 'Clear Cache' button in the Cache Monitor clears the cache as expected.

From the traces you will notice that the logs indicate the wrong cacheName is referenced, which point to a recommended fix not being installed.

[9/27/10 15:19:51:504 MDT] 000000b2 WC_CACHE > com.ibm.commerce.dynacache.commands.DCInvalidationCmdImpl performExecute Entry
[9/27/10 15:19:51:504 MDT] 000000b2 Cache 3 clear() cacheName=default waitOnInvalidation=true

The cacheName should be "baseCache", not "default".

This issue is addressed in the WAS APAR PK77428. This fix is included in WAS V7.0.0.5 if you prefer upgrading your WAS Fix Pack level.

Configuration for Facet display on Store Front 

If the MAX_DISPLAY column in the FACET value is set too low, some categories might not show up correctly.

To resolve this issue:

1. Set the MAX_DISPLAY column in the FACET table to -1.
2. Set the displayChildCategoriesOnly property to true in your custom wc-component.xml file.