Skip to end of metadata
Go to start of metadata

December 23rd, 2011

The dynaTrace team is proud to present dynaTrace 4.1. With a focus on extending User Experience Management, and making dynaTrace easy to configure and maintain, this release contains a number of new features and improvements that will help you be more productive. See below on how dynaTrace 4.1 will change your day.  

1. User Experience Management extended to 3rd Party Web Content

How does third party content from a CDN or an Ad server impact the user experience of your website? How fast is your CDN in the US versus Europe or Asia and does it deliver what is promised? These and more questions can be answered with a single look at the dynaTrace 3rd Party Content Analysis.

Granular Geo Location - Get to Know Your Users!

Are 95% of your online customers living in Germany? Do you want to understand their user experience and create business reports per federal state? You can now do this for all countries, not just the USA, and in a more intuitive way.

User Experience Management for Mobile Apps (Experimental)

dynaTrace 4 delivered User Experience Management (UEM³) to understand how your end users experience your websites. Now even mobile apps running on an iPhone or Android-based smart phone can make use of UEM - to make sure you deliver an optimum experience of all your users regardless of the device they are using.

2. Optimized for Enterprise Environments

dynaTrace has been designed with a focus on enterprise environments, and with dynaTrace 4.1 we have listened to our customers and made it even easier to roll out, maintain, and upgrade dynaTrace in large scale environments.

Bootstrap or Auto-Update or Zero-Maintenance Agents

dynaTrace 4.1 now automatically updates Java and .NET Agents to the same version as the dynaTrace Server. So, whenever you install an update for dynaTrace: The next time your application restarts, Agents are updated to the latest version. (applies to Java and .NET Agents in 4.1) Until the next restart of your application, the previous Agent version remains fully functional, ensuring you don't lose a single transaction. Zero-maintenance Agents for highest productivity and lowest TCO!

More Efficiency, Higher Scalability

A big focus area of dynaTrace 4.1 is improved scalability and performance. The dynaTrace Server performance has been further optimized and now dynaTrace supports up to 750 Agents providing visibility into each single transaction. This means dynaTrace 4.1 officially supports 50% more Agents than dynaTrace 4. Additionally, our optimally performing sensors have become even smarter, greatly reducing the network traffic to the dynaTrace Collector and Server. The network related improvements ensure that even under the highest peak load dynaTrace does not put a major strain on your network and you still get all the data you need to fully understand each single transaction:

  • The logging Sensors for Java and .NET now cache the log messages, achieving a reduction in network traffic of around 70% for typical enterprise applications.
  • The database Sensors (JDBC and ADO.NET) reduce network traffic by 50%-90% depending on the nature of your applications.
  • The exception Sensors for both Java and .NET use a new technology to transmit the stack traces reducing the network traffic by around 80%.
  • The Servlet Sensor has been optimized for all common Java 5 Servlet interfaces reducing the absolute run-time overhead by well over 60%.

Easy Deployment and Integration

  • The LDAP support of dynaTrace now fully supports nested user groups, enabling you to easily roll out dynaTrace to different user groups - even in complex enterprise environments.
  • dynaTrace provides fully automatic installation of FastPacks and updates by just dropping the files into the deployment directory - and next time the dynaTrace server is restarted, everything is installed across all components.
  • dynaTrace 4.1 provides additional REST automation capabilities to store or export sessions and even download them directly - enabling seamless integration into your existing infrastructure.
  • When deploying in complex environments, it is essential that dynaTrace is configured to match existing naming conventions. To make that easier you can now match Agent names with regular expressions to the correct Agent Groups.

3. Trace Across WebSphere Message Broker


As the first APM solution in the industry dynaTrace provides full support for WebSphere Message Broker allowing you to get full transactional visibility into the number one enterprise middleware component. Environments that are using the Message Broker primarily as a gateway from the distributed world into the mainframe, will get more visibility into the mainframe by actually measuring time spent on mainframe calls inside the Message Broker's workflow.

