The connection manager allows you to connect and disconnect to a data
server more efficiently by pooling connections and reusing them. This
reduces the overhead of connecting and disconnecting. The servlets use the
connection pool as follows:
When a user makes a request over the Web to a servlet, the servlet uses
an existing connection from the pool, meaning the user request does not
incur the overhead of a data server connection.
When the request is satisfied, the servlet returns the connection to the
connection manager pool for use by other servlets.
The user request, therefore, does not incur the overhead of a data server
The connection manager also allows you to control the number of concurrent
connections to a data server product. This is very useful if the data server
license agreement limits you to a certain number of concurrent users.
There is a good introduction to connection manager in the WebSphere
documentation under the IBMWebAS directory. In our bdtest1 system, it is at
18.104.22.168 User profile tracking
The WebSphere Application Server has an API, called UserProfile, that
makes it easy to maintain persistent information about your Web site visitors.
The UserProfile enables you to store the user's data in a database without
coding any SQL.
The UserProfile contains the interface to store the user's personal data, such
as name, postal and e mail addresses, telephone numbers, and shopping
cart information. For further information, see the UserProfile API Reference in
the WebSphere documentation under the IBMWebAS directory. In our bdtest1
system, it is at URL:
5.1.2 IBM HTTP Server
The following advanced features of IBM HTTP Server are available but not
utilized in our project:
Section 22.214.171.124, SSL on page 141
Section 126.96.36.199, Caching and dynamic pages on page 141
Linux Web Hosting with WebSphere, DB2, and Domino