Message Parasoft Virtualize message proxies simplify the process of recording live system behavior and routing traffic to the desired endpoints (real or virtual).
A message proxy is deployed to a local or remote SOAtest or Virtualize Server so that it can receive messages to be processed by a virtual asset or passed to a live system (or to an internal endpoint, for advanced scenarios). The proxy can record traffic to emulate the captured behavior—enabling you to cut the dependencies on system components that are difficult to access.
...
- Configurations are saved and managed like virtual assets, enabling you to reuse settings.
- Virtualize Server can host (deploy) multiple proxies on various connections and configurations.
- Each proxy can be enabled/disabled individually, which allows JMS and MQ connections to be disconnected so that messages are not consumed by the proxy (similar to Virtual Assets).
- Proxy settings can be managed on a both the local Virtualize Server or a remote SOAtest or Virtualize Server via the desktopVirtualize Desktop. They can also be managed with CTP.
- Once you point the application under test to the proxy endpoint(s), you can start/stop recording on demand and modify the target service endpoint where the messages are being forwarded at any time without any impact on the AUT. For example, without touching the AUT, you can redirect messages from an actual service to a virtual asset (and that virtual asset can be hosted on the localhost server or a remote server).
- Multiple proxies can be configured on a single server (similar to Virtual Assets).
...