CoreMedia DXP 8 integrates with IBM WCS without importing catalog data into the CMS. Since all catalog data is requested dynamically from the IBM WCS system, CoreMedia DXP 8 comes with its own caching layer to provide fast access to IBM WCS data. In order to promptly reflect any changes of IBM WCS data, CoreMedia DXP 8 supports event based cache invalidation. Apply the following changes to enable event based cache invalidation:
Add the
CacheInvalidationHandleras described in Section 3.4.7, “Configuring REST Handlers”Add database triggers for cache invalidation of segments and marketing spots. In order to create corresponding entries in IBM WCS CACHEIVL table (where Dynacache Invalidation events are stored), several database triggers are needed. These are database specific but IBM WCS already provides correct working examples in the WCS workspace. You do not need all the sample triggers but only those for Segments and Marketing Spots.
Copy the triggers for the INSERT, UPDATE and DELETE cases for the following tables:
EMSPOT
MBRGRP
and add them to your database (for example, by using
http://HOST/webapp/wcs/admin/servlet/db.jsp)The sample files are located in the following directories:
- Oracle:
WCDE-ZIP\schema\oracle\cm.wcs.cacheivl.trigger.sql - IBM DB2:
WCDE-ZIP\schema\db2\cm.wcs.cacheivl.trigger.sql - Cloudscape/Derby:
WCDE-ZIP\schema\clouscape\cm.wcs.cacheivl.trigger.sql
![[Note]](../common/images/note.png) | Note |
|---|---|
If enabled IBM workspaces in your environment setup, you need to create these triggers for each workspace. If you enabled 5 workspaces for example, you need to create these triggers 5 times. Examples are given in the mentioned example files. |
 |  |  |
 |