Migrate > Take the first steps after WebSphere Commerce migration > Migrating marketing > Migrating marketing from WebSphere Commerce Accelerator to Management Center v7

Enable Management Center marketing features

To enable the Management Center Marketing tool and certain features that support behavioral marketing, modify several parameters in the WebSphere Commerce configuration file.

Procedure

1. Open the WebSphere Commerce configuration file in a text editor.
   

2. For sites that have migrated from WebSphere Commerce Accelerator marketing, change the configuration file to point to the marketing services that support Management Center:

   1. Find the <Marketing> element. It looks like the following example:

      <Marketing version="Classic"/>
      

   2. Change the version attribute of the <Marketing> element so that the value is Dialog. If you set the version attribute to Dialog, use the Management Center Marketing tool for all marketing functions that it supports.

      There are two marketing versions:

      Classic

      The marketing runtime that works with WebSphere Commerce Accelerator.

      Dialog

      The marketing services that work with Management Center.

3. Enable the persistent sessions feature and personalization ID feature. These features are required to support behavioral marketing.

   1. Find the <PersonalizationId> element. It looks like the following example:

      <PersonalizationId enable="false"/>
      

   2. Verify the enable attribute is set to true. Depending on the site, this attribute might already be enabled, and require no change.

   3. Find the <PersistentSession> element. It looks like the following example:

      <PersistentSession cookieExpiry="30" display="false" enable="true"/>
      

   4. Ensure that:

      • The enable attribute is set to true.

      • The cookieExpiry value is a positive number. This number represents the number of days sessions are persisted for a customer.

        If the site has run the store enhancements enablement scripts, and if you did not have persistent sessions enabled before running the scripts, then the scripts set the cookieExpiry value to -1.

        To enable persistent sessions, change this value to a positive number.

4. Enable the following marketing listeners: the Sensor Event Listener and Experiment Evaluation Event Listener. These listeners must be enabled to support some behavioral marketing features and to gather marketing statistics for marketing experiments:

   1. Find the following string:

      compClassName="com.ibm.commerce.marketing.dialog.trigger.SensorEventListener"
      

   2. Below the string, ensure that the enable attribute is set to true, as shown in the following example:

      <component
          compClassName="com.ibm.commerce.marketing.dialog.trigger.SensorEventListener"
          enable="true" name="SensorEventListener">
         
      <property display="false">
             
      <start enabled="true"/>
         
      </property>
      </component>
      

   3. To improve performance, you can limit the Sensor Event Listener to monitor events raised only by the stores module.

      To do so:

      1. Search for the <module element that contains the attribute name="CommerceAccelerator".

      2. In the <InitParameters element, add the attribute recordable="false".

      3. Repeat the two previous steps for <module elements that contain the attributes name="SiteAdministration", name="OrganizationAdministration", and name="WorkspaceAdministration".

   4. Find the following string:

      compClassName="com.ibm.commerce.marketingcenter.events.runtime.ExperimentEvaluationECEventListenerImpl"
      

   5. Below the string, ensure that the enable attribute is set to true, as shown in the following example:

      <component
          compClassName="com.ibm.commerce.marketingcenter.events.runtime.ExperimentEvaluationECEventListenerImpl"
          enable="true" name="Experiment Evaluation Event Listener">
         
      <property display="false">
             
      <start enabled="true"/>
         
      </property>
      </component>
      

5. Optional: If we will be redirecting customers from the site to external sites through click actions on e-Marketing Spots, enable URL redirect filtering.

6. Save the changes.

7. Propagate your changes to the WebSphere Commerce configuration file.

• Update store pages to use the e-Marketing Spot JSP sample for Management Center
  If you previously used WebSphere Commerce Accelerator for marketing management and you have migrated to the Management Center Marketing tool, update any e-Marketing Spot code on your storefront with a different sample JSP snippet. This is required so that the e-Marketing Spots and the store work properly with the Management Center marketing services.

Previous topic:

Migrate campaigns and Web activities from WebSphere Commerce Accelerator to Management Center

Next topic:

Review settings in the marketing component configuration file (wc-admin-component.xml) for Management Center

Related concepts

IBM Management Center for WebSphere Commerce

Action: Display Recently Viewed

Related reference

Sample e-Marketing Spot JSP snippets and the Web activities they support

+

Search Tips   |   Advanced Search