Skip to end of metadata
Go to start of metadata

Click here to save the release notes as PDF.


 

Unsupported Version!

Icon

This version is totally outdated / no longer supported / maintained and you should move to the AppMon latest Release Notes (6.5)!

July 26th, 2012

The Compuware APM Business Unit is proud to present dynaTrace 4.2. With a focus on an improved out-of-the-box-experience and zero configuration system monitoring dynaTrace has become much more accessible and provides more value faster. See below for all the detailed improvements and extensions of dynaTrace and find out what dynaTrace 4.2 can do to make your organization more productive.

1. Smart Monitoring Made Easy

A big focus of dynaTrace 4.2 has been making monitoring easy. A new workflow driven user interface guides you through the different system and application level aspects of your deployments, making dynaTrace easy to use even for the casual user. The all new Application Overview - that comes out-of-the-box without any manual configuration shows you all your applications, and guides you through the transactional and system based monitoring aspects, if you need to look into the details.

Reliable Alerts with Self-Learning Baselining

dynaTrace 4.2 finally delivers on the industry promise of a baselining approach that automatically detects anomalies and alerts reliably. Typical baselining approaches rely on averages and standard deviations (implicitly assuming standard distributions where there are none) for alerting. Often this results in more false alerts and not fewer. dynaTrace 4.2 uses multiple advanced statistical models that are specific to different types of measurements - the failure rate or the throughput of an application are differently distributed than the response time. Even in highly dynamic environments these methods result in 90% fewer alerts while still detecting significant anomalies in less than a minute. Finally alert spamming and manual tuning of alerting rules are a thing of the past.

Advanced Analytics: Integrating System Health with Transactional Information

dynaTrace 4.2 integrates the system monitoring aspect with the transactional PurePath based information delivering for the first time in the industry a solution that automatically detects and maps contributing infrastructure components in real-time to every user request. This allows dynaTrace to correlate system-level problems with business transactions and ultimately with the users that are affected. This enables you on the one hand to pinpoint transactional problems immediately to a specific host or processes-level problem and on the other hand give you the immediate impact of a host problem on your business critical functions and end-users. Making sure you focus on the right things first when things go wrong.

Zero-Configuration System Monitoring


Now dynaTrace automatically monitors all hosts that run an instrumented application process - or, if you want to monitor additional hosts, just install the all new host monitoring agent on the target machines. No more configuration of system monitoring plugins - just run your applications and immediately get all relevant host health information. For process-level monitoring like JVM or CLR metrics dynaTrace now gives you comprehensive pre-configured dashboards that can be accessed directly from the Application Overview or the Transaction Flow.

2. Cloud and Virtualization: Automatic Discovery and Analytics


dynaTrace 4.2 provides enhance cloud capabilities including smart detection of various virtualization platforms and fully integrated cloud specific metrics for technologies such as Cassandra or SQL Azure Database giving you full visibility into your cloud applications.

3. User Experience: Faster, Broader, Optimized


dynaTrace User Experience Management (UEM) extends the list of supported AJAX frameworks for automatic click detection to extJS, Google‘s Web Tool Kit and ZK. dynaTrace also becomes the first APM solution to support the brand-new W3C navigation timing specification. Additionally the JavaScript Agent has been optimized to reduce the network overhead and the number of cookies, further reducing the impact especially for legacy browsers, like Internet Explorer 6.

And UEM automatically provides insight into end-users accessing your web applications from IPv6-based networks.

  • Never Again Update your Webserver Agents manually! All you need to do is update your server and the next time your application restarts, the web server agents are updated to the latest version. Until the next restart of your application, the previous Agent version remains fully functional ensuring you don't lose a single transaction even when upgrading your agents - zero-maintenance agents for highest productivity and lowest TCO.
  • dynaTrace now provides smart installers for the web server agents - just download the package for your operating system and the installer detects what exactly needs to be applied to your web server.
  • dynaTrace 4.2 also brings the possibility to build your own sensor packs for JavaScript Agents. Contact our Enablement Services Team to help you get started with this advanced technology.

User Experience Management for Mobile Apps