4. Browser Diagnostics Visualized

dynaTrace provides unparalleled details about the performance of your browser based applications in Internet Explorer and Firefox. And to make the information even easier to understand and show what it means for the user, dynaTrace now takes periodic screenshots of the browser window to show what happens when and in what sequence the browser renders the locations of your web page. dynaTrace 4.1 also provides more metrics in the performance report allowing to easily export all browser performance metrics that are collected by dynaTrace. Along with timer based performance numbers dynaTrace makes Browser Diagnostics a repeatable part of your development process.

5. Real Time Business Metrics Made Easy

dynaTrace 4.1 provides even more detailed business data while at the same time making your business transactions much easier to set-up and maintain.
With dynaTrace 4.1 you will typically not have to manually place any sensors. While dynaTrace 4.0 made life a lot easier by introducing auto-sensors for performance measurements, 4.1 is extending this to user-defined business transactions and measures that are measuring e.g. method response times: dynaTrace 4.1 is automatically taking care of the necessary sensor placement steps.

6. Leading Edge Technology Support

dynaTrace continues to support the latest versions of all major technologies. Be it cloud technologies, Java 7, or Browser Diagnostics of the latest Internet Explorer and Firefox versions - dynaTrace can trace it. Specifically with dynaTrace 4.1 we provide best practices for deploying dynaTrace in the Microsoft Azure cloud - including using the Microsoft Azure SQL database as a Performance Warehouse for the dynaTrace Server.

Integration with the Gomez Product Line

dynaTrace 4.1 provides seamless integration with Gomez DC-RUM, allowing a user to drill down from the web interface of Analysis Server directly to the dynaTrace Client - full root cause information with a single click.

Additional Improvements and Changes

Apart from the big new features dynaTrace 4.1 also contains a number of small improvements and changes. The most important ones are listed below:

  • Improved zoom functionality for the Sequence Diagram
  • Disk space used for Continuous Session Storage is now defaulted to 250GB instead of 1000GB
  • Percentile Information is by default only stored for result measures of Business Transactions
  • By default the UEM sensor is not enabled anymore for new Agent Groups
  • The UEM JavaScript Agent is now injected after all meta tags for improved compatibility with Internet Explorer
  • The PurePath Dashlet now uses breakdown bars to visualize the timings of a complete PurePath and each method call - see at a glance whether you have a synchronization or a CPU problem:

Resolved Issues

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

  • JavaScript Agent causes authentication challenge on enterprise proxy on request to address 0.0.0.0
  • Reporting of Visits Dashlet is not possible
  • Business Transaction is not analyzed, if the name contains '(' or ')'
  • Rate measures cannot be added to Dynamic Measure Matrix Dashlet
  • Memory Snapshots triggered on Out-of-Memory Errors are locked, filling up diskspace
  • Placing JMS sensor can cause dynaTrace Server, Collector, and Agents to disconnect from one another
  • Threads started within a PurePath are not visible under certain conditions
  • Copy/Paste of APIs from one System Profile to another does not work
  • Calculation measure does not work when using certain combinations of inputs
  • API Breakdown and other dashlets missing from drill down list for Web Requests
  • Open Dashboard Dialog leads to "Invalid thread access" if client.properties file cannot be written
  • Importing an Offline Session may lead to an exception on the dynaTrace Server
  • JDBC Sensor breaks when org.logicalcobwebs.proxool.ConnectionPool is used
  • JDBC Sensor may cause exceptions during start up of WAS 6.0
  • Database recognition does not work for some DB2 calls
  • Database dashlet incorrectly compares sessions when using Tomcat or c3p0 connection pooling
  • Database name shows as generic for certain ADO.NET Drivers
  • DB Connection Pool value not correctly displayed in imported session that is filtered
  • Using the URL Monitor Plugin without POST data fails
  • VS2010 plugin not working with dynaTrace 4

Support related Issues (visible for employees only)

