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.
Deleting a merchandising association type
You can delete any custom merchandising association type you created. Do not delete the following default merchandising association types: cross-sell, up-sell, replacement and accessory.

Deleting a merchandising association type

You can delete any custom merchandising association type you created. Do not delete the following default merchandising association types: cross-sell, up-sell, replacement and accessory.

Procedure

Ensure there are no existing merchandising associations of the type you want to delete. If you delete a merchandising association type, any existing merchandising associations using that type will also be deleted. If this situation is acceptable to you, skip this step. Otherwise:
1. From a database command window, find the massoctype_id by running the following command: select massoctype_id from massoctype. Find the massoctype_id in the resulting list.
2. Check for existing merchandising associations between catalog entries by running the following command:
```
select * from massoccece where massoctype_id='massoctype_idFoundInStep_a'
```
3. Check for existing merchandising associations between categories by running the following command:
```
select * from massocgpgp where massoctype_id='massoctype_idFoundInStep_a'
```
4. For any records found in steps b and c, change the type of merchandising association to a merchandising association which you will not delete.
Stop your WebSphere Commerce Server.
Connect to the database.

Run the following command:

delete from massoctype where massoctype_id=' massoctype_idFoundInStep_a'

Start your WebSphere Commerce Server.