FTAM/9000 Programmer's Guide

36 Chapter 1
HP FTAM/9000 Overview
Overview of FTAM Concepts
Initiators and Responders
As noted earlier, you write a program (user program) to access the FTAM
interface using a library of functions. FTAM uses the initiator to make
requests and the responder to service them. (Refer to Figure 1-3.)
• The executable name for an HP-UX initiator is ftam_init (located in
/opt/ftam/lbin). To use an FTAM function, you must link your
application with the libmapftam.a library. The ftam_init process is
also known as the initiator server provider process (SPP). Refer to the
“Using FTAM” chapter for information on linking FTAM libraries.
• The ftam_init is invoked when you call ft_aeactivation(), and serves
also as a responder for local FTAM requests. For information on
ft_aeactivation(), refer to the “Managing FTAM Connections” chapter.
• The ftam_init is invoked when you call a high level function with the
default ae_label (i.e., pointer to a NULL location). For information on
high level functions, refer to the “Using FTAM” chapter.
• The executable name for an HP-UX responder is ftam_resp (located
in /opt/ftam/lbin). The ftam_resp is a daemon process that provides
the interface for the HP-UX file system (real filestore) to the FTAM
VFS. Note that the ftam_resp is also known as the responder SPP.
• One ftam_resp process exists for each active, remote FTAM
connection. Connections to a local responder do not require an
invocation of ftam_resp.
• An ftam_resp daemon process must be active to receive remote
connection requests. After receiving a request, ftam_resp forks the
process to create another ftam_resp process, which then processes all
requests associated with that connection.
Initiator The initiator submits requests on behalf of you. When you
submit a request (i.e., call a function), the initiator sends
your request to a responder.
Responder The responder receives and services an initiator's
request. If applicable, it returns a response.