|
|||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | ||||||||
See:
Description
| Class Summary | |
| RemoteAppParamSet | Provides access to application parameters that reside on a remote system. |
| RemoteFile | Represents a file on a remote system, accessed through the
RemoteLauncher. |
| RemoteLauncher | Provides facilities for performing operations on remote systems,
by communicating with the Server
program. |
| RemoteParamSet | Provides access to parameters that reside on a remote system. |
| RemoteProcess | Represents a process on a remote system, accessed through the
RemoteLauncher. |
| RemoteTestbedParamSet | Provides access to testbed parameters that reside on a remote system. |
| Server | This is a program that provides remote access to various operations
through the RemoteLauncher
class. |
Facilities for launching applications on remote systems.
The Satin test automation system communicates with an application under test (AUT) through an ARO (Awesome Remote Objects) server. Before a Satin test script (Java program) can establish communication with the ARO server in the AUT, the AUT must already be running. If it is not, the script must be able to launch it. If the AUT is to run on the same system as the test script, this presents no special problems. However, if the AUT is to run on a different system, there is no off-the-shelf solution for allowing the script to launch it.
The RemoteLauncher package provides a solution to this problem.
It consists of two main parts: a server program
(Server)
that runs on the system where the AUT is to run, and a client-side class
(RemoteLauncher)
for communicating with the server.
The RemoteLauncher server must be launched independently of the test script. In practice, it should always be running on a testbed system so that the testbed is always ready to be used by a test script.
4/11/01 Ed Stauff - file created.
|
|||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | ||||||||