This topic introduces the Virtualize Server view, which is where you manage and interact with local or remote Virtualize servers, as well as the virtual assets and proxies that are deployed on them. Topics include:
The Virtualize Server view is where you manage and interact with local or remote Virtualize server, as well as the virtual assets and proxies that are deployed on them. From here, you can start/stop servers, start/stop event monitoring, and create/modify/interact with message proxies (for example, to start or stop recording) as well as Parasoft JDBC Drivers (for example, to switch between passthrough, record, virtualize, and hybrid modes). For remote servers, it also provides a Files folder designed to allow easy transfer of files between remote Virtualize servers and the local machine.
To open the Virtualize Server view, go to Window > Show View > Virtualize Server. For an overview of the available buttons and commands, see Virtualize Server View - GUI Reference.
The Virtual Assets node in this view is always synchronized with the VirtualAssets project. If the VirtualAssets project includes any .pva files, the corresponding virtual assets will be automatically added to this view’s Virtual Assets node. If virtual assets are organized into a hierarchical structure via the controls in the Virtualize Server view (as described in Organizing Deployed Virtual Assets), those same structural changes will be automatically applied to the VirtualAssets project.
Also note that icons and labels are used to indicate server access and licenses. If you have a developer sandbox license (designed for modelling and testing virtual assets), a special icon will be used to mark that server.
Icons also alert you if an artifact is locked and, if so, by which user and at what access level. Note: Locking and unlocking artifacts requires CTP.
Configuration details for each virtual asset, message proxy, and JDBC controller deployment on the local Virtualize server are saved within a separate XML file within your workspace directory. These files are automatically named based on the deployment name and use the following extensions: .pvadd (virtual assets), .pmpdd (message proxies), or .pjcdd for (JDBC controllers).
For details on the operations that can be performed from the Virtualize Server view, see the folowing related topics:
Refreshing virtual assets ensures that the Virtualize Server view’s tree is in sync with the deployed virtual assets and any changes to the VirtualAssets project.
To refresh the entire Virtualize Server view, do one of the following:
To refresh a particular Virtualize server (for example, to display virtual assets recently added by a team member):
The Virtualize Server view’s tool bar provides the following buttons:
| Icon | Name | Description |
|---|---|---|
| Start Server | Starts the local server. |
| Stop Server | Stops the local server. |
| Refresh | Refreshes all servers in the tree. |
| Add Server | Allows you to add a remote server to the Virtualize Server view. |
The following shortcut (right-click) commands are available within the Virtualize Server view:
Lock/Unlock: Adds or removes locks that prevent other users from modifying or deleting an artifact you’re working on. Requires CTP.
Virtualize 9.9.3 and earlier saved configuration details for all of the local Virtualize server’s virtual assets, message proxies, and JDBC controllers in single XML file (VirtualAssets.xml) within your workspace directory.
Virtualize 9.9.4 and higher saves configuration details for each virtual asset, message proxy, and JDBC controller deployment on the local Virtualize server within a separate XML "deployment descriptor" file within your workspace directory. This change relieves you from having to use globally unique names and makes it easier to:
If you open a workspace from Virtualize 9.9.3 or earlier in Virtualize 9.9.4 or higher, this migration from a single VirtualAssets.xml files to multiple deployment descriptor files will occur automatically. The deployment descriptor files are automatically named based on the deployment name and use the following extensions: .pvadd (virtual assets), .pmpdd (message proxies), or .pjcdd (JDBC controllers). If the original virtual asset, message proxy, and JDBC controller name contains characters that are not valid for the new format, the name will be automatically adjusted; for example, asset#3 would be renamed to asset_3.
Migration tips:
