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.
Adding a new trigger, target or action
Add a new campaign element to the Activity Builder if the default campaign elements do not meet your business needs. You can then use the new campaign element in marketing activities.
Informing the marketing services of an external event for a trigger or target
If your custom trigger or target must detect an event that occurs on system that is external to WebSphere Commerce, then you must inform the marketing services of that event. To do so, call the Process MarketingTrigger service using a URL or using Java code. If your trigger or target detects a WebSphere Commerce event (or no event), you do not need to do this task.

Informing the marketing services of an external event for a trigger or target

If your custom trigger or target must detect an event that occurs on system that is external to WebSphere Commerce, then you must inform the marketing services of that event. To do so, call the Process MarketingTrigger service using a URL or using Java code. If your trigger or target detects a WebSphere Commerce event (or no event), you do not need to do this task.

Before you begin

Read Ways to inform the marketing services of external or custom events for triggers and targets.

Procedure

Determine the best way to call the Process MarketingTrigger service to inform the marketing services of the external event.
To ensure the marketing services have the customer's personalization ID available for the marketing activity:
1. Provide an implementation of MarketingServicesTaskCmd that implements the method getPersonalizationId. This method must map from the external identifier of the customer to the WebSphere Commerce identifier for the customer (personalizationId).
2. Register the task command in the CMDREG table.
  Here is an example of the SQL statement to register this type of task command:
```
INSERT INTO CMDREG (STOREENT_ID, INTERFACENAME, CLASSNAME) VALUES (0, 
'com.ibm.commerce.marketing.dialog.util.MarketingServicesTaskCmd', 
'com.mycompany.marketing.dialog.util.MyCompanyMarketingServicesTaskCmdImpl');
```
Implement the Process MarketingTrigger service call from the external system using either a URL or Java code.