Overview

Dynatrace AppMon fully integrates with Micro Focus SilkPerformer (formerly: Borland SilkPerformer).
It extends SilkPerformer's capabilities by pinpointing the root cause of performance, stability, and scalability problems in application code.

See the Dynatrace blog for a hands-on introduction incl. a step-by-step guide and screenshots.

SilkPerformer Plugin 3.2.1 and later

Name

SilkPerformer Plugin 3.2.1+

Description

This is the SilkPerformer Plugin for dynaTrace 3.2.1+

Compatible with

dynaTrace 3.2.1 and later

Tested with

SilkPerformer 2007, 2008, 2008 R2, 2010, 2010 SP1, 2010 R2, 2011, 18.0

Author

Dynatrace Software

License

dynaTrace Experimental Software License

Support

Community Supported

Download

SilkPerformer Plugin for dynaTrace 6.5+
SilkPerformer Plugin for dynaTrace 6.3
SilkPerformer Plugin for dynaTrace 5.6
SilkPerformer Plugin for dynaTrace 5.5
SilkPerformer Plugin for dynaTrace 5
SilkPerformer Plugin for dynaTrace 4.2
SilkPerformer Plugin for dynaTrace 4.1
SilkPerformer Plugin for dynaTrace 4
SilkPerformer Plugin for dynaTrace 3.5
SilkPerformer Diagnostics Plugin v3.2.1

Installation

SilkPerformer 2010 SP1 ships with SilkPerformer Diagnostics Plugin v3.2.1 embedded.

Copy the plugin to the <SilkPerformer_home>\Working\Plugins directory and extract it. Start SilkPerformer, choose "Settings" -> "System" and scroll down in the left side bar until the plugin is visible.

Figure: SilkPerformer Plugin installed in SilkPerfomer

Some SilkPerformer versions come with a dynaTrace Diagnostics Plugin installed. Please deactivate this plugin to use the SilkPerformer Plugin .

How to use the SilkPerformer Plugin

The SilkPerformer Plugin offers the ability to record a session when a load test (even a try script) is started. This can be done by setting the option "Automatic Session Recording" in the Plugins "Attributes" tab to true.

The "Wait Timeout" Attribute determines the time the SilkPerformer is waiting for the dynaTrace Client to be started. If the dynaTrace Client cannot be reached within this interval the load test will start without dynaTrace session recording.

The "System Profile" Attribute determines the dynaTrace System Profile on which session recording should be started. If omitted, session recording will be started on the first System Profile on the dynaTrace Server with an Agent connected.

The "SilkPerformer Diagnostics Client Port" Attribute determines the dynaTrace client REST interface port.

If the dynaTrace Client is connected to multiple dynaTrace servers the first connected server will be used.

If you change the configured server in dynaTrace Client SilkPerformer has to be restarted.

SilkPerformer Plugin 3.2 and earlier

Name

SilkPerformer Plugin 3.2.0 and earlier

Description

This is the SilkPerformer Plugin for dynaTrace 3.2 and earlier.

Prerequisite

SilkPerformer 7.2, 7.3, 2006, 2006 R2, 2007, 2008, 2008 R2

Compatible with

dynaTrace 3.0 - 3.2

Tested with

SilkPerformer 2007, 2008, 2008 R2, 2010, 2010 SP1

Author

dynaTrace software

License

dynaTrace Experimental Software License

Support

Supported

Download

SilkPerformer Plugin v3.2
SilkPerformer Plugin v3.1
SilkPerformer Plugin v3.0.1

Installation

Copy the Plugin to the <SilkPerformer_home>\Working\Plugins directory and extract it. Start SilkPerformer, choose "Settings" -> "System" and scroll down in the left side bar until the dynaTrace Plugin is visible.

Figure: dynaTrace Plugin installed in SilkPerfomer

Most SilkPerformer versions come with a dynaTrace Diagnostics Plugin installed. Please deactivate this Plugin to use the dynaTrace Plugin with dynaTrace 3.0 / 3.1.

How to use the SilkPerformer Plugin

The dynaTrace Plugin offers the ability to record a session when a load test (even a try script) is started. This can be done by setting the option "Automatic Session Recording" in the Plugins "Attribute" tab to true.

The "Wait Timeout" Attribute determines the time the SilkPerformer is waiting for the dynaTrace Client to be started. If the dynaTrace Client cannot be reached within this interval the load test will start without dynaTrace session recording.

The "Application Session" Attribute determines the dynaTrace System Profile on which session recording should be started. If omitted, session recording will be started on the first System Profile on the dynaTrace Server with an Agent connected.

If the dynaTrace Client is connected to multiple dynaTrace Servers there may be problems with matching the correct System Profile. If the System Profile is available on multiple dynaTrace Servers, it is possible that session recording is started on the wrong Server. If the "profile name" attribute is omitted, session recording may be started on any of the connected dynaTrace Server on the first System Profile with an Agent connected.

