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 price rules
You can customize price rules to suit the business needs of your site. For example, you can create a new condition or action for business users to add to price rules. Customization is supported for both the Price Rule Builder tool user interface in the Catalog Filter and Pricing tool, and for the pricing services.
Customizing conditions and actions in price rules
To provide business users with more options for price rules, you can create new conditions and actions to use in the Price Rule Builder in Management Center.
Adding a new custom condition or action for a price rule
Add a customized condition or action element to the Price Rule Builder if the default price rule elements in Management Center do not meet your business needs. When your customization is complete, business users can use the new price rule element in price rules.
Creating the price rule element template definition
By creating the price rule element template definition, you define the blueprint for your price rule element. When you have defined the price rule runtime XML you require, you must add the template definition to the PRELETEMPLATE table as a new entry.
Example: price rule element template for a condition
When creating a custom condition for a price rule, you can refer to this sample SQL statement that adds an element template to the PRELETEMPLATE table.

WebSphere Commerce Enterprise

Introduced in Feature Pack 2

Example: price rule element template for a condition

When creating a custom condition for a price rule, you can refer to this sample SQL statement that adds an element template to the PRELETEMPLATE table.

Sample

The purpose of the condition in this sample is to determine if the customer registered on, before, or after a specific date. The business user can then specify a condition such as customer registered after October 31, 2010. The SQL statement looks like this:

INSERT INTO PRELETEMPLATE (preletemplate_id, identifier, storeent_id, description, preletpltgrp_id, runtimexml ) 
VALUES 
(1001,'RegistrationTimeCondition',0,'Shopper registration time condition',2,
'<FlowElementImplementation type="RegistrationTimeCondition">
<Implementation invocationType="TaskCommand">
<Class name="com.mycompany.commerce.price.rule.commands.element.RegistrationTimeConditionElementCmd">
<Argument name="registrationTime" value="PRICERULE_registrationTime"/>
<Argument name="registrationTimeOperator" value="PRICERULE_registrationTimeOperator"/>
</Class></Implementation></FlowElementImplementation>');

For this example, the PRICERULE_registrationTime parameter in the element template definition will be replaced with the actual date (for example, "2010/11/15") when the price rule is used on the storefront to set pricing.