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 no longer supported / maintained and you should contemplate to move to the AppMon latest Release Notes (6.5)!
We will not let you down if you have a problem, but it will have lower priority!

November 30th, 2012

The Compuware APM Business Unit is proud to present dynaTrace 5. dynaTrace 5 is the industry's first continuous transaction-based application performance management solution that spans both the mainframe and distributed application environments, all from one single APM system. Additionally, this release includes other enhancements to improve both productivity and quality.

1. Compuware APM for Mainframe

dynaTrace 5 now extends PurePath Technology into mainframe z/OS CICS environments. Though the z/OS CICS agent differs technically from the other agents, e.g. the Java or .NET Agents, the new agent brings all the well known PurePath benefits to the mainframe and distributed architectures that connect to the mainframe environment.

PurePath for z/OS CICS

After the CICS agent is deployed into all LPARs and CICS regions to be monitored, automatic topology discovery detects all the dependencies between:

  • the distributed world and CICS
  • between different CICS regions
  • between CICS and DB2.

Execution time measurements and automatic error detection allow for identifying the distributed or mainframe tier that caused the problem. Drill down into the root cause is also provided. End-to-end visibility into mainframe calls helps architects save expensive mainframe CPU cycles by now enabling IT to remove unnecessary calls made from the distributed world, that were previously hidden in the complexity. By bringing mainframe CPU time measurements into an end-user or end-to-end context with dynaTrace Business Transaction capabilities, IT operators and application owners can now quantify mainframe costs in business-relevant terms.

Finger pointing between distributed and mainframe teams will be a thing of the past, as deep factual detail available for every single user request will enable a collaborative analysis of facts.

Strobe Integration

The dynaTrace CICS agent brings end-to-end visibility and dependency detection to CICS transactions and programs and helps IT to understand why a CICS program is slow, and if the root cause are DB2, Websphere MQ or CICS calls. If the problem is within the Cobol or PL/I code of the CICS program (you already know with dynaTrace that it is not due to DB2, MQ or other CICS programs called), you can directly start a Strobe measurement from dynaTrace to detailed drill downs. Strobe is Compuware's leading mainframe profiling solution, that can give you any detail on the executed CICS programs as well as deep visibility into the internals of other mainframe environments such as DB2 and MQ.

2. UEM: Broader, Deeper and Easier to Use

dynaTrace 5 brings important improvements to UEM that enable you to use dynaTrace across more applications, look deeper into applications, and save time during deployments by avoiding common pitfalls:

  • dynaTrace 5 UEM now supports applications that are running on Oracle HTTP server 10, 11 and Apache 2.4.
  • The UEM Health Check functionality allows you to test, with a single click, if auto-instrumentation of all applications you want to monitor with UEM was successful and provides help if you need to make changes.
  • The new JavaScript ADK allows you to manually instrument technologies such as Flash and Silverlight and monitor them with dynaTrace UEM.
  • dynaTrace 5's GeoIP support and database has been updated to support IPv6 addresses

Other dynaTrace 5 improvements on UEM include:

3. Deeper Integration of the dynaTrace Product Family

dynaTrace 5 DTM (Deep Transaction Management) and UEM focuses strongly on agent-based UEM and transaction-based deep end-to-end monitoring of your Java/.NET/Webserver/mainframe applications.
dynaTrace Data Center Real User Monitoring (DC RUM) 12, Compuware's agentless network-based monitoring solution, complements DTM by focusing on fault domain isolation in complex and heterogeneous environments (including SAP, CISCO, Citrix, ...). The following enhancements to the integration of the products make it easier to monitor and resolve issues faster:

Please note that DC RUM version 12.0.2 is a prerequisite for the integration with dynaTrace 5.

4. Leading Edge Technology Support

dynaTrace 5 ensures that you can trace even the newest platforms and technologies. New support includes:

  • WebSphere 8.5
  • WebLogic 12
  • WebMethods IS 8.2
  • Mule internal messaging
  • WebSphere MB 7 on Linux
  • Cosminexus 8 (with Hitachi 1.5 JVM)
  • Apache 2.4
  • Oracle HTTP Server 10, 11
  • WebSphere MQ tagging (for Java, .NET and CICS)

See the Supported Technologies matrix below for details.

5. Fault Tolerant by Default

Misconfigured Business Transaction Detection

On some occasions, improperly configured Business Transactions would have created a large number of split measures and thereby overloading the attached database servers and leading to a loss of monitoring data. To prevent this from happening, dynaTrace 5 automatically disables Business Transactions when they produce more than 50,000 split measures. The picture below shows the Start Center alert that is generated when such a Business Transaction is detected. The alerts also provides help on how to resolve the configuration problem.

Please Validate after Upgrade

Icon

In the (rare) situation that you really need a few Business Transactions that have to create more than 50,000 split measures, after upgrading to dynaTrace 5, in the Start Center, configure an exception for the particular Business Transaction(s).

Default Sensor Settings

For compatibility reasons, existing System Profiles are not changed when migrating from previous versions to dynaTrace 5. However, new System Profiles are created with default settings that ensure dynaTrace creates very low overhead when deployed in production. Defaults include:

  • Logging only captures SEVERE, FATAL and ERROR messages
  • Limited number stacktraces captured per second on exceptions
  • JNDI turned off
  • SQL capture length reduced to 512 characters

Additional Improvements and Changes

Apart from the major enhancements described above 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:

Faster Client Response Times

