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.
Business logic layer
The business logic layer is the business components that provide OAGIS services to return data or start business processes. The presentation layer uses these OAGIS services to display data, or to invoke a business process. The business logic provides data required by the presentation layer. The business logic layer exists because more than just fetching and updating data is required by an application; there is also additional business logic independent of the presentation layer.
Name-value pair command framework
The name-value pair framework is the only command framework that existed in releases of WebSphere Commerce Version 6, prior to Feature Pack 3.0.1. This command framework uses name-value pairs as input to the business logic layer, and returns the responses as name-value pairs.
Customizing existing controller commands
A controller command encapsulates the business logic for a business process. Individual units of work within the business process may be performed by task commands. As such, there are several ways in which a controller command can be customized, some of which involve customizing task commands.
Replacing task commands called by a controller command
Replacing task commands allows you to modify how a particular step in the business process is performed. A controller command often calls several task commands that perform individual tasks. Collectively, these tasks make up the business process represented by the controller command. You may need to change the way in which a particular step in the process is performed, rather than adding new business logic to the beginning or end of the controller command. In this case, you must replace the implementation of the task command that you want to override, with the implementation of a new task command that performs the task in your desired manner.

Replacing task commands called by a controller command

Replacing task commands allows you to modify how a particular step in the business process is performed. A controller command often calls several task commands that perform individual tasks. Collectively, these tasks make up the business process represented by the controller command. You may need to change the way in which a particular step in the process is performed, rather than adding new business logic to the beginning or end of the controller command. In this case, you must replace the implementation of the task command that you want to override, with the implementation of a new task command that performs the task in your desired manner.

About this task

As a result of the design of the WebSphere Commerce programming model, you do not need to create a new controller command implementation class to replace the task command. The controller command instantiates the task command by calling the command factory's createCommand method. The command factory uses the task command's interface name and then determines the correct implementation class, based upon the command registry. As such, to replace the task command that gets instantiated, you must create a new task command implementation class and then update the command registry so that the original task command interface name is associated with the new task command implementation class. Refer to Customizing existing task commands for more information.