499-01 Sample Questions Answers

Back-end delay

Front-end delay

Network delay

Server delay

AppResponse Xpert

Browser plugin

A load balancer such as Stingray

SysAdmin or webmaster

Proxy server

An end-user page view

The web server tier

The web application

The server node for the transaction

Use Riverbed Steelhead to inject the script at run time from the web server.

Use Riverbed Stingray to inject the script at run time from the web server.

Manually paste the Javascript in any web page you want to monitor with BrowserMetrix.

Edit a master file for the application by adding the Javascript to the header section of the file.

Safari does not support the W3C Navigation Timing specification.

Safari is a more responsive browser.

BrowserMetrix does not process "time to first byte" currently.

This is the user's first visit to the site or the previous page was not one of the instrumented pages.

Ports cannot be changed after the installation.

Change the server.xml HTTP_PORT and HTTPS_PORT specifications in the installation folder.

Changes are need on both server.xml and bindings-jboss-beans.xml.

Log in to the BrowserMetrix default web user interface.

AppInternals Xpert

AppSensor Xpert

AppMapper Xpert

AppResponse Xpert

Search by Object Name

Top N/Bottom N

Standard Components

By IP Address

By having many people log in with the same account

By clicking on the Link tool to create a unique URL for the dashboard

By exporting the dashboard as a report

As long as a user can view the dashboard, they can make their own local edits.

The user has to own the dashboard to be able to do full editing.

The owner can grant specific users full access.

Unlimited except for standard resource considerations

5

100

250

Unlimited, as long as they use the same machine

In the Java console, under Tools > Pages > Information Privacy Manager

In the Java console, under Tools > Pages > User Session Tracking Manager

In the web user interface under System > Pages > Information Privacy Manager

In the web user interface under System > Setup > Information Privacy Manager

Create New Panel icon

Data Sources icon

Link icon

Create New Dashboard icon

AppResponse Xpert

AppInternals Xpert

Cascade Profiler

BrowserMetrix

Passing a metric name will create a dashboard view with a single Area Chart panel of that metric.

One of the parameters to pass allows for permanently saving the dashboard and assigning role-based permission to it.

You can also specify a pre-built dashboard in a parameterized URL.

By default, anyone who can authenticate to the OPNET Authorization Server can create their own dashboard.

Dashboards can be shared so that authentication is not required, and right-click integration is fully functional.

Being able to view a dashboard panel lets you adjust its time range and copy the panel to your own dashboard for further editing.

External content can be inserted into any dashboard by using the Auxiliary Panel content type.

You get of list of next-hop IP addresses or host names to use to create dashboards.

The field automatically populates with the data sources for the IP address or host names from which you can open pre-configured dashboards.

The "Create New Dashboard" panel opens with templates you can use to create a dashboard with the given IP address or host name.

The dashboards already created with the given IP address or host name automatically open in a new tab.

EJBs: classes that implement the javax.ejb.EntityBean or javax.ejb.SessionBean interfaces

JDBC - classes that implement any of several interfaces in the java.sql package

JNDI - classes that implement the javax.naming.Context or javax/naming/directory/DirContext interfaces

Portlets - classes that implement the javax.portlet.Portlet interface

Generic classes

Tiers with identical code are mapped and correlated for each transaction at run time.

Tiers with identical code are deduplicated and correlated for each transaction at run time.

Each trace includes all the tiers necessary to execute the transaction at run time.

Tiers that are identical in the same transaction are excluded at run time.

Install agents on a limited number of machines.

Restart the server.

Agents self tune so there is no need to control the overhead.

Never install more than 5 agents.

Use multiple consoles.

Unplug the server.

Database server name or internet protocol (IP) address

Database type

Port number(s)

Table name

Query type

Changes in jida.config

Enabling monitoring of generic classes with config.package metrics

Changes in the -agentpath parameter

Enabling cross-tier transactions

Response time for SQL statements

Database usage by application and user

It tracks throughput in terms of database calls, transactions, rows, bytes, and active sessions.

A link to "View Database SQL queries" insights

A change in direction in the data exchange

One full TCP data request-response cycle

A TCP connection that finishes with a FIN-ACK connection close

The TCP three-way handshake (SYN, SYN-ACK, ACK)

Data sent between TCP keepalives

