|Strategi Connections Defined|
The purpose of this bulletin is to explain the different Strategi connection types.
Basic Connection Type
This may be defined as a simple TCP/IP or other communications link between two entities. In this case we say that a browser connects to the HTTP server, or a DHSM server connects to a DHSM agent. This type of connection is limited only by the number of threads available to process them. Currently these threads are implemented via OS processes (iSeries jobs), but in future they may well be implemented in a single process using OS threads. The number of threads is limited by both configuration and by the size of the Strategi system purchased. This limit on threads applies to all services that run threads (currently DHSM and HTTP).
note: Pocket Strategi is not limited by threads because it is a user-oriented service, which uses user licenses.
Login Connection Type
The second type of connection is a logical session establishment, such that an entity is considered to be online. The session may or may not correspond to a continual communications connection. This type of connection we tend to also (and more correctly) refer to as a login.
A "login" connection is controlled via user licensing. When a user makes a connection to Strategi that involves identifying themselves, we create a session for them, consider them logged in, write a "connection" record and use a license. How that connection is ended depends on the medium used to connect. With HTTP authentication, it is ended by either timeout, or by a resource request that includes the directive "*SESSION=LOGOUT".
For example, a hyperlink in a page may look like the following:
Such a link will access the current directory, log the user out and redirect immediately to the homepage. In contrast, if the session is established by the emulation applet, it is ended when the TCP/IP link is ended (unless tunneling is used, in which case a short timeout applies between "http requests" to allow the client to re-establish it's connection to the emulation server, via the HTTP server, before the session is considered to be ended).
Therefore at present, a connection by an authenticated user directly uses a license, and is recorded in the Strategi connections file, visible via WRKSGICNN. Note that in future we may also record other connections here, such as those received for DHSM, for information purposes, but these will not use user licenses.
Strategi System Capacities
For reference purposes, the following table illustrates the different capacities of each Strategi model.
** End of Technical Support Bulletin **