As shown in Figure 51 on page 58, the order page can be reached from the
book abstract page or directly to the order page if you know the form number.
A successful order will display an order number and the shipping details.
Failures will again result in an error message and further instructions being
3.2 Internal design
Our Web application structure is then developed to be able to provide the
presentation flow discussed in Section 3.1, External functionality on page
53. As we have also decided to use the pattern for e business user to online
buying topology, the application is then developed to include a Commerce
server node in the front end and a Database server node in the backend. The
front end runs the Web server and the business logic using WebSphere,
while the backend contains the data. Figure 53 shows our internal
Commerce server node
Figure 53. Internal configuration
The design is started from the Database server structure. We use two data
sources, the DB2 database to store the order and user profiles and the Lotus
Domino database to store the book information. The structure of the DB2
database is given in Section 3.3, DB2 database on page 61. The discussion
on the Lotus Domino's redbook database is given in Section 3.4, Domino
database on page 69.
The Commerce server node is implemented using RedHat Version 6.2 and
Caldera eDesktop Version 2.4. The HTML codes that we used are available in
Appendix D, HTML and JSP files listing on page 173. We describe, in this
Linux Web Hosting with WebSphere, DB2, and Domino