This topic provides details specific to working with a remote Virtualize Server.
For an overview of local vs. remote Virtualize servers, see Dedicated (Remote) Virtualize Servers vs. The Local Virtualize Server.
This functionality assumes that the same version of Parasoft Virtualize is available on the Virtualize desktop and the remote Virtualize Server. Subminor version differences (i.e. these from service packs) do not impact interoperability.
To work with a dedicated Virtualize server, you start Virtualize in server mode from the designated server machine, then you interact with it from the various desktop Virtualize installations that your team uses.
To set up a dedicated Virtualize server:
On that same machine, start Virtualize in Virtualize server mode by using a command such as:
"virtualizecli -startServer -data <workspace_dir> -localsettings
-data: Specifies the Eclipse workspace location. If the -data option is not used, then the default workspace found under [Virtualize_workspace]\parasoft\workspace (where"Virtualize_workspace" could be C:\Users\yourname) will be used.
-prefs "-prefs "workspace.properties" "
ON- all requests are processed asynchronously
DELAY- only response that have a delay are processed asynchronously, default
OFF- no asynchronous processing
When starting Virtualize in this way, the Start deactivated, release automatically when idle option (in Parasoft> Preferences> Parasoft> License) needs to be disabled. Otherwise, you won’t be able to add this server from another Virtualize installation’s UI.
To stop a dedicated Virtualize server:
To configure a desktop Virtualize installation to interact with a remote Virtualize server (e.g., so you can view and add virtual assets):
The server will then be added to the list of servers—allowing you to add virtual assets and configure virtual assets that run on this server.
For instructions on how to deploy virtual assets to a remote Virtualize server, see Local and Remote Deployment Options.
When a virtual asset is deployed to a remote Virtualize server, the .pva file is written to the VirtualAssets project of the workspace being used by the remote Virtualize server.
Each remote server provides a Workspace Files folder designed to allow easy transfer of files between remote Virtualize servers and the local machine. For instance, you can use it to:
Any files that are in your local VirtualAssets project will be synchronized with this folder. In addition, you can:
If your organization wants to monitor asset usage statistics for this server, you can configure the server to collect statistics, then view the collected statistics from either Virtualize or the CTP interface.
Server statistics collection can help you:
To view and modify server statistics collection:
To see a summary of server statistics in Virtualize, open the Virtualize server’s configuration panel, then review the statistics in the Monitoring tab.
"Unrecognized" refers to messages that were received by the Virtualize server, but did not match the listening paths on any virtual asset or HTTP proxy.
"Unmatched" refers to request messages that matched a virtual asset, but failed to match any responder correlations. The unmatched hits are grouped according to the request’s source IP/host and the first virtual asset that attempts to serve this request.
Additional details are available for viewing and export in CTP:
By interacting with the Virtualize API, you can write custom applications that interact with the Virtualize server. For details, see Managing Virtualize Servers Through the Web Service Interface.