End-user experience monitoring

User-defined transaction profiling

Application component deep dive

Network device monitoring

Status polling

TCP window scaling

Maximum transmission unit (MTU)

TCP maximum segment size

Packet size

Automatically discover downloads of web pages and related groups of web pages.

Collect detailed metrics on web page usage, such as download times, overall web-page traffic, total number of page downloads, total number of slow pages, distribution of HTTP response codes; auto-decode and analyze SSL traffic.

Store, and make accessible to end users, decoded SSL-encrypted packets.

Automatically detect users based on login information and identify the web page downloads for each detected user.

Identify the location, platform and browser of users.

Managed nodes use the embedded client and synchronize with a common server.

Managed nodes use the embedded NTP client and synchronize with symmetric multiprocessing (SMP).

Managed nodes use their own NTP client.

No specific NTP configuration is needed, as AppInternal Xpert could handle the correct timing by itself.

Netflow and monitoring port data merged

Netflow and monitoring port data merged, but only if the "merge netflow and monitoring port data" is enabled in the web user interface configuration pages.

Netflow data only

Monitoring port data only

User response time (servers)

User response time (clients)

Payload transfer time (clients)

Server response time (servers)

Turn rate (clients)

Web-based

IP-based

Port-based

Database-based

Server-based

AppInternals Xpert

AppResponse Xpert

AppTransation Xpert

Riverbed Performance Management Dashboards

You can toggle back and forth between the source code and the AppInternals Xpert performance data to examine selected class/method transactions that exceed a particular duration.

You can open the source code directly into Transaction Trace Warehouse.

In Visual Studio or Eclipse source code, you can click on the name of a generic method or click inside the code for the method and link to traces on transactions that the .NET or Java code generated, and display those transactions in Transaction Trace Warehouse.

You can click on the name of a generic method or click inside the code for the method and link to AppInternals Xpert metrics that the method generated, displaying in the desktop console.

You can open the source code directly into Transaction Trace Analysis.

1 minute

5 minutes

1 second

15 minutes

4

3

2

1

IP addresses

Hostnames

IP address range

Subnets

The servers cannot be the problem.

It must be the network.

There is no problem. The user's experience is normal and expected.

No conclusion can be made due to insufficient data.

More monitoring and analysis is required to identify and eradicate monitoring gaps at the end user, network, server, and back-end dependencies.

AppTransaction Xpert

AppResponse Xpert

Riverbed Performance Management Dashboards

AppSensor Xpert

Each web page associated with the application

A back-end data adapter that identifies and tracks all tiers of the application

The front-end web application with JavaScript and the application tiers with agents

The front-end web application with agents and the back-end with specified scripts

BrowserMetrix

AppSensor Xpert

AppInternals Xpert

AppTransaction Xpert

An agent installed on the database

AppResponse Xpert Appliance capturing traffic

Agent installed on application server

Agent installed on web server

Some code compilation or modification is needed.

You can set the IBM_JAVA_OPTIONS environment variable to add the argument into the application startup.

IBM SDK Java is not supported.

Setting the IBM_JAVA_OPTIONS environment variable will add the same argument into every IBM SDK Java application startup.

TCP out-of-sequence

TCP retransmission

TCP frozen window

TCP reset

TCP connection failed

AppSQL Xpert

CX-Tracer

AppDatabase Xpert

AppSensor Xpert

Enable the X-Forwarded-for field.

Route clients around the load balancer.

Create a firewall rule to ensure the client IP addresses are seen.

Specify a route in the router for the client IP addresses.

The Web tier is the bottleneck because it has the most open requests waiting for a response.

The DB tier is the bottleneck because it is the lowest tier that is clearly not handling requests in time.

The App tier is the bottleneck because it is the first tier not handling the same number of requests as the tier above it.

The Web tier is the bottleneck because at an Offered Load of 300, there are still 50 requests waiting from the Web tier, and it never recovers. The lower tiers do not get the requests passed to them because the Web tier is not processing fast enough.

The App tier is the bottleneck because the DB tier is handling everything the App tier sends it.

From AppTransaction Xpert, use the AppTransaction Xpert capture manager

From AppSensor Xpert, when defining synthetic tests

From AppResponse Xpert, use the packet download manager

Using the distributed agent controller

From the packet trace warehouse