To change any properties in the order 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.
About this task
Use this procedure if you want to modify the wc-admin-component.xml file
that is in the following directory:WC_eardir\xml\config\com.ibm.commerce.order-fep\
Procedure
- Open
WebSphere Commerce Developer and switch to the Enterprise Explorer
view.
- Create a com.ibm.commerce.order-fep-ext folder
for your customized order component configuration file at the following
path:
WC_eardir\xml\config\
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 or contain
a customized version, complete these substeps:
- Navigate to the default order component configuration
file at the following path:
WC_eardir\xml\config\com.ibm.commerce.order-fep\
- Copy the wc-admin-component.xml file
to the new WC_eardir\xml\config\com.ibm.commerce.order-fep-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
your site.
If your customized order 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 order component
configuration file at WC_eardir\xml\config\com.ibm.commerce.order-fep\wc-admin-component.xml.
- Remove any properties that are not set differently from
the default order component configuration file. The customized file
must contain only the differences.
- Save and close the customized file.
- To update the changes in a development environment, start,
or restart the WebSphere Commerce server.
- If you want to push the configuration changes out to the
production environment, see Deploying J2EE assets for a single file.