This topic explains how to configure monitoring for events that are transmitted through Software AG webMethods Broker. This monitoring requires admin client group privileges.
Sections include:

Adding Required Jar Files to the SOAtest Classpath

The following jar files need to be added to the SOAtest classpath:

The jar files can be found under [webmethods install dir]/Broker/lib/. For more details, please refer to webMethods Broker Client Java API Programmer's Guide> Getting Started> Using the webMethods Broker Java API.

To add these jar files to SOAtest’s classpath, complete the following:

  1. Choose Parasoft> Preferences.
  2. Open the Parasoft> System Properties page.
  3. Click the Add JARS button and choose and select the necessary JAR files to be added.

Configuring Event Monitor

To configure the Event Monitor tool to monitor webMethods Broker:

  1. Double-click the Event Monitor tool to open up the tool configuration panel.
  2. In the Event Source tab, select Software AG webMethods Broker as the platform. The configuration fields will be populated with default values.
  3. Adjust the configuration field values as needed. The fields are the same as those used in the webMethods tool, and are described in webMethods.

    The Event Monitor uses BrokerAdminClient to monitor events. By default, it subscribes to the "admin" client group. Thus, if you wish to filter events based on their content, you should change the client group value to one that allows for subscription to regular event types (instead of Trace). Why? Because when using Broker::Trace::* events, the filter string will be applied to the fields in the trace BrokerEvents—not the original events that they represent.

    When completing the Event Type field, remember that wildcards are not allowed for Broker::Trace or Broker::Activity event types according to WebMethods Broker Client Java API Programmer's Guide. If you wish to monitor a set of event types, specify a client group name that allows subscription access to the desired event types (possibly other than the default "admin" client group setting), then provide event types with wildcards. For example, you can use Sample::*

    You may also use ${data bank column name} variables in your string. SOAtest will replace that with the data bank value so filter strings can have dynamic values based on the output of other tests.

    For more details on filters and using wildcards in event type names, please refer to the WebMethods Broker Client Java API Programmer's Guide.

  4. In the Options tab, modify settings as needed.


With admin client group privileges, the Event Monitor tool can subscribe to the following event types:

Note that you can also configure the webMethods tool (described in webMethods) to subscribe to the desired event type—the only difference is that with the webMethods tool you need to provide the specific event type name.