For all Dashlets that access PurePath data (e.g. PurePath-, Transaction Flow-, Response Time Hotspots Dashlets) the time it takes to display results has been reduced by upto 5x. The improvements will be especially noticeable when many users access the system simultaneously or you are analyzing longer time frames. 

If you are using HTTP tunneling to access the dynaTrace server with a dynaTrace client through firewalls/proxies, you will benefit from an improvement that now makes tunneling as fast as direct access, effectively reducing response time by 2-3x.

Web Page Performance Dashlet

PurePath Crossing dynaTrace Servers

A PurePath that is started on an dynaTrace agent that is connected to dynaTrace server A and continues on an agent that is connected to another dynaTrace server B, is now treated consistently as if there was no PurePath on Server A by Server B, which means that in most situations in the above scenario there will be two PurePath on the two different dynaTrace Servers.

Others

News from the APM Community

Out of many APM Community contributions we want to highlight two here:


The Server Time Line Dashlet allows e.g. water-fall, histogram and scatter plot visualization of PurePath.

Better rich client support brings UEM to rich client applications.

Please notice that APM Community contributions are usually experimental features that are supported by Compuware, if you have questions or problems with these add-ons you can post them on the community portal.

License Changes

Due to the new features and supported environments in dynaTrace 5 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 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 5.0 license.

Please be aware that Web Server Agent licensing is enforced in version 5.0, too. Please check what number of Agents are covered after conversion / upgrade of your license or talk to sales, if you are unsure.

Resolved Issues

dynaTrace 5 contains more than 150 quality improvements, including the following issues that have been resolved:

  • Process Health Dashboard does not work correctly for IBM JVM 2.6
  • Host monitoring on Solaris 10 Sparc 31-bit may deliver wrong network utilization measurements
  • Business Transaction Dashlet is not reportable via REST interface
  • Message Broker agent may cause failing SOAP calls
  • IIS application pool names are not added to the agent name
  • The Java Agent can cause deadlocks in very rare high load situations
  • Web Server Agent on AIX PPC 32 doesn't start
  • Web Service Dashlet not showing data when CXF framework used
  • Message Broker Agent causing errors with an Execution Group if specific header value is not present
  • Monitoring plugins that create dynamic measures are only working on embedded collector
  • On .NET 4.0 certain PurePath are not started correctly

Known Issues

While the new release of dynaTrace has been tested extensively to ensure it works with all supported platforms and technologies, certain issues cannot be addressed by the product. This section provides links to more information on the issues you might run into. Please refer to the Knowledge Base for other workarounds and tips.

Additional Information

Software and Hardware Requirements

Icon

This section describes 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 which depend 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, HP-UX PARISC, HP-UX IA64
  • Oracle (Sun) JVM, IBM JVM, JRockit JVM, HP JVM
  • 10MB disk space

dynaTrace Server

  • Windows 7/Vista/XP or Server >= 2003 with latest service pack; Linux x86/x64 with a recent kernel >= 2.6; 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
  • Minimum 1.5 GB disk space
  • Minimum 1GB, typical 4-12 GB memory

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

dynaTrace Collector

  • Windows 7/Vista/XP or Server >= 2003 with latest service pack; Linux x86/x64 with a recent kernel >= 2.6; 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 store the data. Out of the box, dynaTrace uses an embedded database for demo / testing purposes. Any production installation of dynaTrace should use one of the following database management systems in the quoted (minimum) version(s) 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 the Deployment Guide.

Supported Java Virtual Machines

OS

Architecture

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

IBM JVM
7.0, 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

Supported Web Servers for UEM

OS

Architecture

Apache Web Server
2.0, 2.2, 2.4

Microsoft IIS
6, 7, 7.5

IBM HTTP Server (IHS) 6, 7

Oracle Http Server 10, 11

Windows

x86/x64

(tick)

(tick)

(tick)

(tick)

Linux

x86/x64

(tick)

 

(tick)

(tick)

Solaris 8+

SPARC 32/64

(tick)

 

(tick)

(tick)

AIX 5.2, 6.1

P32/P64

(tick)

 

(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/8.5
C Oracle WebLogic 8.1 (SP3+)
C Oracle WebLogic 9/9.1/9.2/10/11g/12
C Oracle Application Server 9i, 10g   
C JBoss 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 WebMethods 8.2
C Mule 1.x / 2.x / 3.x
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 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-12.1
S JBoss Connection Pool 4.0-7.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, Linux 64bit, zLinux (64bit) 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 6, 7
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/12
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 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-16 
S Internet Explorer 6/7/8/9

Mainframe Environments

OS for Mobile ADK

C IBM z/OS 1.12, 1.13
C IBM CICS Transaction Server 4.1, 4.2   
C IBM WebSphere MQ 7.0, 7.1  
C IBM DB2 v9, v10

C Apple iOS 4.2+
C Google Android 2.2+

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 about the planned end of life for a given version as well as providing manageable upgrade paths for even the largest deployments. Typically we support the last two minor versions (now 5.0) as well as the last minor version of the previous major version (currently 4.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. As an exception (and extension) to our general end of life policy, we are continuing support for 3.5.2 and 4.1 until April 2013.

Support Level Overview

dynaTrace
version

On-demand
support

Projected
end of life

5

(plus)

 

4.2

(plus)

 

4.1

(plus) *

April 2013

4

(minus)

 

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

Announcement of Platform Support Changes

The dynaTrace 5 release discontinues support for the following RDBMS systems for the performance warehouse:

  • SQL Sever 2000/2005
  • DB2 prior to 9.7
  • Postgre 8.3