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.
Image installation mechanisms
Technology is available from Microsoft and from external vendors to create an installable image of a preconfigured Windows XP system. The image can be installed on compatible hardware, creating a clone of the original system including any installed applications.
Tivoli Configuration Manager Pristine Service
Users of Tivoli Configuration Manager can take advantage of its Pristine Manager component which integrates Tivoli support with Microsoft Remote Installation Services. Pristine Manager uses the images on Microsoft Remote Installation Services (RIS) servers to install them on the bare target machines. At the same time, Pristine Manager includes the machines in the Tivoli environment as Endpoints, which enables the Tivoli Change Manager and Activity Plan Monitor services to work with the machines as Tivoli endpoints after the pristine installation is complete.

WebSphere Commerce Enterprise

WebSphere Commerce Professional

Tivoli Configuration Manager Pristine Service

Users of Tivoli Configuration Manager can take advantage of its Pristine Manager component which integrates Tivoli support with Microsoft Remote Installation Services. Pristine Manager uses the images on Microsoft Remote Installation Services (RIS) servers to install them on the bare target machines. At the same time, Pristine Manager includes the machines in the Tivoli environment as Endpoints, which enables the Tivoli Change Manager and Activity Plan Monitor services to work with the machines as Tivoli endpoints after the pristine installation is complete.

In Pristine Manager, the user defines the servers that have the images and the machines on which they will be installed. They specify the operating system element and the targets, which creates a connection among the operating system to be installed, the target pristine machines, and the servers. Then, this information is used to create an activity plan that is used by Activity Planner to do the installation.

The advantages of using Pristine Manager are:

The ability to perform remote, unattended image installations
The ability to reinitialize machines that are already configured, for example, to reinstall the operating system or a new operating system from scratch.
A Tivoli Endpoint is automatically installed on the target machine.

In order to use Pristine Manager successfully, the following prerequisites must be met:

The RIS server is already installed, configured, and working.
There is a Tivoli endpoint on the machines where the RIS server is installed.
The images are already created on the RIS server. Refer to the appropriate RIS documentation for instructions.
On the RIS server directory with the binary files to install the Tivoli endpoint. The directory must be shared and have full-control permissions.