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 marketing
Marketing customization: Management Center
There are many aspects of the Marketing tool you can customize to suit the business needs of your site. For example, you can customize Web and Dialog activities, the Activity Builder user interface, e-Marketing Spots, and customer segments. Customization is supported for both the Marketing tool user interface and the marketing services.
Customizing triggers, targets, and actions
To provide business users with more options for Web and Dialog activities, you can create new triggers, targets, and actions to use in the Activity Builder for the Marketing tool. You can also change the behavior of existing triggers, targets, and actions.
Marketing activity data storage and process flow
If you are customizing triggers, targets, and actions, you must know which database tables store data about marketing activities. In addition, you should understand what is happening behind the scenes when customers are experiencing your marketing activities. This knowledge helps you understand what you need to create or change to support a customized trigger, target, or action.
Process MarketingTriggers service
The Process MarketingTrigger service is used in Dialog activity processing to notify the marketing services that specific events occurred.

Process MarketingTriggers service

The Process MarketingTrigger service is used in Dialog activity processing to notify the marketing services that specific events occurred.

This service performs the following functions:

Evaluates the information that is provided in the marketing trigger against the behavior rules in currently active activities. If the marketing trigger event matches the behavior rule definition, then the marketing services perform the corresponding action in the behavior rule:
- send: Forward the occurrence of this event to the marketing services to be processed. Examples of customer events are: the customer places an order, or the customer registers with the store, or the time that is specified in a Wait trigger elapses for the customer.
- record: Forward the occurrence of this event to the marketing services so that the behavior is recorded for a customer. Examples of recorded customer events are: the customer browsed a category, or the customer viewed a page with a URL containing a specific name-value pair.
- custom: Detect the occurrence of this event, but do not forward the event to the marketing services. When action=custom, a custom task command handles the processing of this event. Some customization scenarios might use this value to detect events but then record the data by using some other means.
Updates the statistics when a customer clicks an e-Marketing Spot.