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.
Creating the campaign element template definition
By creating the campaign element template definition, you define the blueprint for your campaign element. When you have defined the XML you require, you must add the template definition to the DMELETEMPLATE table as a new entry.
Example: campaign element template for a trigger
When you create a custom trigger for a marketing activity, you can refer to this sample when you create the trigger's campaign element template.

Example: campaign element template for a trigger

When you create a custom trigger for a marketing activity, you can refer to this sample when you create the trigger's campaign element template.

WebSphere Commerce Professional WebSphere Commerce Enterprise Dialog activities are available only in the Professional and Enterprise editions of WebSphere Commerce.

Sample

Here is the SQL statement to add the campaign element template code for an example trigger to the DMELETEMPLATE table. In this example, an external system detects credit fraud. The external system can detect credit card fraud, or credit account fraud. The external system sends a message to the marketing runtime that one of these occurrences of fraud occurred for a customer. Using this customized trigger, a Marketing Manager would be able to create a Dialog activity to specify how to follow up with the customer in this situation (for example, send a mobile text message or an email, depending on their level of coverage, and then send a follow-up message after a certain time).

This campaign element template has an implementation definition and a behavior rule definition.

insert into dmeletemplate (dmeletemplate_id, dmelementtype_id, name, implxml, behaviorxml) 
values 
(1003, 1, 'Custom Fraud Detected Trigger',
'<Trigger type="customFraudDetectedTrigger">
<Implementation invocationType="TaskCommand">
<Class name="com.mycompany.CustomFraudDetectedTriggerTaskCmd">
</Class>
</Implementation>
</Trigger>',  
'<BehaviorRule 
command="CustomFraudDetectedTriggerEvent" 
action="send" 
comparison="=">
<Variable 
name="eventType" 
value="MARKETING_eventType" 
type="NVP"/>
</BehaviorRule>');