Viewing the application flow of the exit and entry points for an instance


Viewing the application flow of a transaction instance enables you to see details for each component of the flow. As shown in the following example, each component is displayed as a node in the application tree. Click a node to see the details pane for that specific node. The arrows between nodes show the transaction flow. The technology used in the specific flow between nodes is displayed on the arrow.

Above each node is displayed the accumulated time, in milliseconds, spent on the node, as well as the percentage of time spent on the node out of the total time spent on the entire Transaction Instance.

biz_trans_details_appflow.png

To view application flow details

  1. On the Business Transaction Details window, click the Application Flow tab.
  2. Click a node.
     Node details are displayed in the pane to the right of the flow tree.

The following table describes each node.

Node

Description

ico_client.png Client

The Client is the entry-point node furthest to the left.

The following information is extracted from the HTTP request and displayed:

  • Browser type
  • User: Remote request user, if known. If unknown, "Client" is displayed
  • IP remote address
  • Details:
    • IPv6 IP of client, if relevant.
    • HTTP header information: All HTTP headers from the request, including the HTTP response content type, customer custom header, and the size of the HTTP request and HTTP response
    • Request parameters: All request parameters from both the body of the request and URL, including user name and number of lines to display

ico_appserver.png Application server

The application server node displays the following information:

  • Application server type and its version
  • Name defined for the installed BMC Application Diagnostics Agent
  • The platform and version the application server is deployed on, such as Java Sun 1.5, Oracle 1.5
  • The operating system and version, such as Windows XP SP12, Linux 1.0
  • A list of metrics recorded with the instance, such as the amount of CPU and memory used, and number of threads

ico_db.png Database

Each database node represents a database instance.

The following Database instance details are displayed in the pane to the right of the application flow tree:

  • Instance name, if available. If not available, the database address is displayed
  • Database type, if available (such as Oracle, SQL or Sybase)
  • Title of the nodes
  • URL connection, if available
  • Formatted SQL statements
  • Prepared statements
  • Stored procedure name

ico_jms.png Java Messaging Service (JMS)

The JMS node indicates the collected JMS exit points and the following JMS-specific data:

  • Host port
  • Node title
  • Number of invocations
  • Message details

ico_ejb.png Enterprise JavaBeans (EJB)

The EJB node displays the server name, the port, and the time spent on the invocation.

The following detailed EJB node information is displayed in the pane to the right of the application flow tree:

  • Server name
  • Port
  • Server vendor
  • IP address
  • Number of invocations
  • Total time spent on the invocation

ico_ws.png Web Server

The Web Server node displays the server name and the time spent on the invocation.

The following detailed Web Server node information is displayed in the pane to the right of the application flow tree:

  • Server
  • Server vendor
  • IP address
  • Number of invocations
  • Total time spent on the invocation
Warning

Note

Depending on the transaction type and tier technologies used, there may be any number of application servers, database nodes, JMS, EJBs and Web Servers displayed.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Application Diagnostics 1.2