Changing properties in the marketing component configuration file (wc-admin-component.xml)

To change any properties in the marketing component configuration file (wc-admin-component.xml), you must create a customized version of the file in a new folder. The customized version of the file must contain only the changed properties.

Before you begin

To understand the properties that this file contains, see Marketing component configuration files (wc-admin-component.xml).

Procedure

  1. Open WebSphere Commerce Developer and switch to the Enterprise Explorer view.
  2. Create a com.ibm.commerce.marketing-ext folder for your customized marketing component configuration file at the following path:

    WC_eardir\xml\config\com.ibm.commerce.marketing-ext\

    If this folder exists and contains a customized version of the wc-admin-component.xml file, or if a customized version exists elsewhere, open the customized version and skip to the next step. If the folder does not exist and contain a customized version, complete these substeps:

    1. Go to the default marketing component configuration file at the following path:

      WC_eardir\xml\config\com.ibm.commerce.marketing\

    2. Copy the wc-admin-component.xml file to the new WC_eardir\xml\config\com.ibm.commerce.marketing-ext\ folder.
    3. Open the copied wc-admin-component.xml in an editor. This copy becomes the customized version of the wc-admin-component.xml file.
  3. Change any properties as required for your site.

    If your customized marketing component configuration file already exists, and if you want to change additional properties that are not currently in the customized file, you can copy those properties into your customized file from the default marketing component configuration file at WC_eardir\xml\config\com.ibm.commerce.marketing\wc-admin-component.xml.

  4. Within the <_config:configgrouping name="MarketingRuntime"> element, remove any properties that are not set differently from the default marketing component configuration file. The customized file must contain only the differences.
  5. Save and close the customized file.
  6. To update the changes in a development environment, start, or restart the WebSphere Commerce server.
  7. If you want to push the configuration changes out to the production environment, see Deploying J2EE assets for a single file.