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 IBM Sales Center
In the IBM Sales Center for WebSphere Commerce there is a set of user interface panels, views and dialogs that contain the most commonly used features. You can add to or configure the user interface to suit your needs, as well as changing the content and format of the data that is passed between the client and the server.
Online help
The online help is defined using the base Eclipse extension point org.eclipse.help.toc. Put your new help documentation in a new plug-in.
Replacing the default table of contents
To replace the default table of contents with your own table of contents:

Replacing the default table of contents

To replace the default table of contents with your own table of contents:

Procedure

Define the new table of contents using the org.eclipse.help.toc extension point.
Disable the default IBM Sales Center help by adding the following line to the System configurator extension point:
```
com.ibm.commerce.telesales.doc=null
```

Results

This will disable the com.ibm.commerce.telesales.doc plug-in. Note that this plug-in just contains the primary table of contents entries which link to the secondary table of contents entries defined in the com.ibm.commerce.telesales.tsr.doc plug-in. When defining a new table of contents in a customization plug-in, use the same strategy and link to the secondary table of contents entries in com.ibm.commerce.telesales.tsr.doc where appropriate.