User guide

112 DC 900-1333P
Freeway User Guide
All sections of the TSI configuration file have the following format:
connection-name
{
parameter-name = parameter-value; // comments...
.
.
.
}
3.3.2 Default Server TSI Configuration File (muxcfg)
When you followed the software installation procedures described in Chapter 2, the
default server TSI configuration file named
muxcfg
1
(Figure 3–2) was installed in the
freeway/boot directory on the boot server. Freeway uses the information in the muxcfg
file to set up the server-resident TSI software to listen for incoming client connections
on the default well-known port. For most sites,
muxcfg can be used “as is.”
During the boot process (described in Section 4.3.1 on page 122), Freeway uses the
information in the boot configuration file (Figure 3–1 on page 101) to configure phys-
ical or virtual devices, services, and corresponding databases prior to downloading soft-
ware to the ICPs. One of the parameters in the boot configuration file is the server TSI
configuration file name (
tsi_config_file = muxcfg). Freeway downloads the muxcfg file
and uses it to configure the server-resident TSI software so it can communicate (using
the Freeway message multiplexor) with the client TSI software. Refer back to Figure1–1
on page 24 to see how the server TSI software relates to the Freeway message multi-
plexor.
There is one critical difference between the server TSI software and the client TSI software,
namely that the server TSI software must use TSI non-blocking I/O support (that is, the
AsyncIO parameter in the muxcfg file must be set to “yes”, as shown in Figure 3–2).
1. The example server-resident application uses muxcfg.sra. The Military/Government protocol uses
milmuxcfg.
Techpubs: If
you change
this section,
also change
the equivalent
section in
chapter 3 of
the Freeway
TSI Reference
Guide.