After the experimental release of dynaTrace UEM for native mobile Apps in dynaTrace 4.1, we now offer the production ready Agent Development Kit (ADK) to make sure you have the visibility you need - even for native mobile applications on iPhones or Android based smart phones and tablets.

4. External Call Analysis: What Happens Outside Your Data Center?

Current applications depend more and more on external services - be it the ubiquitous Facebook or Twitter integrations on a web page or calls to external systems via Web Services or message queues. Now dynaTrace makes these external calls much more obvious and enables you to understand which third party service affects which parts of your applications, so you can easily spot dependencies and bottlenecks.

5. Leading Edge Technology Support


* Single tier tracing only
dynaTrace 4.2 ensures that you can trace even the latest state of the art platforms and technologies including WebSphere 8, Cosminexus, Interstage, Java 7, .NET 4.5, WebMethods or the latest browser version. See the Supported Technologies Matrix below for details.
Additionally dynaTrace 4.2 provides improved .NET support with better visibility into the .NET ASP.NET framework and a more robust approach to tracing across different App-Domains even in tightly secured environments.

6. Integrating with the Compuware APM Product Family

With this new release of dynaTrace you can now fully leverage other major Compuware APM products. The improved integration with Gomez Web Load Testing gives you complete 360° view of performance, scalability and reliability from an end-users perspective - so you can release you web offering with confidence.
Additionally with the experimental integration with dynaTrace Data Center Real-User Monitoring (DCRUM) you can increase your visibility into components like load-balancers or processes for which you cannot deploy an agent and still drill-down directly to dynaTrace - contact your sales representative, if you are interested in an Early Access Program.

Additional Improvements and Changes

Apart from the major focus points there have been dozens of other enhancements that make dynaTrace easier to use and more productive in many different areas. Here are the most important improvements:

  • dynaTrace now provides a separate access right for decompiling code - so you can now protect the intellectual property of your applications
  • dynaTrace now provides full proxy support for obtaining license information or downloading the latest Geographical Locations Database and SpeedoftheWeb™ data
  • To focus the testing and maintenance effort, dynaTrace no longer supports .NET 1.1 CLRs

Licensing Changes

Due to the new features and supported environments in dynaTrace 4.2 there are also some important licensing changes that you need to be aware of. Please note that you have to upgrade your license when upgrading your dynaTrace deployment. You can now upgrade an existing dynaTrace license on your own with the new self-service license management capabilities of the dynaTrace customer portal at eservices.dynatrace.com. If you need help with that, our Licensing team will gladly help you with transforming your existing license to a new 4.2 license.

UEM Licensing changed from Page Actions to Visits

With Visits becoming a more common metric for websites we are keeping pace and will be moving to visits-based licensing with dynaTrace 4.2. Page Actions will no longer be used as a basis for the dynaTrace UEM volume instead we will automatically convert your dynaTrace UEM volume to the new Visits based system.

If you have any questions regarding the new conversion ratio, please contact your Compuware sales representative.

New Types of Agents

With the release of dynaTrace 4.2 two new types of specialized agents will be available. These new agent types have to be licensed separately, similar to our Java and .Net agents. So if you are interested in this type of functionality, please contact your Compuware sales representative.

WebSphere Message Broker Agent

The WebSphere Message Broker Agent allows tracing through a WebSphere MB deployment, supporting several protocols such as HTTP, JMS as well as MQ.

Host Monitoring Agent

The Host Monitoring Agent provides host information and several host health measures such as CPU and memory usage, network utilization and disk capacity. It can be installed on any host - virtualized or not - and replaces the now deprecated host monitoring plugins for Windows and Unix.

Resolved Issues

All the bugfixes and enhancements that have been addressed in the monthly updates for 4.1 are also incorporated into the dynaTrace 4.2 release. The 4.2 release contains more than 400 quality improvements, here are some important ones:

  • Instrumenting methods with more than 31 arguments may not work
  • URLs with special characters may not be captured correctly
  • JavaScript Agent may cause application errors on Safari
  • Instrumenting the .NET OracleConnection class may cause an exception
  • Virgo Tomcat instrumentation not working without sensor modifications
  • Error Rules based on the redirect target used the request URI instead
  • CPU Usage for AIX Power 5 is based on number of logical processors instead of physical processors
  • Querying non-English performance counters may fail
  • Editing the Geo Locations is not bound to a permission
  • Transaction Flow does not show the database instance names
  • Browser Agent may report the caching ratio as too low for Firefox
  • Top-X filter may not work for dynamic result measures in the Business Transaction Dashlet

Known Problems

While the new release of dynaTrace has been tested extensively to ensure it works with in with all supported platforms and technologies, certain problems can not be addressed by the product. This section provides links to more information on certain problems you might run into. Have a look at the Knowledge Base for other workarounds and many hints.

Additional Information

Software and Hardware Requirements

Icon

This section outlines the minimum system requirements to install dynaTrace. Typically these minimum requirements are suitable for demonstration purposes only. Please refer to the Deployment Guide for production ready hardware requirements - depending on the size of your dynaTrace deployment.

dynaTrace Agent

  • Windows x86/x64, Linux x86/x64, Solaris SPARC 32/64, Solaris x86/x64, AIX 32/64 Power 5, 6 and 7 Architectures, z/OS 31/64 (no host health information available), z/Linux 31/64, Windows IA64, HP-UX PARISC, HP-UX IA64
  • Oracle (Sun) JVM, IBM JVM, JRockit JVM, HP JVM
  • 10MB disk space

dynaTrace Server

  • Windows 7/Vista/XP, 2003/2008 Server, Linux x86/64, Solaris SPARC, Solaris x86/64, AIX Power 5, 6 and 7
    • Windows and Linux installers/packages contain a private 32bit/64bit JRE
    • AIX requires IBM JRE 1.6 SR2+
    • Solaris SPARC and Solaris x86/64 require J2SE 6.0
  • min. 1GB disk space
  • min. 1GB, typical 4-12 GB memory

See the Deployment Guide for detailed hardware recommendations specific to your load.

dynaTrace Collector

  • Windows 7/Vista/XP, 2003/2008 Server, Linux, Solaris SPARC, Solaris x86/64, AIX Power 5, 6 and 7, z/OS, z/Linux, HP-UX
  • Oracle (Sun) JVM 1.6+, IBM JVM 1.6 SR2+, HP JVM 1.6+
  • min. 1GB disk space
  • min. 128MB, typical 1-2GB memory

See the Deployment Guide for more specific hardware recommendations.

dynaTrace Client

  • Windows 7/Vista/XP, 2003/2008 Server, SUSE/RedHat Linux with GTK
    Client not officially supported on 64 bit Linux. Needs (installation of) 32 bit Java, GTK/SWT and libXtst-32.
  • 100MB disk space
  • 1GB memory
  • Minimum screen resolution: 1024x768px

dynaTrace Performance Warehouse

Long term historical data is stored in the dynaTrace Performance Warehouse. The Performance Warehouse uses a relational database to actually store the data. Out-of-the-box dynaTrace uses an embedded database for demo purposes. Any installation of dynaTrace should use one of the following database management systems to host the Performance Warehouse database:

NOTE: dynaTrace supports partitioned tables for high load scenarios for all of the above databases.

To determine the disk space requirements for the dynaTrace Repository upfront you can/should calculate 15GB per 1000 persistent measures (of all System Profiles within the dynaTrace Repository). You can find more details in Deployment Guide.

Supported Java Virtual Machines

OS

Architecture

Oracle (Sun) JVM
7.0, 6.0, 5.0, 1.4.2 32/64bit

IBM JVM
6.0, 5.0, 1.4.2 32/64bit

Oracle JRockit
6.0, 5.0, 1.4.2* 32/64bit

HP JVM
6.0, 5.0, 1.4.2* 32/64bit

Windows

x86/x64

(tick)

(tick)

(tick)

 

Linux

x86/x64

(tick)

(tick)

(tick)

 

Solaris 8+

SPARC 32/64

(tick)

 

(tick)

 

Solaris 10+

x86/x64

(tick)

 

(tick)

 

AIX 5.2, 6.1

P32/P64

 

(tick)

 

 

HP-UX

IA64/PA-RISC2.0

 

 

 

(tick)

z/Linux

z31/z64

 

(tick)

 

 

z/OS

z31/z64

 

(tick)

 

 

*) these 64bit 1.4.2 JVMs are not supported by dynaTrace

Supported .NET Platforms*

 

Windows
x86/x64
32 bit

Windows
x64
64 bit

.NET 2.0

(tick)

(tick)

.NET 3.0

(tick)

(tick)

.NET 3.5

(tick)

(tick)

.NET 4.0

(tick)

(tick)

.NET 4.5**

(tick)

(tick)

n.a. = not applicable
*) .NET is not supported on the Itanium architecture
**) No certified support yet, as of July 2012 only the .NET 4.5 release candidate was available. CPU Sampling is not supported in the .NET 4.5 release candidate.

Supported Web Servers for UEM

OS

Architecture

Apache Web Server
2.0, 2.2

Microsoft IIS
6,7,7.5

IBM HTTP Server (IHS) 6,7

Windows

x86/x64

(tick)

(tick)

(tick)

Linux

x86/x64

(tick)

 

(tick)

Solaris 8+

SPARC 32/64

(tick)

 

(tick)

Solaris 10+

x86/x64

(tick)

 

(tick)

AIX 5.2, 6.1

P32/P64

(tick)

 

(tick)

Supported Application Environments and Technologies

Application Servers

Databases, Connection Pools and BigData Solutions

Operating Systems (Platforms)

C IBM WebSphere 5.1/6/6.1/7/8
C Oracle WebLogic 8.1 (SP3+)
C Oracle WebLogic 9/9.1/9.2/10/11g
C Oracle Application Server 9i, 10g   
C JBoss 3/4/5/
C Apache Tomcat 5/6/7
C Borland Enterprise Server 6.5
C Borland Application Server 6.7
C Sun Java Web Server 6.1
C Sun Java Application Server 8.2/9/9.1
C Microsoft IIS/ASP.NET 6/7/7.5 
C Microsoft SharePoint
S Jetty 6/7/8
S MS COM+ Component Services for .NET
S Adobe LiveCycle
S SpringSource dm Server
S Fujitsu Interstage 8
S Cosminexus 8
S SAP NetWeaver 2004/2007 * 
S ATG Dynamo 6.3.0
S CoreMedia
S ServletExec 4.1
S JRun 4
S ColdFusion 6.1/7
L other/proprietary Java/.NET Servers

*) S when used with supported JVM,
L when used with SAP JVM

Databases:
C IBM DB2 8/9
C Oracle DB 9i/10g/11g
C MS SQL Server 2000/2003/2005/2008
C PostgreSQL
C Java DB
C Generic JDBC drivers and
ADO.NET data providers
(e.g. ODP.NET)

Connection Pools:
S WebSphere Connection Pool 5.0+
S WebLogic Connection Pool 8.1-10.3(11g)
S JBoss Connection Pool 4.0-6.0
S Apache DBCP 1.0-1.4
S Tomcat Connection Pool 1.0.6+
S c3p0 0.8.5+
L generic support is available for
all J2EE connection pools

BigData Solutions:
C Cassandra
S Solr

C Windows 7/Vista/XP
C Windows 2003/2008 Server
C Suse Linux 8+
C RedHat Linux 4+
C AIX 5.2/6.1
C Solaris SPARC 8+
C Solaris 10+ x86/x64
C IBM z/OS 390
C z/Linux SLES 8 SP4
C HP-UX PA-RISC2.0
C HP-UX IA64

ESBs and SOA

Remoting

Messaging

C IBM WebSphere Message Broker 7 *
C Oracle Service Bus
C Fuse ESB
S Oracle SOA Suite
S SOA Software Service Manager
S Apache OpenEJB


*) works only on supported Windows,
AIX, zLinux (32bit) Platfoms

C RMI / IIOP
C RMI / JRMP
C RMI / T3
C .NET Remoting
C ORMI (OC4J 10g R3)
C JBoss Remoting
C WCF
C HTTP Remoting
C XML-RPC.NET

C JMS
C IBM WebSphere MQ 5.1/6/6.1
C Apache Active MQ 4/4.1
C Microsoft MQ 3.0
S TIBCO Rendezvous

Web Service Stacks

Frameworks

LDAP (for User Authentication)

