Chapter 12. Pay-As-You-Drive 307
In order to handle high traffic networks, IBM WebSphere Everyplace Wireless
Gateway can be implemented in a clustered environment. Clustering means that
several machines are running one instance of the IBM WebSphere Everyplace
Wireless Gateway software. Workload from one or more network connections are
distributed across them.
Load balancer and caching proxies should be used to achieve high availability of
WebSEAL and content servers.
12.6.1 Integration into existing infrastructure
The security infrastructure based on the Access Manager infrastructure and
WebSEAL is expanded by integrating the WAP gateway into the authentication
Because of the lack of heavy transactional processing, transcoding of different
back-end content will not be used in the first step, so YRI decided to develop the
required WML coding (for example, WML forms) on its own. But YRI is already
thinking of deploying new services to its clients and of course integrating
pervasive computing models like intelligent cars. Therefore a transcoding model,
as discussed in Chapter 18, “Wireless integration” on page 477, is also suitable
for future services.
YRI already plans future enhancements like intelligent notification and
location-based services for its clients using WebSphere Everyplace Server as a
platform (see Appendix A, “IBM WebSphere Everyplace Suite - An overview” on
We have shown in this scenario that a given infrastructure can be extended to
meet new business requirements. To assure secure access for mobile devices
today’s WAP environment and its WTLS support is already suitable to provide a
certain level of wireless security.
The main requirement to use WebSEAL as the focal point for authentication and
authorization issues is met using the features of WebSEAL to connect to WAP
gateways in a secure way and to assure that no other back-end resources than
the required ones can be accessed.