Home
User Guide
The information contained in this section applies to IBM WebSphere Commerce Version 7.0.0.9 and Feautre Pack 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in new editions.
Developing
The topics in the Developing section describe tasks performed by an application developer.
Presentation layer
WebSphere Commerce uses Java Server Pages (JSP) to implement the view layer of the Model-View-Controller (MVC) design pattern. The view layer is in charge of retrieving data from the database through the use of data beans and formatting it to meet the display requirements. The view layers determines whether the request is sent to a browser or streamed out as XML. JSP files present a clean separation between data content and presentation.
Customizing content versioning
The content versioning feature is enabled for some objects in the Catalogs tool in Management Center. You can add or remove content versioning support for existing objects and custom objects by customizing both Management Center and WebSphere Commerce server.
Extending the content versioning feature to support additional business objects
You can extend the content versioning feature to support versioning in your own custom objects or in existing WebSphere Commerce objects.
Updating the version schema with custom tables
The updateVersionSchema utility automatically creates the custom tables in the version schema. This utility replicates newly added tables marked to be versioned from the base schema into the version schema.

Updating the version schema with custom tables

The updateVersionSchema utility automatically creates the custom tables in the version schema. This utility replicates newly added tables marked to be versioned from the base schema into the version schema.

Before you begin

Ensure that you have created your custom content versioning configuration file. See Creating a content versioning configuration file for instructions on how to create a custom content versioning configuration file.
Stop the WebSphere Commerce test server.

Procedure

From the command prompt, navigate to WCDE_installdir\bin
Run the updateVersionSchema utility.

Results

Ensure your custom tables are created successfully in the version schema by checking the log file WCDE_installdir\logs\updateVersionSchema.log. The SQL is generated in the file WCDE_installdir\logs\Update_version_db_demo.sql.log.