C IBM WebSphere 5.1/6/6.1/7/8
C Oracle WebLogic 8.1/9/9.1/9.2/10/11g
C .NET WebServices
C AXIS 1.4
C AXIS2 1.3 / 1.4 / 1.5 / 1.6
C Hessian 2.1/3/3.1/3.2/4.0
C Oracle WebServices
C JAX WebServices
C Codehaus XFire 1.2
C Apache HttpClient 3.1/4.0/4.1/4.2
C Jetty Http Client 6/7/8
C Apache CXF 2.2/2.3/2.4/2.5/2.6 (exkl. JAX RS)
C Spring Web Services 2.0
S SAP Netweaver
S WebMethods Glue

C Hibernate
C Struts 1.x/2.x
C AWT/Swing/RCP/WPF/WinForms
S Spring Web Services 2.0
S BlazeDS
S Oracle Coherence 
C Applets
others

S Active Directory
S openLDAP

AJAX Frameworks for UEM

Browser Support for UEM

Browser Diagnostics (with plugin)

UEM is compatible with all JavaScript frameworks,
automatic click detection is available for:
S jQuery
S Dojo
S ICEfaces
S extJS
S GWT
S ZK

Compatible with any JavaScript enabled browser
Browsers:
S Internet Explorer 6+
S Firefox 3.5+
S Safari 4+
S Chrome 10+
L Embedded Browser

Mobile Browsers:
S Mobile Safari 4+ (iPhone 3/4/4S, iPad 1/2/3)
S Android Webkit 4.0+

S Firefox 3.6, 4-13
S Internet Explorer 6/7/8/9

Support level: C = certified, S = supported, L = limited support

Please see the SYS section of the Community Portal for details.

Supported Browsers for Web Start

The dynaTrace Java WebStart client can be started with any WebStart compatible browser. Internet Explorer 6+ and Firefox 3+ are certified by dynaTrace. The Java WebStart Client requires a 32-bit JRE 1.6.0_26 or higher to be installed (JRE 1.7 is not supported as of yet).

dynaTrace Support Levels and End of Life Policy

Compuware is committed to providing effective and reliable support for dynaTrace on all supported platforms and technologies. This includes communicating early on about the planned end of life for a given version as well as providing manageable upgrade paths for even the largest deployments. Generally we support the last two minor versions (now 4.2 and 4.1) as well as the last minor version of the previous major version (currently 3.5.2). This ensures that clients can always stay on a well supported version of dynaTrace, even if the upgrade of large systems with various organizational challenges can take a long time to plan and execute. To help you ensure a smooth and predictable upgrade to a new version of dynaTrace our Enablement Services Team will gladly assist you.

Support Level Overview

dynaTrace
Version

On-demand
support

Projected
end-of-life

4.2

(plus)

 

4.1

(plus)

April 2013

4

(plus) *

November 2012

3.5.2

(plus) *

April 2013

3.5.1, 3.5.0

(minus)

 

3.2.1, 3.2.0

(minus)

 

3.1 and earlier

(minus)

 

*) On demand support and FixPacks for these versions are only available for severe production problems

  1. Anonymous (login to see details)

    "IHS" is a common reference to IBMs HTTP Server, which we support. Perhaps it would be helpful to label the IBM HTTP Server as "(IHS)" for those that are looking for that string in this document.

    1. Anonymous (login to see details)

      Hey Joe, (Wanna sound like Jimi Hendrix <g>)
      did a little extra work and checked for occurrences in the 4.2 docs too - as I´m always interested that Confluence gets better in finding and ranking search results. (Still a sore spot, but we´re getting better in tweaking it!)
      Cheers
      G.

  2. Anonymous (login to see details)

    Which agents are supported by a 4.2 server/collector? Just 4.2 or 4.1 as well?

    1. Anonymous (login to see details)

      Hi Eric,
      Agents need to be the same version as Server / Collector and in the 4.1 > 4.2 scenario Java and .Net Agents update themselves on connection. You need to update the others manually.
      Please see https://apmcommunity.compuware.com/community/display/DOCDT42/Upgrade+and+Migration+Guide+4.1+to+4.2#UpgradeandMigrationGuide4.1to4.2-UpgradeAgents.

      Cheers
      G.