...
The recommended workflow is to first deploy a newly - created virtual asset to a "staging" remote server in order to validate that it works as expected and to fine-tune its behavior. Then, once the virtual asset is operating properly, you can move it to a "production" Virtualize server for centralized, team-wide access.
Note that Virtualize Server requires a server license.
For details, see Deploying Virtual Assets Virtualize.
Continuous Testing Platform
...
Allows you to connect to a JMS broker to retrieve the list of queues provided by that broker and see the messages currently sitting on each queue. The Queue Browser also lets you delete messages off the queues.
For details, see see Browsing Queues_virt.
Change Advisor
To keep pace with rapidly - evolving services and environment conditions, it’s important to have a fast, easy, and accurate way to update virtual assets. Change Advisor enables you to assess the impact of changes to existing virtual assets and then quickly update existing assets (or create new ones) in response to the identified change impacts. This vastly reduces the amount of time required to modify assets as services and environment conditions change.
For details, see Change Management Virtualize.
Recording Proxies (not be confused with message proxies)
...
An environment is a collection of variables that can be referenced in your Virtualize Responder suite. Using environments, you can define variables for endpoints, connection properties such as usernames and passwords, database table names, etc... then indicate which variable values should be applied in a given environment. By using environment variables instead of specifying" hard-coded" values in your responders and associated tools, you can instantly "flip a switch" and reconfigure them for use in a different environment (e.g., development, testing, UAT, pre-production, etc.).
For details, see see Configuring Virtualize Environments.
...