Changing properties in the component configuration file (wc-component.xml) (WC EAR)

To change any properties in the component configuration file (wc-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 search-related properties that this file contains, see Search properties in the component configuration file (wc-component.xml) (WebSphere Commerce EAR).


  1. Open WebSphere Commerce Developer and switch to the Enterprise Explorer view.
  2. Create a custom component configuration file (wc-component.xml), if one does not exist:
    1. Go to the following path:


    2. In the config folder, create a new folder so the path looks like this:


      If this folder exists and it contains a customized version of the wc-component.xml file, then open the file and skip to step 4.

    3. Create an empty wc-component.xml file in the folder. This file is your custom wc-component.xml file.
  3. Add the basic XML elements that are required for your custom wc-component.xml file:
    1. Open your empty custom wc-component.xml file in an XML editor.
    2. Copy the following code into the file:
      <?xml version="1.0" encoding="UTF-8"?>
      	xsi:schemaLocation=" ../xsd/wc-component.xsd "
  4. Add the XML for any properties that you want to change to your custom wc-component.xml file:
    1. Go to the default component configuration file at the following path:


      Never change properties directly in this file because your changes will be overwritten with future IBM software updates.

    2. Copy the XML elements for the properties you want to change from the default component configuration file to your custom wc-component.xml file. Insert the copied XML elements after the <_config:extendedconfiguration> element.

      Even though you are copying only certain elements, you must maintain the XML hierarchy for those elements in the file. For example, if you want to change the property that is defined in a specific <_config:property> element, you must retain the parent and ancestor elements of the <_config:property> element, but you can delete all the siblings if you are not changing them. You must also maintain the ordering of the siblings, as they are expected in the same order that they appear in the default configuration file. See the example at the end of this topic.

    3. Change the values for the copied properties as required.
  5. Save and close the custom configuration file.
  6. Test your configuration changes.
  7. Deploy the customized file to the production environment.


The following example shows the contents of a custom catalog component configuration file that changes search configuration properties:

<?xml version="1.0" encoding="UTF-8"?>
xmlns:xsi = "" 
xsi:schemaLocation = " ../xsd/wc-component.xsd " 
xmlns:_config = "">

      <_config:configgrouping name = "SearchConfiguration">

            <_config:property name = "SearchProfilesStatistics" value = "true"/>
            <_config:property name = "SearchStatisticsUpdateInterval" value = "4800"/>
            <_config:property name = "SearchStatisticsResultPagesTrackingThreshold" value = "2"/>


In the previous example, the code snippet that starts with A and ends with B is the inserted code, which contains the following properties:
  • SearchProfilesStatistics: The value is changed to true to enable site search statistics.
  • SearchStatisticsUpdateInterval: The value is changed to 4800 seconds as the time interval between batch processing updates.
  • SearchStatisticsResultPagesTrackingThreshold: The value is changed to 2 search results pages to track search rule statistics.