User guide

6: Customizing the System Configuration
DC 900-1333Q 175
TSI connections are defined in a server TSI configuration file (such as
muxcfg). Two
types of configuration sections are included in the TSI configuration file. The first sec-
tion (called “main”) specifies the TSI configuration for non-connection-specific opera-
tions. Subsequent sections define the operational environment for one or more specific
connections.
Note
If you define multiple TSI connections, each should have a unique
connection name; otherwise the parameters associated with the
first occurrence are used for all sessions with the same name.
All sections of the TSI configuration file have the following format:
connection-name
{
parameter-name = parameter-value; // comments...
.
.
.
}
6.4.2 Default Server TSI Configuration File (muxcfg)
When you followed the software installation procedures described in Chapter 3, the
default server TSI configuration file named
muxcfg (Figure 6–2) was installed in the free-
way/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 5.1 on page 141), Freeway uses the infor-
mation in the boot configuration file (Figure 6–1 on page 168) to configure physical or
virtual devices, services, and corresponding databases prior to downloading software to
the ICPs. One of the parameters in the boot configuration file is the server TSI configu-
ration file name (
tsi_config_file = muxcfg). Freeway downloads the muxcfg file and uses it to
Techpubs: If
you change
this section,
also change
the equivalent
section in
chapter 3 of
the Freeway
TSI Reference
Guide.