Recording from an ad hoc monitor
Create an ad hoc monitor to record events from a transport rather than from an operation.
Before you begin
In the early stages of a project, you might not yet have much of the logical architecture of the system. Use this feature to record messages that you can use to build the architecture, tests, and stubs.
To use this feature, you must have a logical transport with a valid binding to a physical transport in the current working environment.
About this task
In some cases, you can record events directly from a transport. Where this option is not available, or where extra software is needed to record directly from the transport, you can create an ad hoc monitor.
Procedure
- In the Recording Studio perspective, click the Ad Hoc Monitor icon on the Event Monitors toolbar.
- In the Ad Hoc Monitor wizard,
provide the following information:
- Name
- Enter a name to be displayed in the list of Event Monitors.
- Transport
- Click Browse to display a list of available logical transports in the current project.
- Message Type
- The available values depend on the value of the Transport field.
- Header Information
- The available values depend on the value of the Transport field. For more information, see the documentation for the appropriate transport type.
- Display Color
- Choose a unique color to identify the events that are associated with this monitor.
- Click OK.
- In the Event Monitor window, select the new ad hoc monitor.
- In the Events View window, click Start Recording.
What to do next
After recording from this monitor, you can use the messages
in the same way that you use any other recordings, including the following
tasks:
- Create a test, stub, trigger, or requirement. See Creating test resources from recorded or imported events.
- Save messages as a new operation. See Creating an operation from recorded events.