You create a content versioning configuration
file in your service module directory for each custom object you want
versionable. This file defines the configuration for the UI objects
that are versionable and what parts of the UI objects to save when
a version is created.
Procedure
- Open
WebSphere Commerce Developer and switch to the Enterprise Explorer
view.
- In the Enterprise Explorer view, expand ;
where servicemoduleDir is your service module directory.
For example, com.mycompany.commerce.project.
- In the servicemoduleDir folder, create
the custom configuration file.
- Right-click the servicemoduleDir folder;
then click
- In the Name field, type wc-content-version.xml.
Note: You must name your content versioning
configuration file wc-content-version.xml.
- Add the following code snippet into the custom configuration
file:
<?xml version="1.0" encoding="UTF-8"?>
<wc:ContentVersionConfiguration xmlns:wc="http://www.ibm.com/xmlns/prod/WebSphereCommerce"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.ibm.com/xmlns/prod/WebSphereCommerce ../../content-version/xsd/wc-content-version.xsd">
All
configuration files start with the preceding code snippet.
- Build your custom configuration file. For detailed information
about the content versioning configuration file, see Content Versioning configuration file (wc-content-version.xml).
- Add the
</wc:ContentVersionConfiguration>
tag
to the end of your custom configuration file. - Save and close the custom configuration file.