Web 2.0 client environment

The IBM® WebSphere® Multichannel Bank Transformation Toolkit Web 2.0 client is used for home banking applications or web-based teller applications. Only the web browser is required to run the application on the client machine.

The WebSphere Multichannel Bank Transformation Toolkit Web 2.0 client consists of the Web 2.0 Workplace component and the Web 2.0 Transaction UI component.

The Web 2.0 Workplace

The Web 2.0 Workplace, which responsible for site UI layout, contains a full set of Personalized Internet Banking Package, which is based on HTML, DHTML, JavaScript and CSS, which illustrates fancy User Experience, Personalized Layout, User Contribution and multiple Widget Container Templates (such as iWidget, Google Gadget and Web 1.0 Compatible Widget and so on).

The WebSphere Multichannel Bank Transformation Toolkit Web 2.0 Workplace presents a new User Experience about the web application through the following features:

The following figure is a WebSphere Multichannel Bank Transformation Toolkit Web 2.0 Workplace demo screen:
Figure 1. A WebSphere Multichannel Bank Transformation Toolkit Web 2.0 Workplace demo screen
The figure is BTT Web2.0 Client Demo screen.

The Web 2.0 Transaction UI

Web 2.0 Transaction UI is Dojo-based Web 2.0 page for form-level UI controls.

WebSphere Multichannel Bank Transformation Toolkit provides extensions of Dojo Dijit controls, which exploit properties defined through WebSphere Multichannel Bank Transformation Toolkit tools to provide client-side validation, AJAX communication, event handling, and widget manipulation.

Web 2.0 Transaction UI pages and logic can be defined by using the following features that are provided by WebSphere Multichannel Bank Transformation Toolkit version 8.0:
  • Using HTML table to manage dojo control layout
  • Dojo widget support, including Label, Image, TextBox, TextArea, Button, CheckBox, RadioButton, Anchor, ComboBox, RichTextEidtor, Form, Grid, Tree, Error Message Widget, and so on.
  • Support for Dojo-based UI screen flows and data sharing between different pages.
  • Support for form submission and AJAX submission through Dojo-based UI. AJAX form support enables data to be sent from forms to a server asynchronously and enables forms to be updated with response data without requiring the entire page to be refreshed. This reduces the response time and improves interactivity with the end-user.
  • Support for both client side and server side validation and error messages. Client-side validation, including support for optional or mandatory entries, range-based, mask-based and minimum/maximum length entries. Whenever a validation error is detected, immediate feedback is provided through flexible validation messages. The error messages can be placed anywhere in the input form or presented as a popup dialog.
  • Support for client side Dojo-based NLS mechanism. Internationalization support through components that are aware of the end-user location and the format of user input; for example, when presenting dates or numerical amounts.
  • File upload support. Client and server side components support the sending of files from the client workstation to the server.
  • ECA rule parser to adopt zero code event handling rules. The ECA rules can be used to define complex cross-validation behavior, such as enabling input fields and making the input fields mandatory depending on the value of other fields. For example, a Marital status field can be validated and a Spouse data input section can be configured to be mandatory if a value of married has been selected in the Marital status field.
Figure 2 shows a sample page from a checkout flow in an account opening that was created with WebSphere Multichannel Bank Transformation Toolkit version 8.0:
Figure 2. A sample page created with WebSphere Multichannel Bank Transformation Toolkit version 8.0