Client/Server Configuration - Configuration tasks
If this is the protocol you normally use and you will not be including any
Motif-based workstations in your testing configuration, you can use
This section presents some configuration requirements that must be met to
use SilkTest to test applications over a network. In general you should set up
your Agents and make all adjustments to the partner.ini file or environment
variables before enabling networking on the host machine.
As you look through the rest of this chapter, please be sure to read all sections
that apply to your configuration. You can ignore topics that do not apply to
If you use any PC-class platforms...
You have to explicitly assign a unique network name to remote Agents so that
SilkTest can identify the Agent when your testcase connects to that machine.
This step is not necessary for Motif-based Agents because SilkTest
automatically uses the workstation's TCP/IP name.
In a single-application test environment, if the application is local, you do not
have to determine an Agent name or issue a connection command because if
you start an Agent on the local machine, SilkTest automatically connects to it
and directs all Agent commands to it.
In a single-application test environment, if the application is remote, specify
the Agent name in the Runtime Options dialog (select the Runtime choice
from SilkTest's Options menu). This causes SilkTest to automatically connect
to that machine and to direct all Agent commands to that machine. This
contrasts with the multi-application case, in which you explicitly connect to
the target machines and explicitly specify which machines are to receive
which sections of code.
One or more remote
When you have one or more remote PC-based Agents in your testing
network, you have to enable networking by specifying the network type. If
you are not using TCP/IP, you have to assign to each Agent the unique name