background image
<< Client/Server Configuration - Configuration tasks | Client/Server Configuration - Enable networking on TCP/IP host >>
Client/Server Configuration - Multiple remote applications
<< Client/Server Configuration - Configuration tasks | Client/Server Configuration - Enable networking on TCP/IP host >>
356
User's Guide
20 C
ONFIGURING
S
ILK
T
EST
FOR
C
LIENT
/S
ERVER
T
ESTING
Configuration tasks
that your scripts will use to direct test operations to the associated
application. Use the following procedure to enable networking and assign the
Agent its network name:
1
Start the Agent software.
2
Left-click the Agent icon to display the icon menu.
3
Select the Network item from that menu.
4
In the dialog that appears, select the network type from the Network
pulldown list.
5
For NetBIOS, enter the Agent name into the Agent name field. For TCP/
IP, the default port number appears in the Port number field. You
normally want to accept the default, but if you have port number
conflicts, read the section "And you have port number conflicts..." on
page 356.
6
Click OK.
You only need to execute this procedure the first time you run that Agent.
Multiple remote
applications
When you enable networking by selecting the networking type in the
Runtime Options dialog on the host, do not set the Agent Name field to an
Agent name if you have multiple remote Agents. This field only accepts a
single Agent name and using it prevents you from handling all your client
machines the same way. If you specify one Agent name from your set of
Agents, then you cannot issue a Connect call to that Agent and thus would
not receive the machine handle that the Connect function returns. Since you
have to issue some Connect calls, be consistent and avoid writing exception
code to handle a machine that is automatically connected.
If you use TCP/IP...
TCP/IP is an intrinsic part of the UNIX operating system and is the only
protocol that SilkTest supports on UNIX-family platforms. Therefore, in a
mixed PC and UNIX network, SilkTest and all the Agents must use TCP/IP.
For Agents running under TCP/IP, the Agent name is the TCP/IP name of the
Agent's machine. You do not have to set the Agent name on the target
machine as you do for NetBIOS.
And you have port
number conflicts...
SilkTest connects to each Agent through a TCP/IP port that has a 4-digit ID.
Normally all the machines in your testing network automatically use the
same default port number. This allows the 4Test Connect function to
automatically specify the port number for all connections. If some other
application on one of your machines has already used the default port