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 WebSphere Commerce Accelerator, Organization Administration Console, or Administration Console
The WebSphere Commerce browser-based tools (WebSphere Commerce Accelerator, Organization Administration Console, Administration Console) can be extended or changed. In addition to customizing the tools you can also create a new browser-based tool that uses the same underlying framework. A new tool based on the tools framework is referred to as a WebSphere Commerce tools user interface center.
Customizing product management tools for WebSphere Commerce Accelerator
You can customize the product management tools within WebSphere Commerce Accelerator to add enhancements to help business users work more efficiently.
Creating a merchandising association type
By default, WebSphere Commerce displays four merchandising association types: cross-sell, up-sell, accessory and replacement. You can create your own merchandising association types, based on your business needs. The following instructions work for both the development and production environments. You should test your changes in the development environment before propagating them to your production environment.
Creating a merchandising association semantic
By default, WebSphere Commerce displays four merchandising association semantics: comes_with, none, requires, or temp. You can create your own merchandising association semantics, based on your business needs. The following instructions work for both the development and production environments. You should test your changes in the development environment before propagating them to your production environment.
Adding a merchandising association semantic to the database
By default, WebSphere Commerce displays four merchandising association semantics: comes_with, none, requires, or temp. You can create your own merchandising association semantics, based on your business needs. You can add a merchandising association semantic by manually inserting information into the database.

Adding a merchandising association semantic to the database

By default, WebSphere Commerce displays four merchandising association semantics: comes_with, none, requires, or temp. You can create your own merchandising association semantics, based on your business needs. You can add a merchandising association semantic by manually inserting information into the database.

Procedure

Connect to the database.
Run the following command:
```
insert into massoc (massoc_id, description) values
('yourCustomMASemantic',
'yourCustomMASemanticDescription')
```
Where:

yourCustomMASemantic

is the merchandising association type and yourCustomMASemanticDescription is the custom merchandising association semantic description.
For example, to insert a merchandising association called recommended, run the following command:
```
insert into massoc (massoc_id, description) values ('Recommended', 'Recommend another product.')
```
The new merchandising association semantic displays the next time you load the Merchandising Association page in the WebSphere Commerce Accelerator.
Optional: Add translations of the new custom merchandising association semantic.