Adding database triggers to automatically update registries after data propagation

You can add database triggers to automatically update the marketing registry after running the stagingprop utility to publish data to the production database. The new triggers add a row to the CACHEIVL table. The value for the DATAID column in the table is "WCR+CampaignInitiativeCache" whenever the EMSPOT or DMACTIVITY tables are modified. This value causes the DynaCacheInvalidation scheduler job to refresh the CampaignInitiativeCache registry and marketing business object cache. The cache is refreshed the next time the DynaCacheInvalidation schedular job runs.

Fix pack 3 and higher fix packs provide database triggers that you can add to automatically update the promotions registries after running the stagingprop utility. The new triggers add the following values to the CACHEIVL table in the DATAID column:

• WCR+PromotionRegistry
• WCR+PromotionGroupRegistry
• WCR+PromotionPolicyRegistry

Note:

• If you are using the e-Marketing Spot JSP caching technique based on activity behavior, do not add the database triggers with "WCR+CampaignInitiativeCache" invalidation. When using the JSP caching technique, clearing the CampaignInitiativeCache registry is no longer required. To set up this technique, follow the instructions in Setting up JSP snippet caching based on activity behavior.
• If you are using the e-Marketing Spot JSP caching technique based on activity behavior and you installed APAR JR44939, then consider dropping database triggers that run "WCR+CampaignInitiativeCache" invalidation. For more information, see Enabling interim fix JR44939.