Application changes when you enable content versioning

Enabling content versioning changes a number of files and database tables.

When you enable content versioning:

Changes to the EAR file when content versioning is enabled

The following changes occur:

The following new files or modules are added to the EAR file after you enable content versioning.

properties\version\install\7.0.0.0\backup\componentmaps\componentmap.content-version.server.70.be.xml
properties\version\install\7.0.0.0\backup\componentmaps\componentmap.content-version.server.70.xml
properties\version\install\7.0.0.0\backup\content-version.server.70\files.list
properties\version\install\7.0.0.0\backup\content-version.server.70.be\files.list
properties\version\install\7.0.0.0\backup\nif.componentmap.content-version.server.70\files.list
properties\version\install\7.0.0.0\backup\nif.componentmap.content-version.server.70.be\files.list
properties\version\content-version.server.70.be.component
properties\version\content-version.server.70.component xml\config\com.ibm.commerce.catalog-fep\wc-content-version.xml
xml\config\xsd\wc-content-version.xsd

New tables

Enabling content versioning creates the following new tables:

Existing tables

Enabling content versioning does not alter any existing tables.

New indexes

Enabling content versioning does not create any indexes.

New triggers

Enabling content versioning does not create new triggers.

New keys

Enabling content versioning creates the following keys: