To support the application's HTML client requests on the server,
the toolkit requires the following things:
- ProcessorOperation interface to provide a front-end layer between the
request from the client workstation and the processor responsible for controlling
the navigation dialog. The following diagram shows the role of the ProcessorOperation
implementation:
- Definitions for the operations required to perform the main business transactions.
These include definitions for toolkit entities such as contexts and formats.
- Definitions for the actions for executing operations. These actions must
be able to signal an error event when the result of executing a business operation
halts further user interaction. The processor can use this event to display
an information message to the user. For example, the processor should display
a message when an action retrieves a list of accounts but the operation cannot
use them due to constraining business rules. Note that the toolkit provides
a default action with this functionality, ExecuteOperationAct, in the com.ibm.btt.automaton.ext
package.
- Input validation of the PIN number using a subclass of DSEGuardCondition.
The subclass validates the PIN and returns true or false. For an incorrect
PIN, the subclass should leave data in the process context so that the confirmation
page can display an informative warning message for the user.
- JSP pages for rendering the views in a Web browser.