User`s guide

26 DC 900-1317J
ADCCP NRM Programmer’s Guide
1.2.1 Establishing Freeway Server Internet Addresses
The Freeway server must be addressable in order for a client application to communi-
cate with it. In the Figure 1–3 example, the TCP/IP Freeway server name is
freeway2,
and its unique Internet address is 192.52.107.100. The client machine where the client
application resides is
client1, and its unique Internet address is 192.52.107.99. Refer to
the Freeway User’s Guide to initially set up your Freeway and download the operating
system, server, and protocol software to Freeway.
1.3 Embedded ICP Environment
Refer to the user’s guide for your embedded ICP and operating system (for example, the
Freeway Embedded ICP2432 User’s Guide for Windows NT) for software installation and
setup instructions. The user’s guide also gives additional information regarding the data
link interface (DLI) and embedded programming interface descriptions for your spe-
cific embedded environment. Refer back to Figure 1–2 on page 23 for a diagram of the
embedded ICP environment. Running a client application in the embedded ICP envi-
ronment requires the basic steps described in Section 1.4
1.4 Client Operations
Client application communication with the Freeway takes place over the Data Link
Interface (DLI) sessions and their underlying Transport Subsystem Interface (TSI) con-
nections. Communication with the embedded ICP uses the DLI but not the TSI.
1.4.1 Defining the DLI and TSI Configuration
You must define the DLI sessions and TSI connections between your client application
and Freeway (only the DLI sessions for an embedded ICP). To accomplish this, you first
define the configuration parameters in DLI and TSI ASCII configuration files; then you
run two preprocessor programs,
dlicfg and tsicfg, to create binary configuration files
(see Chapter 5). The
dlInit function uses the binary configuration files to initialize the
DLI environment. (The
dlTerm function terminates the DLI environment.)