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:
- User interface and user experience
- Enable the end user to customize the internet banking workplace
service and user interface (UI), and different end users have their
own internet banking workplaces.
- Provides a workplace that is entirely based on XML.
- CSS Binding User Interface feature. WebSphere Multichannel Bank
Transformation Toolkit Web
2.0 Workplace Definition XML binds CSS, which
makes managing the UI easier.
- Multiple Window Support. Users can open multiple windows by using
tabs in the same browser.
- Services
- A subscription mechanism. End users can subscribe services that
he or she is interested in.
- An XML-based service deployment mechanism. The new service can
be deployed to the end user. If the bank provides a new service, just
edit the Service List XML file, and the end user can subscribe to
the service. It is never-release programming model.
- Follow the iWidget Standard, and provide widget runtime and some
predefined widgets. Developers can also extend to develop their own
widget. And WebSphere Multichannel Bank
Transformation Toolkit widget
definitions can be used in IBM Lotus® Mashup.
- Enable Cross Selling through the service subscription mechanism.
A Recommend Service List for cross selling can be provided for each
user.
- In the transaction UI and Web 1.0. compatible widget implementation
is provided to execute or display traditional Web 1.0 applications.
- Security
Support HTTPS
When a user visits the start page
of the internet banking and logs in, a menu with a list of available
services is displayed in the browser. The user can select any service
that he or she is interested in, and then add it to his or her internet
banking home page. The sequence of the events in runtime are as follows:
- Besides the service list, the page layout consists of four main
areas, the title area, the tab area, the column area and the footer
area. This personalized information is kept in XML format.
- Users can use the Tab Management to classify the content. Create
the new tag or remove the old one, such as, stocks or transactions.
- Users can manage the column to organize the content. Add new columns
in a window, or remove old columns.
Remember: If a column
is removed, all widgets contained in this column are destroyed.
- Users can change the UI Style conveniently with CSS Binding. The
style includes color, font color and size and so on.
- Service Deployment and Subscription. All the services which the
bank provides to customers are displayed in the service list. Users
can look up their interested category from the service list.
- Users can manage the service module in the page. They could minimize
maximize or close the service module.
- Users can drag and drop modules between column areas in the page.
- Communication between the two widgets (80 H). Widgets can communicate
with each other. If one widget wires event, another widget can capture
it if registered.
- Describe the service by XML. WebSphere Multichannel Bank
Transformation Toolkit Server
keep record of each single user's layout XML file which records the
user's unique perspective. Next time when the user login again, the
personalized home page will be restored again.
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 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