Patch for SilkPerformer JMX Integration

Name

SilkPerformer JMX Browser Patch

Description

This is the SilkPerformer JMX Browser Patch for dynaTrace 3.0.x and 3.1.

Prerequisite

SilkPerformer 2006, 2006 R2, 2007, 2008, 2008 R2, 2009

Version

3.0.1

Compatible with

dynaTrace 3.1
dynaTrace 3.0.x

Tested with

SilkPerformer 2007, 2008, 2008 R2, 2009

Author

dynaTrace software

License

dynaTrace Experimental Software License

Support

Supported

Download

SilkPerformer Patch

All currently available SilkPerformer versions are missing the JMX integration data for dynaTrace 3.0. To be able to use dynaTrace 3.0 JMX data please follow the steps below.

Installation

Copy the zip file to <SilkPerformer_home>\Working and extract it. A dynaTrace 3.0.xml will be extracted to <SilkPerformer_home>\Working\Include\jmx-config.
Open the realtime.ini located in <SilkPerformer_home>\Working\Include. Adapt the file as indicated by the excerpt below.

Add the following line to "Application In-Depth":
C= JMX:dynaTrace 3.0, Application In-Depth\dynaTrace\dynaTrace 3.0 (JMX MBeanServer),dynaTrace 3.0 (JMX MBeanServer)

V= 1.2

S= Application In-Depth\Borland OptimizeIt ServerTrace 3.0\SNMP, SNMP,
 M= SNMP:1.3.6.1.4.1.1648.500.5.4.0,         OptimizeIt ServerTrace 3.0\JVM Heap Size Total,   	eAvgOnlyCounter,  0,  bytes,   	0,  1, 2, 3, 4, 5,
 M= SNMP:1.3.6.1.4.1.1648.500.5.5.0,         OptimizeIt ServerTrace 3.0\JVM Heap Size Used,    	eAvgOnlyCounter,  0,  bytes,   	0,  1, 2, 3, 4, 5,
 M= SNMP:1.3.6.1.4.1.1648.500.8.4.0,         OptimizeIt ServerTrace 3.0\Virtual Memory Total,   eAvgOnlyCounter,  0,  kbytes,   0,  1, 2, 3, 4, 5,
 M= SNMP:1.3.6.1.4.1.1648.500.8.5.0,         OptimizeIt ServerTrace 3.0\Virtual Memory Used,    eAvgOnlyCounter,  0,  kbytes,   0,  1, 2, 3, 4, 5,
 M= SNMP:1.3.6.1.4.1.1648.500.7.4.0,         OptimizeIt ServerTrace 3.0\Physical Memory Total,  eAvgOnlyCounter,  0,  kbytes,   0,  1, 2, 3, 4, 5,
 M= SNMP:1.3.6.1.4.1.1648.500.7.5.0,         OptimizeIt ServerTrace 3.0\Physical Memory Used,   eAvgOnlyCounter,  0,  kbytes,   0,  1, 2, 3, 4, 5,
 M= SNMP:1.3.6.1.4.1.1648.500.6.4.0,         OptimizeIt ServerTrace 3.0\Paging File Total,     	eAvgOnlyCounter,  0,  mbytes,   0,  1, 2, 3, 4, 5,
 M= SNMP:1.3.6.1.4.1.1648.500.6.5.0,         OptimizeIt ServerTrace 3.0\Paging File Used,     	eAvgOnlyCounter,  0,  mbytes,   0,  1, 2, 3, 4, 5,
 C= JMX:dynaTrace Diagnostics 1.6, Application In-Depth\dynaTrace Diagnostics\dynaTrace Diagnostics 1.6 (JMX MBeanServer),dynaTrace Diagnostics 1.6 (JMX MBeanServer)
 C= JMX:dynaTrace Diagnostics 2.0, Application In-Depth\dynaTrace Diagnostics\dynaTrace Diagnostics 2.0 (JMX MBeanServer),dynaTrace Diagnostics 2.0 (JMX MBeanServer)
 C= JMX:dynaTrace 3.0, Application In-Depth\dynaTrace\dynaTrace 3.0 (JMX MBeanServer),dynaTrace 3.0 (JMX MBeanServer)

S= Application Server\BEA WebLogic preconfigured\SNMP, ESNMP:BEA-WEBLOGIC-MIB,

The installation is finished and the JMX data of dynaTrace 3.0 is now available in SilkPerformer.

How can I add dynaTrace 3.0 JMX data?

Open "Silk Performance Explorer" and choose "Monitor" -> "Add Data Source". In the "Data Source Wizard" choose "Select from predefined Data Source" and click "Next". Open "Application in-Depth" -> "dynaTrace" -> "dynaTrace 3.0" and click "Next".

Fill in the correct data in the connection parameters dialog:

Choose the JMX values you want to monitor: