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.
Deploying customizations to the IBM Sales Center
Depending on the number of clients and frequency of updates required, you have several choices for installing and updating the IBM Sales Center.
Building customizations for deployment in Rational Application Developer
All of the recommended mechanisms suitable for custom IBM Sales Center extension deployment and service depend on packaging those extensions as Eclipse update sites.
Automating builds in Rational Application Developer
After the projects are created, they can be built in an automated build that uses the runAnt capability to run Rational Application Developer without a user interface.

Automating builds in Rational Application Developer

After the projects are created, they can be built in an automated build that uses the runAnt capability to run Rational Application Developer without a user interface.

Rational Application Developer provides Ant tasks to create build.xml files for each feature and plugin, and to generate and export JAR files suitable for an update site. However, there is not an Ant task equivalent to the Build all button that the site.xml editor provides. For detailed instructions on how to create an automated build of features and plugins, and to construct an update site from the result, see Build and Test Automation for plug-ins and features.