This topic provides details specific to working with a remote Virtualize Server.

Sections include:

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.

Starting and Stopping the Server

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.

Starting the Server

To set up a dedicated Virtualize server:

  1. Install Virtualize Server on the machine that you want to act as a dedicated Virtualize server.
  2. On that same machine, start Virtualize in Virtualize server mode by using a command such as: 

    "virtualizecli -startServer -data <workspace_dir> -localsettings
    <localsettings_file>" file

You can use the following command line options with virtualizecli:

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.

The Virtualize server is controlled by a web service with the URL http://localhost:9080/axis2/services/StubService?wsdl. For details about this web service’s operations, see Managing Virtualize Servers Through the Web Service Interface.

Stopping the Server

To  stop a dedicated Virtualize server:

Interacting with a Remote Virtualize Server from the Parasoft Virtualize Desktop

To configure a desktop Virtualize installation to interact with a remote Virtualize server (e.g., so you can view and add virtual assets): 

  1. Open the desktop Virtualize installation’s Virtualize Server view (Choose Window> Show View> Virtualize Server).
  2. Do one of the following:
    • Right-click the Server node, then choose  Add Server.

    • Select the Server node, then click Add Server.

  3. In the wizard that opens, specify the server’s host name, display name (shown in the Virtualize server tree), protocol, and port.

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.

Deploying Virtual Assets

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.

Transferring Files Between the Remote Server and the Local Machine

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:

Collecting Server Statistics

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:

Enabling Statistics Collection

To view and modify server statistics collection:

  1. Start Virtualize Server in GUI mode.
  2. In that GUI, open the configuration panel for the server you want visibility into (double-click its Virtualize Server view node).
  3. In the Server Configuration tab, review and modify the available options:
    • Enable the statistics collection service: Enables/disables statistics collection for this server. Collection is enabled by default.
    • Statistics provider: Specifies the provider that the statistics service uses. By default, a built-in provider based on ActiveMQ is used. To use another provider, select it from the list of available options, then complete the applicable fields.
    • Port: The default service port number 9618. If that port is in use, a different port number will automatically be assigned based on availability. You can also configure the port by setting the following property in your JVM arguments on startup:<port>

    • Collection period: Determines the frequency (in seconds) at which statistical usage messages are aggregated and reported.

Reviewing Server Statistics

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:

Accessing a Virtualize Server through its API

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.