FEPI resources
There are four types of FEPI resource: pool, property set, target, and node. This topic describes the relationships between them.
- Pool
- A collection of nodes and targets
- Property set
- Defines the characteristics of a pool
- CICS1, CICS2, IMS1, IMS 2...
- Back-end systems
- Node 1, Node 2, Node 3...
- Simulated terminals
A FEPI pool can have one or more nodes and one or more targets. The same nodes and targets can be in any number of pools, except that the same node-target pair (a connection) cannot occur in more than one pool.
A CICS FEPI application can reach a target only by specifying a pool, which defines the set of nodes that can be used to make the connection, and the characteristics of the communication.
A target and an open node in the same pool are ‘connected’; when bound, they are ‘in session’. To bind means to establish a session on a connection, to make it ready to allow communication.
The process of communicating with a back-end system is called a conversation; it is the fundamental entity that a FEPI application deals with. Only one conversation can use a connection at one time, although any number can do so consecutively. For efficiency, the session on the connection is kept bound between conversations, unless you choose otherwise. Furthermore, a conversation is owned by the task that establishes it; no other task can use it.
The resources are further explained in Configuring FEPI and the more complex relationships possible between them are illustrated in An example FEPI configuration.