<< Configuring SilkTest for Client/Server Testing | Client/Server Configuration - The configuration process >>
Client/Server Configuration - Networking protocols used by SilkTest
<< Configuring SilkTest for Client/Server Testing | Client/Server Configuration - The configuration process >>
number of Agents can run on remote machines. This manual refers to the
systems that run remote Agents as target machines.
subnet as the host machine. (If the third octet of the IP address
doesn't match any two machines, then they are on different
subnets and cannot be tested with distributed testing.)
application by means of an Agent process running on each application's
machine. The application then drives the server. Alternatively, SilkTest is
capable of driving the GUI for a server (if it has one) or of driving a
server database directly by running scripts that submit SQL statements to
the database. See "QA DBTester features" on page 346 for more
information on this capability.
protocols are used. This means that a SilkTest script on one platform can
drive the Agent on a target platform, as long as both the host and Agent
platforms are running an appropriate protocol for the platform and both are
running the same protocol (regardless of the protocols used by the
applications under test). The table on page 353 lists the protocols available
for each platform.
testing an application that requires TCP/IP communications in order to
communicate with a server on a Sun Sparc station. SilkTest's Windows
machine can run NetBIOS for the host and the application's Windows
machine must then run NetBIOS for the Agent as well as TCP/IP for the
application under test. Running NetBIOS will have no impact on your TCP/
IP connections but will allow SilkTest to communicate with the Agent.
choose to use TCP/IP for SilkTest and its Agents as well.
and Motif platforms, SilkTest's machine and all the Agent machines will run
TCP/IP because that is the only protocol that SilkTest supports for Motif-
based platforms.