Skip to content
DevTest Solutions - 8.0.1
Documentation powered by DocOps

Path Graph

Last update February 2, 2015

A path graph contains a graphical representation of a path and its frames. The path graph displays in the upper area of the transaction detail dialog.

When you select a root transaction frame in graphical or list view from the Analyze Transactions window, the transaction detail dialog displays with the path graph at the top.

You view the path graph from the Analyze Transactions window by:

  • clicking a path in graphical view.
  • clicking Open transaction details from the Actions column in list view.

The icons indicate the type of frame. Examples of the frames types are EJB, HTTP, JMS, REST, web service, DevTest, and unknown. The DevTest frame type represents a step executing inside a test case or virtual service model.

The text below the icon provides the following information:

  • Frame name
  • Execution time

Use Zoom In and Zoom Out to size the path display.

Frame Name

The format of the frame name depends on the type of frame.

The frame name for HTTP is the path portion of the URL. The name also contains the method. Paths that are created using the VS Traffic to CAI Companion are indicated with the virtualized label in the component name.

An example is POST/itkoExamples/EJB3AccountControlBean(virtualized).

See VS Traffic to CAI Companion for more information about using this companion.

The frame name for JDBC is SQL Activity (N), where N is the number of SQL statements that were used to generate the frame.

The frame name for JMS consists of the following parts:

  • A string that identifies the type of operation. If the operation involves the production of a message, the string is send:. If the operation involves the consumption of a message, the string is recv:.
  • The name of the queue
  • (Optional) The name of the connection factory

An example is recv:queue/ORDERS.REQUEST@ConnectionFactory.

The frame name for JMS can also be DevTest. This name is used when a test case receives a JMS message.

The frame name for RMI is the Java class and method that was executed.

The frame name for webMethods is the flow service name.

The frame name for WebSphere MQ consists of the following parts:

  • The string put or get
  • The WebSphere MQ host name
  • The queue manager name
  • The queue name

An example is put-172.24.255.255-QueueManager-ORDERS.REQUEST.

The frame name for a web service is the path portion of the URL.

Execution Time

In certain scenarios, the execution time below the leftmost component is the time for the entire transaction.

If the execution time is so low that it rounds down to zero, the value 0 ms is displayed.

Incoming and Outgoing Request Information

In the path graph, you can view the incoming and outgoing requests by selecting the line that connects a frame. The Incoming Request tab and Outgoing Request tab displays in the lower area of the transaction detail dialog.

The following graphic displays the incoming and outgoing request information in the path graph:

Screen capture of incoming and outgoing requests in the path graph.

Was this helpful?

Please log in to post comments.