IBM WebSphere V5.0 Security - CGISecurity

Client
Tier
Synchronous
Application
Synchronous Application 1
Asynchronous
Application 2
Figure 11-2 Self-Service:: Directly Integrated Single Channel application pattern
The primary business driver that directed the use of this pattern is to reduce
business process latency by providing direct access to back-end application and
data from the Web-enabled business process.
This pattern provides a structure for point-to-point connection from the client
browser to one or more applications. We do not need multiple channel
integration mechanisms. Although this Application pattern can be used to
implement any one of the delivery channels, we only focus our design on the
Web delivery channel.
This Application pattern requires applications to be divided into three different
logical tiers: presentation, Web application and back-end business logic. Data
can be accessed from both Web and business tiers. We can have in mind any
typical J2EE structure while selecting this pattern.
►
►
►
The presentation tier is responsible for all the application presentation logic.
In the Web application tier, some of the application business logic is done and
all the communication to the back-end business logic is implemented.
Back-end application logic in our case covers data access functions of the
ITSOBank application. Here, are all the application integration interfaces are
implemented as well.
All the communication between tiers is either synchronous or asynchronous.
11.2.2 Application pattern for the Access Integration pattern
The main goal of the Access Integration pattern is to give users a consistent and
seamless front-end access mechanism to multiple business applications that
reside on multiple servers, each with its own access mechanism.
In our ITSOBank example, we have chosen the Extended Single Sign-On
application pattern.
354 IBM WebSphere V5.0 Security Handbook