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.
Service request handlers
The IBM Sales Center service request extension point is the mechanism by which requests are made of the server and the request results are handled and the model is updated. The class that constructs the request and interprets the response is the request handler.

Service request handlers

The IBM Sales Center service request extension point is the mechanism by which requests are made of the server and the request results are handled and the model is updated. The class that constructs the request and interprets the response is the request handler.

Each type of service request in the IBM Sales Center has its own service request handler. If you want to customize the Business Object Document (BOD) format, you will need to create a subclass and customize this class. All service request handlers are defined in the com.ibm.commerece.telesales.core.impl plug-in manifest file (plugin.xml). The plug-in manifest file has the list of service requests and the corresponding request handler class, as well as the communication service ID.