Develop > Presentation layer > Customize marketing > Marketing customization: Management Center > Work with the marketing component configuration file
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), 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 file (wc-admin-component.xml).
Procedure
- Open WebSphere Commerce Developer and switch to the Enterprise Explorer view.
- Create a com.ibm.commerce.marketing-ext folder for the customized marketing component configuration file at the following path:
WC_EAR\xml\config\com.ibm.commerce.marketing-ext\.
If this folder already exists and it contains a customized version of the wc-admin-component.xml file, or if a customized version exists elsewhere, then open the customized version and skip to the next step; otherwise, complete these substeps:
- Navigate to the default marketing component configuration file at the following path:
WC_EAR\xml\config\com.ibm.commerce.marketing\
- Copy the wc-admin-component.xml file to the new WC_EAR\xml\config\com.ibm.commerce.marketing-ext\ folder.
- Open the copied wc-admin-component.xml in an editor. This copy becomes the customized version of the wc-admin-component.xml file.
- Change any properties as required for the site.
If the customized marketing component configuration file already exists, and to change additional properties that are not currently in the customized file, you can copy those properties into the customized file from the default marketing component configuration file at WC_EAR\xml\config\com.ibm.commerce.marketing\wc-admin-component.xml.
- 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.
- Save and close the customized file.
- To make the changes in the file take effect in the development environment, restart the WebSphere Commerce server.
- To push the configuration changes out to the production environment, see Deploy J2EE assets for a single file.
Related concepts
Marketing component configuration file (wc-admin-component.xml)