background image
<< Client/Server Configuration - The configuration process | Client/Server Configuration - Configuration tasks >>
Client/Server Configuration - Selecting the SilkTest protocol
<< Client/Server Configuration - The configuration process | Client/Server Configuration - Configuration tasks >>
User's Guide
20 C
Selecting the SilkTest protocol
Gather the information that your test scripts will need when making
explicit connections. For example, you can edit the Agent names into a
list definition and have your testplan pass the list variable name as an
argument for testcases controlled by that plan. The testcases then pass
each Agent name to a Connect or SetUpMachine function and that
function makes the explicit host-to-Agent connection.
The rest of this chapter provides configuration details specific to the different
protocols and operating systems you might be using. This detailed
information makes it possible for you to implement the configuration process
outlined above. Look for headings that mention topics applicable to your
Selecting the SilkTest protocol
On a PC-Class platform, SilkTest and its Agents can use one of three possible
protocols, depending on circumstances. On a Motif-based platforms, TCP/IP
is the only available protocol.
Use TCP/IP...
If the host or any Agent is Motif-based, you must use TCP/IP.
Or you can use TCP/IP just because you prefer to.
Use IPX/SPX...
If SilkTest and all its Agents are running MS Windows 3.11 on 16-bit PCs in
a Novell network, you can save the overhead of NetBIOS by using Novell's
IPX/SPX protocol. The PCs must all be running some kind of Novell network
software, such as Netware or Personal Netware, that can use IPX/SPX as the
communications protocol. If you are running under 32-bit Windows or
running Agents under OS/2, NetBIOS does not present an overhead problem
because it is included in these systems.
Note Since all Agents must use the same protocol, if you want to
drive Agents on both 16-bit and 32-bit PCs you must use NetBIOS
or TCP/IP.