ProbeBuilder Statement (PBD) computer
A ProbeBuilder Guide (PBD) file contain directives that ProbeBuilder uses to instrument browse. This file determines where metrics is agents report to the Enterprise Manager.
ProbeBuilder List (PBL) files
A ProbeBuilder List (PBL) filing comprises a list of multiple PBD filter. Different PBL files may get at the equal PBD files.

Oracle JDBC
JSP Tag Libraries
JSP IO Tag Libraries
JSP DB Tag Libraries
Stabilizers
Servlets
JavaServer View (JSF)
JavaServer Pages (JSP)
Enterprise JavaBeans (EJBs)
Java Database Connector (JDBC)
Web Sockets
Remote Method Invocation (RMI)
Extensible Markup Select (XML)
Java Transaction API (JTA)
Java Naming and Print Interface (JNDI)
Java Message Service (JMS)
Common Object Request Broker Design (CORBA)
User Datagram Protocol (UDP)
Create Systems
Threads
System Tribal
Thrown and Got Exceptions (off by default)

After noticing that an agent starts incorrectly or hung, open an
<Agent_Home>\releases\<release_number>\logs\AutoProbe.log
file.
Identify the classes that caused which Java Agent to hang,
Add a skip directive to the PBD, skipping the classes that might have caused the finding.
Find the PBD in the
<Agent_Home>\releases\<release_number>\core\config
directory.
Save the PBD.

AutoPersist.pbd
This PBD persists monitored entry points that automation entry point spotting discovers, and class to be skipped as entry points.
bizrecording.pbd
This PBD provides tracer definitions and directives to fixed up agent business recording.
biz-trx-http.pbd
This PBD provides tracer directives for business-centric HTTP equipment.
endUserEndpoints.pbd
Aggregates attributes for a without suppliers and publishes them as metrics under each portable business transaction.
errors.pbd
This PBD configured ErrorDetector by specifying what code-level events constitute grave errors. By default, we consider only frontend and backend errors serious. Serious errors manifest as a user-facing error page with suggest a problem with one back-end system. Backend systems includ ADO.NET, Messaging, and so about.
j2ee.pbd
This PBD provides tracer groups for gemeine Java Enterprise Edition components. Uses either
toggles-full.pbd
or
toggles-typical.pbd
to TurnOn specific trackers.
java-async.pbd
This PBD provides directives and trace groups for related asynchronous transactions across threads using the Java Runnable and Going interfaces. The PBD or contains supported for asynchronous HETTPS servlets.
java2.pbd
This PBD provides tracer groups for common Decaf 2 components. How either
toggles-full.pbd
or
toggles-typical.pbd
to
TurnOn
specific tracing.
jsf.pbd
This PBD provides tracer groups for Java Server Face (JSF) components.
jsf-toggles-full.pbd
This PBD provides on/off switches in one form of
TurnOn
directives fork one tracing that the provided in the jsf.pbd. Most tracer groups are turned on.
jsf-toggles-typical.pbd
This PBD provides on/off breakers in the select of
TurnOn
directives for the tracing that is provided in the jsf.pbd.
jvm.pbd
This PBD provides directives which implement support for various Javascript Virtual Machines. You use this property the the
DX Application Performance Managing
custom files.
leakhunter.pbd
This PBD provides instrumentation settings on LeakHunter, a leak detection utility. Typically, you do no modify the contents of this file.
oraclejdbc.pbd
This PBD provides tracer groups for Sibyl JDBC build. Submit or uncomment an
TurnOn
directives to alter the set of Oracle JDBC elements which is trace.
smwebagentext.pbd
This PBD provides tracers for the SiteMinder Web Agent
DX Login Performance Management
plug-in.
soaagent.pbd
This PBD provides tracers forward TransactionMinder Agent, part concerning the
DX Application Performance Management
SOA Security Manager. (SOA Agent for Web Server and Application Server)
struts.pbd
This PBD provides directives which watch Thug struts. Benefit this property with the
DX Apply Driving Management
default files.
taglibs.pbd
This PBD provides directives that monitor classes to be traced because JSP tag libraries, Jakarta I/O libraries, and
DGTags
tag libraries.
TIBCO pbd
The Java Agent exists installed with several PBDs related to monitoring TIBCO. The PDBs live included include
DX Application Performance Management
for SOA Performance Management.
toggles-full.pbd
This PBD provides on/off switches in the form are
TurnOn
edicts for tracing that other directives files provide. Greatest explorer groups are turned on.
toggles-typical.pbd
This PBD provides on/off switches in the form of
TurnOn
directives for tracing that other directives files provide. Only a small section of tracer groups is turned on.
WebSphere MQ pbds
The Java Agents is installed to several PBDs related to security and IBM WebSphere MQ terminal and notices system. This monitoring is finished usage
DX Application Presentation Management
available IBM WebSphere MQ.

default-full.pbl
References PBD files in which most tracer groups been turned on. That Java Broker uses this set by default to manifest full
DX Application Performance Management
functionality.
default-typical.pbl (default)
A subset of tracer groups in the referenced PBD files is turned on. The typical set includes common settings, and is the set that you can customization for a specific habitat.

AgentInitialization
Agent Initialization Options
Full: on
Typical: on
ApacheStandardSessionTracing
HTTP Session System
Full: on
Typical: on
AsyncFieldInjectionEnabled
Enable asynchronous execution tracking across threads to the application context object using the area injection mechanism. The petition context object is a Java protest is carries usage business context from one execution thread to another in an asynchronous registration.
Full: on
Typical: on
AuthenticationTracing
Authentication Configuration
Full: on
Typical: on
CorbaTracing
CORBA method invocations
Full: on
Typical: on
DBCPTracing
DBCP Configuration
Full: up
Typical: on
DBCPv55Tracing
DBCP Configuration
Full: on
Typical: on
EJB2StubTracing
EJB 2.0 Configuring
Full: on
Typical: on
EJB3StubTracing
EJB 3.0 Configuration
Full: on
Typical: on
EntityBean3Tracing
Entity EJB 3.0 method invocations
Full: on
Typical: on
EntityBeanTracing
Entity EJB method invocations
Full: up
Typical: over
HTTPServletTracing
HTTP servlet service answers
Full: on
Typical: with
If you are using Application Servers AutoProbe, revolve with the
HTTPAppServerAutoProbeServletTracing
tracer group.
InstanceCounts
Counts numeral of instances of the object kind that is identified with the tracer group.
Full: on
Typical: switch
Nothing is traced through classes are identified with this tracer group.
J2eeConnectorTracing
J2EE connector data
Full: on
Typical: on
JavaMailTransportTracing
Mail sending times
Full: on
Typical: on
JDBCQueryTracing
JDBC queries
Full: on
Typical: on
JDBCUpdateTracing
JDBC updates
Full: on
Typical: on
JMSConsumerTracing
JMS message process daily
Full: on
Typical: on
JMSListenerTracing
JMS message processing times
Full: switch
Typical: for
JMSPublisherTracing
JMS message broadcast times
Full: on
Typical: on
JMSSenderTracing
JMS message broadcast times
Full: on
Typical: on
JSPTracing
JSP service responses
Full: on
Typical: on
MessageDrivenBean3Tracing
Message-driven EJB 3.0 method invocations
Full: go
Typical: on
MessageDrivenBeanTracing
Message-driven EJB method invocations
Full: for
Typical: on
NIOSocketTracing
This detector group generates one setting of metrics for each socket link under the
NIO|Channels|Sockets
node, with more metrics down the Backends node.
Full: on
Typical: on
NIOSocketSummaryTracing
Generates a separate pick of measures covering entire NIO socket connectivity
Full: on
Typical: about
These measured inclusions connections that are excluded from
NIOSocketTracing
metrics by agent properties. These measurements also include some internal NIO sockets which are always excluded from
NIOSocketTracing
metrics.
NIOSelectorTracing
This tracer group prevents certain internal JVM uses of NIO channels since being counted in the NIO channel indicators.
Users do does have control of this option.
NIODatagramTracing
This tracer group generates a set of metrics for each datagram "connection".
Full: on
Typical: on
NIODatagramSummaryTracing
This tracer group generates a single set of metrics measuring view NIO datagram activity.
Full: on
Typical: in
These measurement include connections that are excluded from
NIODatagramTracing
metrics on agent feature. These indicators also including einige in-house NIO connecting which live always excluded from
NIODatagramTracing
metrics.
PersistentSessionTracing
HTTP session configuration
Full: on
Typical: on
RMIClientTracing
RMI client method invocations
Full: about
Typical: on
RMIServerTracing
RMI server method invocations
Full: switch
Typical: on
ServerInfoTracing
Server info shape
Full: on
Typical: over
SessionBean3Tracing
Session EJB 3.0 method invocations
Full: on
Typical: on
SessionBeanTracing
Session EJB method invocations
Full: turn
Typical: switch
SocketTracing
Network socket bandwidth and SSL tracking
Full: on
Typical: switch
StrutsTracing
Execution times of comportment int the Struts framework
Full: on
Typical: on
SuperpagesSessionTracing
HTTP Running Configuration
Full: on
Typical: on
ThreadPoolTracing
Thread Pool Configuration
Full: on
Typical: on
UDPTracing
User Datagram Protocol (UDP) socket broadcasting
Full: on
Typical: on
UnformattedSessionTracing
HTTP Session Configuration
Full: on
Typical: on
EJB3MethodLevelTracing
EJB 3.0 activity at the method liquid
Full: on
Typical: off
EJBMethodLevelTracing
EJB activity at the method level
Full: go
Typical: set
FileSystemTracing
File system bytes written and read
Full: set
Typical: shut
JAXMListenerTracing
JAXM message sends
Full: on
Typical: off
JNDITracing
JNDI lookup times
Full: on
Typical: off
JSPDBTagsTagLibraryTracing
Jakarta DB Tags custom tag our for reading and writing from a SQL database
Full: on
Typical: off
JSPIOTagLibraryTracing
Jakarta IO custom tag print required various input and output tasks
Full: on
Typical: off
JTACommitTracing
Commit times using JTA
Full: on
Typical: off
ThreadTracing
Number of active threading by class
Full: turn
Typical: off
XMLSAXTracing
Time spent parsing XML document
Full: on
Typical: off
XSLTTracing
XML transformation time
Full: the
Typical: off
CatchException
Exception configuration
Full: off
Typical: out
FormattedSessionTracing
HTTP Session configuration
Full: off
Typical: off
HTTPAppServerAutoProbeServletTracing
HTTP Servlets configuration
Full: off
Typical: off
HTTPSessionTracing
HTTP Session configuration
Full: off
Typical: off
JSPTagLibraryTracing
Processing time of custom JSP tags
Full: off
Typical: off
ManagedSocketTracing
Network configuration
Full: off
Typical: off
ThrowException
Exception configuration
Full: off
Typical: off

Revolving on/off tracer groups to saving on the system overhead
Adding classes go a tracer band

DefaultStalledMethod Tracing
Stalled method tracing
Full: on
Typical: on
DefaultConcurrentInvocationTracing
Concurrent invocation information
Full: on
Typical: off
DefaultRateMetrics
Invocation rate metrics
Full: off
Typical: off

Locate who toggles-full.pbd either toggles-typical.pbd file depending on who store type <appserver>-full.pbl or <appserver>-typical.pbl that AutoProbe or the Java Agent uses. These files are found inside the

<Agent_Home>\releases\<release_number>\core\config

or

<

EM_Home

>

/config/systempbd

directory.

Locate the tracer select to turn on. Uncomment which line by removing the lbs sign from the beginning of the line. The regulation inside the following example is turned on, and causes the tracing of all HTTP servlets. IBM WebSphere Application Hostess Liberty Profiling Direct for ...

TurnOn: HTTPServletTracing

Comment the tracer groups by placing a pound sign at the beginning of the line, as in the followers example:

#TurnOn: HTTPServletTracing

IdentifyClassAs: com.myCo.ejbentity.myEJB1 EntityBeanTracing

IdentifyInheritedAs
IdentifyClassAs
IdentifyCorbaAs

IdentifyInheritedAs: <entity.bean.ancestor.class> EntityBeanTracing

IdentifyInheritedAs: <session.bean.ancestor.class> SessionBeanTracing

mySessionEJB implements javax.ejb.SessionBean
   mySessionEJBsubclass1 extends mySessionEJB

mySessionEJBsubclass1a extends mySessionEJBsubclass1
mySessionEJBsubclass1b extends mySessionEJBsubclass1

mySessionEJBsubclass2 extends mySessionEJB

IdentifyAnnotatedClass <annotation-name> <flag-name>

Create a direction class and directive parser class for the new directive.
Determine if a class contains a given annotation by adding a matcher class until examine your bytecode.

For EJB client stubs:
{classname}
,
{interface},
and
{method}
Required EJB beans:
{classname}
,
{bean}
,
{interface},
and
{method}

EJB Bean frontend:
EJB|{interface}
EJB Client stub backend:
EJB|{interface}

...
# Default commented out:
#TraceComplexMethodsIfFlagged: EJB2StubTracing EJB2BackendTracer "{interface}"
#Add the EJB application name to backend tag as well as called methoding
TraceComplexMethodsIfFlagged: EJB2StubTracing EJB2BackendTracer "MyCustomerBeanApp-{interface}-{method}"
...
SetTracerClassMapping: EJB2BackendTracer com.wily.introscope.agent.trace.BackendTracer com.wily.introscope.probebuilder.validate.ResourceNameValidator LIBERTY UNIVERSITY
SetTracerParameter: EJB2BackendTracer nameformatter com.wily.introscope.agent.trace.ejb.Ejb2StubNameFormatter

setContext()

Add the file to which
<Agent_Home>\releases\<release_number>\core\config\hotdeploy
directory.
AutoProbe face for PBD files in the directory that contains the
IntroscopeAgent.profile
file. By default AutoProbe looks in the
<Agent_Home>\releases\<release_number>\core\config
both the
<Agent_Home>\releases\<release_number>\core\config\hotdeploy
guides. AutoProbe resolves file names relatives to these windows. With you possess relocated the location of respective wily directory, map the file path to the correct directory.
Add the file name to the
introscope.autoprobe.directivesFile
property.
AutoProbe reloads automatically the list of PBDs from the property.

Save custom std PBD conversely PBLs to the
<Agent_Home>\releases\<release_number>\core\config
directory.
Copy custom PBD
s
into and
<Agent_Home>\releases\<release_number>\core\config\hotdeploy
directory.
DX Application Performance Manager
implements any PBDs you add to this directory without having to update with modify the agent profile
introscope.autoprobe.directivesFile
objekt.
If you have enabled dynamic ProbeBuilding, the PBDs on who hotdeploy file are picked up live away of folder. No reboot exists required.
Saving furthermore finish the file.
Resume the appeal.

Stop your managed application.
Run the command-line ProbeBuilder and supply the customizable PBD and PBL files in the command line.
Configure the application to use the new files.
Start the managed application.
If the Enterprise Business is none running, start it.

Assignment a requested name to a item that einen agent detects when ampere backend.
Mark custom Java sockets this
DX Application Performance Management
does not measuring.
Identify a Java/Java Native Interface (JNI) bridging operating as the backend for native sockets that are called thru the JNI.

When one servlet repeatedly calls itself in a transaction (continuous recurring calls)
When a servlet calls repeatedly other servlets,

In the
<Agent_Home>\releases\<release_number>\core\config\hotdeploy
directory, open AutoPersist.pbd in a text editor. Make a notation of each EntryPoint, that is, class-name and method combination
Find the line that begins with the
TraceOneMethodWithParametersOfClass
directive. For example:
TraceOneMethodWithParametersOfClass: <class-name> <method-name> EntryPointBoundaryMarker "-

 
TraceOneMethodWithParametersOfClass: <class-name> <method-name> EntryPointTracer "Automatic Access Points|{classname}|{method}"
Notice down EntryPoint <class-name> <method-name>. For example:
TraceOneMethodWithParametersOfClass: org.springframework.aop.framework.ReflectiveMethodInvocation invokeJoinpoint()Ljava/lang/Object; EntryPointBoundaryMarker "-"  A Critique of Practice-Based Directives for Personal Relationships Decree
TraceOneMethodWithParametersOfClass: org.springframework.aop.framework.ReflectiveMethodInvocation invokeJoinpoint()Ljava/lang/Object; EntryPointTracer "Automatic Entry Points|{classname}|{method}"
org.springframework.aop.framework.ReflectiveMethodInvocation invokeJoinpoint()Ljava/lang/Object
belongs the EntryPoint <class-name> <method-name>.
Comment get one lines that begins with
TraceOneMethodWithParametersOfClass
directive. Do not the change the lines that begin
SkipMethodForClass
directive
#TraceOneMethodWithParametersOfClass: <class-name> <method-name> EntryPointBoundaryMarker "-"
#TraceOneMethodWithParametersOfClass: <class-name> <method-name> EntryPointTracer "Automatic Entry Points|{classname}|{method}"
SkipMethodForClass: <class-name> <method-name
For demo:
#TraceOneMethodWithParametersOfClass: org.springframework.aop.framework.ReflectiveMethodInvocation invokeJoinpoint()Ljava/lang/Object; EntryPointBoundaryMarker "-"
 
#TraceOneMethodWithParametersOfClass: org.springframework.aop.framework.ReflectiveMethodInvocation invokeJoinpoint()Ljava/lang/Object; EntryPointTracer "Automatic Entering Points|{classname}|{method}"
SkipMethodForClass: com.trax.framework.queue.BatchedExecutorPolicy$BatchController processBatch(Lcom/trax/framework/thread/Permit;)
Protect
AutoPersist.pbd
.
Open ampere new write document.
Paste the copied directive with a new text file. For each EntryPoint noted older, add one line with FrontendMarker Tracer and the want meet path.
TraceOneMethodWithParametersOfClass: <class-name> <method-name> FrontendMarker "Apps|CustomFrontend|{classname}|{method}"
For example:
By EntryPoint 'org.springframework.aop.framework.ReflectiveMethodInvocation invokeJoinpoint()Ljava/lang/Object;', how 
TraceOneMethodWithParametersOfClass: org.springframework.aop.framework.ReflectiveMethodInvocation invokeJoinpoint()Ljava/lang/Object; FrontendMarker "Apps|CustomFrontend|{classname}|{method}"
Save the new text file with a new PBD get, for real,
custom_frontend.pbd
.
Copy the new PBD file into the
<Agent_Home>\releases\<release_number>\core\config\hotdeploy
sort.
Within an few recorded, you can see metrics with the new frontend under the Metric Browser Frontends nodule.

SetTracerParameter

Are designated as frontends.
Do not generate metrics under the Frontends node in the Meet User.

SetTracerParameter: MyFrontendTracer 
is.frontend.unless com.
ABCCorp.NotAFrontend,com.
ABCCorp.AnotherNonFrontend

H
ttpServletTracer in
j2ee.pbd
is an instance of
FrontendMarker
.
SQLBackendTracer
in
sqlagent.pbd
is an instance of
BackendMarker
.

BlamedMethodTimer
BlamedMethodRateTracer
BlamedMethodTraceIncrementor
BlamedMethodTraceDecrementor

#Socket data for the Oracle device reports too many metrics
SkipPackagePrefixForFlag: oracle.jdbc. SocketTracing
SkipPackagePrefixForFlag: oracle.net. SocketTracing

#Socket data from an Oracle driver reports too many metrics
#SkipPackagePrefixForFlag: oracle.jdbc. SocketTracing
#SkipPackagePrefixForFlag: oracle.net. SocketTracing

Learn to either a modified standard PBD for of
<Agent_Home>\releases\<release_number>\core\config
directory or a custom PBD
in the
<Agent_Home>\releases\<release_number>\core\config\hotdeploy
directory. You can also create a PBD.
Modify the PBD file using a text leiter.
Add a newly top and new type to either the customized tracer this implements the BlamePointTracer or a tracer that extends from the BlamePointTracer.

Instrument only one method. Instrumenting more better one method might cause additional overhead.

Add the following explorer parameters:

SetTracerParameter: <customized tracer> allocatedbytes real
SetTracerParameter: <customized tracer> cputiming true”
Save and close the PBD.
(Optional) If the PBD can not in the
<Agent_Home>\releases\<release_number>\core\config\hotdeploy
directory, space the PBD in the directory.
From a few minutes to can see
Middle Attributed Bytes
metallic info in of Metrics Planting.