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.
Deploying the custom object content versioning customization
After you have customized content versioning to support your custom object, you are ready to deploy the customization to your WebSphere Commerce Server.

Deploying the custom object content versioning customization

After you have customized content versioning to support your custom object, you are ready to deploy the customization to your WebSphere Commerce Server.

Procedure

Package and deploy your custom changes. See the instructions in Packaging Java EE assets for a partial application and Deploying Java EE assets for a partial application.
Alternatively, you can deploy your custom changes by using the WebSphere Commerce Build and Deployment tool.
Ensure that your custom content versioning configuration file is placed in the WC_installdir\instances\demo\xml\config\servicemoduleDir directory; where servicemoduleDir is your service module directory.
Run the UpdateVersionSchema utility in the runtime environment.
If you have workspace enabled, run Ant target: CM_updateWorkspacesSchema to update the workspace schema with any content versioning base schema changes.