5250 Connect User’s Guide
72
When you have a need for multiple tiers of pooling based on multiple
security challenges within your system. (For example, users may need one
set of logon credentials to get into the network, another to get into the
mainframe, and another to get into the CICS region.) Serial log-in
requirements may dictate the use of multiple logon components.
When your service needs stateful “session-based” connections.
When you need the performance advantages available through connection
pooling.
If performance under load is not a high-priority issue and your connectivity needs
are relatively uncomplicated, you may not need to use Logon Components at all.
But there is no way to know if performance is adequate merely by testing services
at design time, on a desktop machine.
Components and services built with the 5250 Component Editor may appear to
execute quickly at design time (in Animation Mode, for example). But in real-
world conditions—which is to say under load, with dozens or even hundreds of
requests per second arriving at the server—session overhead can be a significant
factor in overall transaction time. The only way to know whether you need to use
the special performance enhancement features described in this chapter is to do
load testing on a server, under test conditions that mimic real-world “worst case”
conditions.
Connection Pool Architecture
When you install the 5250 Terminal Connect, two types of Connection Resources
are added to the Connection creation wizard: a TN5250 Connection and a 5250
Logon Connection (henceforth a Logon Connection).
The TN5250 connection is a true connection and, when used by a 5250 Terminal
component, can establish a session with a host system.
