Pass the Riverbed RCSP-APM 499-01 Questions and answers with CertsForce

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

By default, the DSA attempts to keep 1-second data for 2 hours. The length of this time period is specified by the RawDataPersistDuration attribute in the dsa.xml file.

The DSA deletes the oldest 1-second data from the database If there is less than 10 percent of free disk space (the default for the RawDataPersistFreeSpaceTargetPercent attribute)

The DSA deletes the oldest 1-second data from the database if the database file is larger than specified in the RawDataPersistMaxDiskTarget attribute (unlimited as default).

If both the RawDataPersistFreeSpaceTargetPercent and RawDataPersistMaxDiskTarget attributes are satisfied, the DSA deletes data, if necessary, to retain only as much data as specified by RawDataPersistDuration.

At startup, and every 2 hours thereafter (or the frequency specified by RawDataPersistPurgeInterval), the DSA deletes the oldest 1-second data from the database.

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.

An agent installed on the database

AppResponse Xpert Appliance capturing traffic

Agent installed on application server

Agent installed on web server

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.

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.

MovingWindowPercentile

MovingWindowSigma

HourlyLimits

HistoricalBaseline

HardLimits

Percent of free heap

Percent of time garbage collecting

Percent of usage

Average number of live objects

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