Feature Pack 7

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:
  • No files are deleted from the WebSphere Commerce EAR file
  • Files are added to the WebSphere Commerce EAR file
  • Files are changed in the WebSphere Commerce EAR file
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

Files changed in the WebSphere Commerce EAR file

The following existing files are changed in the WebSphere Commerce EAR file:
  • META-INF\ibmconfig\cells\defaultCell\applications\defaultApp\deployments\defaultApp\deployment.xml
  • META-INF\ibm-application-runtime.props

Changes to the database when content versioning is enabled

New tables

Enabling content versioning creates the following new tables:
  • CMVERSNINFO
  • CMACTVERSN
  • CMVERSNCOLL
  • CMVERSNCOLLREL
  • CMVERSNCHGLOG

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 any triggers.

New keys

Enabling content versioning creates the following keys:
  • FCM_ATCHREL
  • FCM_ATTRIBUTE
  • FCM_ATTRVAL
  • FCM_ATTRVALDESC
  • FCM_ATTRVALUE
  • FCM_CATALOG
  • FCM_CATALOGDSC
  • FCM_CATCONFINF
  • FCM_CATENTDESC
  • FCM_CATENTDESCOVR
  • FCM_CATENTREL
  • FCM_CATENTRY
  • FCM_CATENTRYATTR
  • FCM_CATENTSHIP
  • FCM_CATENTSUBS
  • FCM_CATGPENREL
  • FCM_CATGROUP
  • FCM_CATGRPDESC
  • FCM_CATGRPREL
  • FCM_CATTOGRP
  • FCM_CMACTVERSN_0
  • FCM_CMVERSNCOLLREL_0
  • FCM_CMVERSNCOLLREL_1
  • FCM_DKPDCCATENTREL
  • FCM_DKPDCCOMPLIST
  • FCM_DKPDCDESC
  • FCM_DKPREDEFCONF
  • FCM_LISTPRICE
  • FCM_MASSOCCECE
  • FCM_STORECAT
  • FCM_STORECENT
  • FCM_STORECGRP