Enabling the Marketing tool inside the Management Center

To use the Marketing tool inside the Management Center you must first enable the marketing runtime. You must perform this task once after installing the feature pack.

Before you beginBefore you enable the marketing runtime, complete the following prerequisites:

  1. Ensure that any necessary WebSphere Commerce fix packs are installed.

  2. Ensure that you have enabled the Management Center.

  3. If WebSphere Commerce is managed by WAS Deployment Manager (dmgr), start the deployment manager and all node agents. If WebSphere Commerce is not managed by WAS Deployment Manager, start your WAS.

  4. To enable or disable features in WebSphere Commerce Developer that run on Cloudscape, the WebSphere Commerce Test Server must be stopped. The test server does not need to be stopped if WebSphere Commerce Developer is running on another database, such as DB2.

About this taskTo enable the marketing runtime in support of the Marketing tool in the Management Center:

  1. Navigate to the following directory:

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

    1. Find the Marketing tag. It resembles the following text:
      <Marketing version="Classic"/>
      

    2. Change the version attribute of the Marketing element so that the value is Dialog. This value tells WebSphere Commerce which marketing runtime to use. There are two marketing versions: Classic refers to the pre-Feature Pack 3 marketing runtime; Dialog refers the marketing runtime required for Feature Pack 3 and later feature packs. When you set this value to Dialog, use the Management Center Marketing tool for any functions that it supports (campaigns, content, Web activities, e-mail activities, and e-mail templates).

    3. Find the PersistentSession tag. It resembles the following text:
      <PersistentSession cookieExpiry="30" display="false" enable="true"/>
      

    4. Ensure that the enable attribute is set to true. Depending on your site, this might already be configured properly, and require no change.

    5. Find the PersonalizationId tag. It resembles the following text:
      <PersonalizationId enable="false"/>
      

    6. Ensure that the enable attribute is set to true.

    7. Optional: If you will be redirecting customers from your site to external sites through click actions on e-Marketing Spots, enable URL direct filtering.

  3. Save your changes.

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

  5. Optional: Configure the default session length for your site to specify how long certain marketing messages are displayed to a customer before being refreshed. This can be set by creating a wc-admin-component.xml file, in the WCDE_installdir\xml\config\com.ibm.commerce.marketing-ext directory, according to the extending the configuration of a service module to add name-value pairs topic.

  6. Optional: If you updated the session length, deploy the wc-admin-component.xml file made to configure the default session length to the xml/config/com.ibm.commerce.marketing-ext/ directory on your production server according to the instructions in the Deploying customizations made using the BOD command framework and the data service layer topic.

  7. Restart your WebSphere Commerce Server.

  8. Configure the marketing event statistical counters.

ResultsWhen the Marketing tool is enabled, you can begin using it inside the Management Center to manage marketing assets.

What to do nextIf you have not already Enabled the Management Center features for starter stores, also complete Use the e-Marketing Spot JSP sample, before your marketing assets are visible on your storefront pages.