Support related fixes in dynaTrace 4.1

Known Problems

While our team is striving to provide a world-class customer experience, it is not always in our hands to resolve all issues e.g. due to third party constraints or known bugs in other technologies. This section provides a heads-up on common problems you might run into. Check out the Knowledge Base for 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, 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 - NOTE: Windows 2000 is not supported anymore
  • 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:

  • Oracle 10g/11g
  • Microsoft SQL Server 2000/2005/2008
  • IBM DB2 Version 9
  • PostgreSQL 8.3, 9.1

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 officially supported by dynaTrace

Supported .NET Platforms*

 

Windows
x86/x64
32 bit

Windows
x64
64 bit

.NET 1.1

(tick)

n.a.

.NET 2.0

(tick)

(tick)

.NET 3.0

(tick)

(tick)

.NET 3.5

(tick)

(tick)

.NET 4.0

(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

Microsoft IIS
6,7,7.5

IBM HTTP Server 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

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

Application Servers

Databases and Connection Pools

Operating Systems (Platforms)

C IBM WebSphere 5.1/6/6.1/7
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
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 MS COM+ Component Services for .NET
S Adobe LiveCycle
S SpringSource dm Server
S Fujitsu Interstage 9
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

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

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
C Oracle Service Bus
C Fuse ESB
S Oracle SOA Suite
S SOA Software Service Manager
S Apache OpenEJB

C RMI / IIOP
C RMI / JRMP
C RMI / T3
C .NET Remoting
C ORMI
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
C Oracle WebLogic 8.1/9/9.1/9.2/10/11g
C .NET WebServices
C AXIS 1.4
C AXIS2 1.3
C Hessian 2.1/3/3.1/3.2
C Oracle WebServices
C JAX WebServices
C Codehaus XFire 1.2
C Apache HttpClient 1
S Apache CXF 2.2
S SAP Netweaver
S WebMethods Glue

C Hibernate
C Struts 1.x/2.x
C AWT/Swing/RCP/WPF/WinForms
S Spring
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

Compatible with any JavaScript enabled browser
Fully supported:
S Internet Explorer 6+
S Firefox 3.5+
S Safari 4+
S Chrome 10+

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

S Firefox 3.6, 4, 5, 6, 7, 8, 9beta
S Internet Explorer 6, 7, 8, 9

Please see the Known Systems 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 JRE 1.6.0_26 or higher to be installed.

dynaTrace Support Levels and End of Life Policy

dynaTrace is committed to providing effective and reliable support for the entire product-line on all supported platforms and technologies. Active maintenance and large scale testing is performed on the latest two generally available versions (now dynaTrace 4 and 4.1) and the latest release of the previous major version (now dynaTrace 3.5.2). For the latest versions dynaTrace also provides pro-active support. Pro-active support means that dynaTrace provides regular (typically monthly) easy to install updates to the product to ensure that all users of dynaTrace can benefit from the on-going maintenance and testing. The updates contain bugfixes and stability improvements. In some cases also support for new technologies (e.g. Browser Diagnostics for the latest Firefox version) is included in an update, but only on the latest version - not for dynaTrace 3.5.2.

This policy ensures that clients can always stay on a pro-actively 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

Pro-active
support

On-demand
support

Projected
end-of-life

4.1

(plus)

(plus)

 

4

(plus)

(plus)

 

3.5.2

(minus)

(plus)

 

3.5.1, 3.5.0

(minus)

(plus) *

April 2012

3.2.1, 3.2.0

(minus)

(minus)

January 2012

3.1 and earlier

(minus)

(minus)

 

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

Announcement of Support Changes

  • The dynaTrace 4.1 release does not support Windows 2000 environments for Agent, Collector, and Server.
  • The Web Transaction Monitor Plug-In is deprecated with the dynaTrace 4.1 release and will not be supported with the next major release. dynaTrace recommends  using Gomez Synthetic Monitoring for new projects.