...
Also note that icons and labels are used to indicate server access and licenses. If your team is using user access control, Virtualize Server view labels indicate your access level to each server. For details on what operations are allowed for each access level, see Understanding Role-Based Permissions.If you have a developer sandbox license (designed for modelling and testing virtual assets), a special icon will be used to mark that server.
...
- From the Server node:
- 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.
- From the Local machine node:
- Open: Opens a panel that allows you to configure advanced settings for the local Virtualize server. See Configuring Server and Deployment Settings Virtualize for details.
- Refresh: Refreshes the local Virtualize server.
- Add Virtual Asset: Allows you to add a virtual asset to the local Virtualize server.
- Re-deploy All Virtual Assets: Re-deploys virtual assets so that modifications are "live."
- From a remote server node:
- Open: Opens a panel that allows you to configure advanced settings for the given Virtualize server. See Configuring Server and Deployment Settings Virtualize for details.
- Refresh: Refreshes the given server (e.g., to keep it in sync with virtual assets added or removed by other team members).
- Add Virtual Asset: Allows you to add a virtual asset to the given server.
- Re-deploy All Virtual Assets: Re-deploys virtual assets so that modifications are "live."
- Remove Server: Removes a remote server from the Virtualize Server view.
- From a specific virtual asset node (local machine or remote server):
- Open: Opens a panel that allows you to configure advanced deployment settings for the given virtual asset. See Configuring Server and Deployment Settings Virtualize for details.
- Copy: Allows you to copy a virtual asset so you can paste it from one server to another.
- Paste: Allows you to paste a copied virtual asset from one server to another.
- Disable: Disables the virtual asset (so it is still present, but cannot be accessed).
- Delete: Deletes the virtual asset from the given server.
- Start monitoring/stop monitoring: Tells Virtualize to start/stop reporting the events related to a virtual asset. See Gaining Visibility into Server Events for details.
- Re-deploy Virtual Asset: Re-deploys this virtual asset so that modifications are "live."
- Lock/Unlock: Adds or removes locks that prevent other users from modifying or deleting an artifact you’re working on. See Locking and Unlocking Virtualize Server Artifacts for details.
- Copy to workspace: Copies this virtual asset to your workspace so you modify it.
- Unprocessed Messages: Shows details on messages that were sent, but not processed.
...
Virtualize lets you lock artifacts that you're working on to ensure that they are not modified or removed by other users. This functionality is available only if the remote Virtualize Server hosting those artifacts authenticates with Parasoft CTP using a valid username and password. It is supported only when a) the connection to CTP is successful, and b) CTP does not allow anonymous access.
Locking/unlocking functionality is available for artifacts on remote Virtualize Servers (not those on the local machine). Locking/unlocking functionality applies to virtual assets, message proxies, JDBC controllers, and files. Locking/unlocking functionality is also available for Data Repositories; see Locking and Unlocking Repositories in CTP for details.
Any authenticated user can lock a currently-unlocked artifact, modify an artifact that he or she locked, and unlock an artifact that he or she locked.
Admin-level users can also unlock any artifact (no matter which user applied the lock). However, they cannot modify artifacts that other users locked. If they wanted to modify a locked artifact, they would need to unlock it first, then modify it.
Authenticating with CTP
The Virtualize server authenticates with CTP using the credentials specified in that server’s Preferences> Parasoft> CTP. You do not need to enter any CTP credentials from your desktop installation. Just be sure that you specified a valid username and password for connecting to that remote Virtualize server.
Locking and Unlocking Artifacts
To lock an artifact:
- Right-click that artifact in the Virtualize Server view, then choose Lock.
A lock image will be added to the associated artifact icon, and the label will indicate that this artifact is now locked by you. At this point, you are the only one who can modify or delete this artifact.
To unlock an artifact:
- Right-click that artifact in the Virtualize Server view, then choose Unlock. Remember that unless you are an Admin-level user, you can unlock only the artifacts that you previously locked.
Migrating Workspaces from 9.9.3 or Earlier
...