User guide

6: Customizing the System Configuration
DC 900-1333Q 177
configure the server-resident TSI software so it can communicate (using the Freeway
message multiplexor) with the client TSI software. Refer back to Figure 1–1 on page 26
to see how the server TSI software relates to the Freeway message multiplexor.
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”, a s s h o w n i n Figure 6–2). Chang-
ing the
AsyncIO parameter to “no” or omitting it prevents the server TSI software from
operating as designed.
Caution
Before modifying the muxcfg file for the server TSI software, you
should be familiar with the parameter descriptions in the Freeway
Transport Subsystem Interface Reference Guide. Of particular
importance are those parameters that control server resources,
such as the TSI buffer pool size (
MaxBuffers parameter) or message
size (
MaxBufSize parameter). Improper values could adversely affect
server operation.
Keep the following points in mind if you must modify the
muxcfg file:
//
Server2
{
transport = "tcp-socket";
logLev = 0;
traceLev = 3;
timeout = 63999;
MaxInQ = 10;
MaxOutQ = 10;
asyncio = "yes";
wellknownport = 0x'2011'; // protocol specifics
}
Figure 6–2: TSI Configuration File (muxcfg) for Freeway Server (Cont’d)