...

1. Start Virtualize Server in GUI mode.
2. In that GUI, open the configuration panel for the server you want visibility into (by double-click clicking its Virtualize Server view node).
3. In the Server Configuration tab, review and modify the available options:
   • Enable the event monitoring service: Enables/disables event monitoring for this server. Event monitoring is enabled by default.
      
   • Event Monitoring Provider: Specifies the provider that the event monitoring service uses. By default, a built-in provider based on ActiveMQ is used. To use another provider, select it from the list of available options, then complete the applicable fields.
   • Port: The default service port number 9617, but a different port number will automatically be assigned based on availability if that port is in use. You can also configure the port manually by setting the following property in your JVM arguments on startup: 

     parasoft.event.monitoring.broker.port=<port>

...

To indicate that you want Virtualize to start reporting the events related to a virtual asset or message proxy, do one of the following:

• Right-click the asset or proxy in the Virtualize Server view , then and choose Start Monitoring.
  
• In the proxy’s/asset’s configuration panel, click Start Monitoring.
  

Note that the related icon will cфсhange сhange to indicate that it is now being monitored.

...

To indicate that you want Virtualize to stop reporting the events related to a virtual asset or message proxy, do one of the following:

• Right-click the asset or proxy in the Virtualize Server view , then and choose Stop Monitoring.
• In the proxy’s/asset’s configuration panel, click Start Stop Monitoring.
  
  
  

...

You can open this perspective in any of the following ways:

• Click the Parasoft Event Details button in the shortcut bar (on the top right of the workbench).
• Click the Open Perspective button in  in the shortcut bar, choose Other, then choose Parasoft Event Details in the Select Perspective dialog that opens.
• Choose Window> Window > Open Perspective> Perspective > Other, then choose Parasoft Event Details in the Select Perspective dialog that opens.

...

• Request messages received
• Response messages sent
• Data source usage (e.g.for example, which data source row was used in a response message)
• Error events (a request did not correlate to a message, invalid messages were sent, etc.and so on)
• Provisioning action suite execution events (see Defining Provisioning Actions for for details about action suites
  

...

Anchor
Reviewing Message Proxy Events Reviewing Message Proxy Events

Reviewing Message Proxy Events

Viewing the events generated when  when messages flow through a deployed message proxy helps you understand what traffic the application under test is sending through the message proxy. Generally, every request/response message pair that travels through a message proxy will generate the following events:

• Request received: Indicates a message received by a message proxy. Provides details on the  the HTTP path or queue name where the message was received, the Virtualize server host name, and the message.
• Proxy request sent: Indicates that the proxy has forwarded the message to its intended target service destination. Details include the destination and the message contents.
• Proxy response received: Indicates that the proxy has received a response from the target service.
• Response sent: Indicates that the proxy has forwarded the response received from the service to the original caller (the AUT).
  

Note that if the proxy is configured to forward messages to virtual asset endpoints, then the same events will be generated and message destination details will include the URL or destination details to indicate that.   However, if the virtual asset which receives that proxy message is also being monitored, it will generate its own events (typically 2 two for successful transactions: a Request received and Response sent event).

...

...

• An incoming message "Request received" event with the message content (labeled as "Unrecognized message").
• An Error "Error returned" event with details.

Reporting Custom Events

The  The Extension Tool (described in Extension Tool for Custom Scripting) can be used to report custom events to the Event Log by calling the report(IEvent) method of the given com.parasoft.api.ScriptingContext object.

Here is a Jython example:

from com.parasoft.api 
import Event def test(input, context):
    context.report(Event("Here I am!"))

See com.parasoft.api.ScriptingContext and com.parasoft.api.IEvent in the Extensibility API Javadocs for more information. The Javadocs can be accessed by choosing Parasoft> Help> going to Parasoft > Help > Extensibility API.

Integrating a Third-Party Monitoring System with Virtualize Event Monitoring

...

JNDI Connection URL: tcp://VirtualizeHostName:9617
JNDI Initial Context class: org.apache.activemq.jndi.ActiveMQInitialContextFactory 
JMS Connection Factory: ConnectionFactory
Destination Name: PARASOFT_SERVER_EVENTS
Destination type: Topic

Note that the Virtualize Host port is assigned dynamically at server startup based on availability. To check the actual port number, open the server’s configuration page (from the Virtualize Server view) or open the Server preferences page (choose Parasoft> go to Parasoft > Preferences, then select  Parasoft> click Server).

The JMS messages that are published by the Virtualize Server event monitoring service are in XML format. If you are interested in only certain event types, you can use a JMS selector expression to receive only events that meet your criteria:

...

This area displays virtualization-related events such as messages sent, messages received, and errors. Selecting an item here displays more information in the Details view. The 5 five most recent logs are saved and available.

...