5250 Connect User’s Guide
74
A Connection Resource is always required in order to get to the host. (This is true
for any Composer service that uses 5250 components.) For simplicity, this
diagram shows the Connection Resource going directly to the host; in the real
world, there may be intervening security layers.
The Logon Component contains Actions (an action model) designed to find a
particular screen of interest in the host program. This drill-down location is the
effective entry point of the transaction for any upstream process that uses this
Logon Component. You can think of the Logon Component as a go-between
between the physical connection (represented by the Connection Resource) and
the logic layer (represented by the 5250 Component itself.
In order for a 5250 Component (at the top of the diagram) to use a Logon
Component, it needs to enlist the aid of a Logon Connection resource. The Logon
Connection is the bridge between the 5250 Component and the Logon
Component.
The kinds and responsibilities of the various objects discussed above are
summarized in the following table.
Object Role
Connection Resource
(TN5250)
Allows a connection to be established with a
host system.
Logon Component Specialized type of component in which the
action model contains Logon, Keep Alive, and
Logoff action blocks. This component can
maintain a connection at a particular launch
screen in a host program.
Logon Connection Specialized type of Connection Resource that
associates a pool of UserIDs and passwords
with a given Logon Component type. At
runtime, connections are established for client
processes on demand (and reused), with one
Logon Component instance per connection.
Every connection in the pool provides ready
access to a given point (a particular launch
screen) in the host program, thanks to the
associated Logon Component (see above).
5250 Terminal
Component
Contains the action model that comprises the
business logic for a particular 5250 interaction
(or transaction).
