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
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.
Command types
WebSphere Commerce commands are Java beans that contain the programming logic associated with handling a particular request. Commands perform a specific business process, such as adding a product to the shopping cart, processing an order, updating a customer's address book, or displaying a specific product page.
Controller command programming model
The abstract class and interface are both found in the com.ibm.commerce.command package.
Long-running controller commands
If a controller command takes a long time to execute, you can split the command into two commands. The first command, which is executed as the result of a URL request, simply adds the second command to the Scheduler, so that it runs as a background job.

Long-running controller commands

If a controller command takes a long time to execute, you can split the command into two commands. The first command, which is executed as the result of a URL request, simply adds the second command to the Scheduler, so that it runs as a background job.

Diagram illustrating the flow between ControllerCommand1, Scheduler, and ControllerCommand2 explained in the following paragraph.

The flow shown in the preceding diagram is as follows:

ControllerCommand1 is executed as a result of a URL request.
ControllerCommand1 adds a job to the Scheduler. The job is ControllerCommand2. ControllerCommand1 returns a view, immediately after adding the job to the Scheduler.
The Scheduler executes ControllerCommand2 as a background job.

In this scenario, the client typically polls the result from ControllerCommand2. ControllerCommand2 should write the job state to the database.