Analyzer User Manual
Capturing Traffic | Page 89 of 264
3. Click on OK.
If a recording is initiated without having first selected an analyzer, the
analyzers
dialog will pop up to request the user to select an analyzer. Selecting
the Use this analyzer by default checkbox in this dialog will conveniently
force the automatic selection of the specified analyzer on each new recording.
7.7 Ellisys Injection API
The analyzer application supports an Injection API, selectable in the
Available Analyzers
dialog, located in the
Record menu (once it is enabled in the Tools menu – see below).
There are two services provided:
Injected User Log Service - displayed in the
Message Log Overview
.
HCI Injection Service - displayed in the
HCI Overview (Injection)
once the Ellisys Injection API
recording is initiated.
The Ellisys Injection API is designed to transport client messages to the analyzer application, and events and
message handling status back to clients.
Messages are packet-oriented and use TCP or UDP as the transport layer. Each message packet links several
possible information objects into one message. The possible objects are defined by the different log services,
while reusing standard object types as much as possible. All messages are addressed to specific log services
that define the required / allowed objects in the messages and might be stateful or stateless
In addition, injection of the user’s log messages is supported. This feature allows for the user’s “
printf
” debug
messages to be displayed in the
Message Log Overview
(View | Overviews), concurrent with any HCI traffic
being captured by the analyzer’s hardware. The analyzer hardware is not required to capture injection sources.
Injection API Download
Use the link below to download helpful documents on the Injection API, including samples and instructions.
http://www.ellisys.com/better_analysis/bex400a_injection_api.zip
To Next Page
Loading...
Need help?
General
