This topic explains how to configure monitoring for events that occur on Parasoft Virtualize Servers.

Sections include:

Why Monitor Server Events?

Visibility into what messages are sent to and from Parasoft Virtualize Servers—and what validations and errors occur at the virtual asset level—enables you to:

For example, in a common test situation, SOAtest will send a message to a system, such as an available service or a web browser, which will then send a message to a virtual asset deployed on a Parasoft Virtualize server (e.g., because the actual resources is not yet available or is not accessible for testing). 

By adding an Event Monitor tool to the test suite, you gain insight into messages 2 and 3 and well as messages 1 and 4. You also see the result of any validation tools you may have attached to the virtual asset  (for instance, XML Assertor tools) and receive details on any errors that may have occurred (for instance,  because the virtual asset was not properly configured to process valid messages, or because invalid messages were sent).

By default, the Virtualize event monitoring service uses a built-in provider based on ActiveMQ. For details on how to use another provider, see Using an Alternative JMS System for Virtualize Server Event Monitoring.


  1. Add an Event Monitor tool to the test suite that drives the interaction with the Virtualize Server you want to monitor.
  2. In the Event Source tab of the Event Monitor tool’s configuration panel, select Virtualize Server as the platform.
  3. (If you are connecting to a Virtualize Server that is version 9.6 or newer AND requires user authentication) In the Event Monitor tool configuration panel, complete the User and Password fields to the right of the Automatic option. Also, adjust settings for SSL, Host, and Port if needed.

  4. (If you are connecting to a Virtualize Server that is version 9.3 or older AND uses a port other than 1080) In the Event Monitor tool configuration panel:
    1. Set connection to Manual
    2. Click View Settings.

    3. Provide OpenJMS connection settings as follows:
      • URL:rmi://hostname:portnumber/
      • Initial Context: org.exolab.jms.jndi.InitialContextFactory
      • Connection Factory: ConnectionFactory
      • Destination Name: SOATESTSERVER_STUB_EVENTS
      • Destination Type: Topic
  5. Under Event Subscriptions, specify what type of events you want to monitor. Available options are:
  6. Under Test Failure Criteria, specify the test failure criteria. Note that if a validation tool is chained to the current Event Monitor tool, the outcome of that validation will determine this test’s success or failure—and the following settings not applicable. Available options include:
  7. In the Options tab, modify settings as needed.
  8. The Event Viewer tab will display details about the events received. It indicates the virtual asset name, the name of responder that processed that message, the response message, results of validation tools (if available), and errors that occurred. Double-clicking  an item opens a dialog with additional details.

Troubleshooting: No Events or Specific Error Messages are Reported

If you no events or specific error messages are reported by Event Monitor, then disable your firewall. Firewalls running where SOAtest is running can sometimes block communication between the Event Monitor and a remote Virtualize Server. If you are using the Windows firewall, it needs to be disabled prior to using Event Monitor with a remote Virtualize Server. Other firewalls may also need to be disabled. 

Using an Alternative JMS System for Virtualize Server Event Monitoring

By default, Virtualize Server events are monitored using the built-in ActiveMQ-based provider. Alternatively, you can  use another JMS system that you have. To configure this:

  1. Open the view for the Parasoft Server you want to monitor (e.g. for a  Parasoft Virtualize server, go to Parasoft Virtualize, and choose Window> Show View> Virtualize Server).
  2. Double-click the node for the machine (local or remote) you want to configure to use the event monitoring provider.
  3. In the Event Monitoring Provider field, select your preferred server. If you want to use a JMS server that is not specifically listed, choose Other JMS  Provider.
  4. Specify the connection settings.

    Note that a default event monitoring destination and type are specified in the available controls.

    You need to either:

    - Configure your JMS system to use this default destination, or

    - Change the Parasoft settings to another destination that is available on your system.

  5. In the Event Monitor tool configuration panel:
    1. Open the Event Source tab.
    2. Set connection to Manual
    3. Click View Settings.

    4. Select the appropriate Event Monitoring Provider.
    5. Specify the settings required to connect to your JMS.

For details on the connection settings, see