Skip to end of metadata
Go to start of metadata

July 17th, 2014

The Compuware APM team is proud to present dynaTrace 6.

This major product release brings fundamental architectural changes that provide scalability and ease of use for both small and large environments. Real user monitoring has never been easier with automatic insight into iOS and Swift-based mobile apps, in-flight visit analysis during peak events, and full transaction tracing through NGINX and iPlanet. APMaaS is now more scalable, more secure, and provides additional deployment options to bypass content delivery networks. With dynaTrace 6, full end-to-end insight is provided on IBM IMS platforms and newly supported technologies, which include TIBCO, Java 8, iOS 8, and Javascript frameworks such as Angular.js, PHP on Windows, and many more.

Thank you for your feedback in the forums. We're always happy to respond your feedback by adding enhancements such as thread analysis for .NET apps, deep object access, and PHPUnit.


1. World's Most Scalable "All Transactions" APM Solution

Game-Changing Architectural Improvements

Forward-looking architectural improvements have been made to optimize scalability and reliability. Although this release is only the first step, dynaTrace Server can now handle about 10% more transactions,  20% more Agents, and 5x more simultaneous Client analyses . In addition, the communication between Agents and Collectors has been reduced by 90% during instrumentation and the 64-bit dynaTrace Client is perfect for memory intensive tasks, such as longer time frames and powerful transaction-based root cause analytics.

Failover for Agents and Collectors

With dynaTrace 6, every Agent automatically connects to a Collector group to guarantee that all transactions are captured even during peak times, infrastructure upgrades or maintenance windows. In addition, high availability is provided with automatic f ailover of Agents and Collectors Bandwidth usage has been optimized by enabling compression between the Server and Collector by default.

Simplified Sizing and Recommendations

Many sizing questions are now addressed automatically with the new sizing configuration dialog box which offers five sizing variants (Demo, S, M, L, and XL). "What hardware is needed for a dynaTrace Server?" "How many Agents can be connected to that Server?" "How many Clients can be served?" "Is there a transaction limit?" All these questions and more are now answered for you automatically. Based on available hardware (CPU cores, memory), dynaTrace checks for sufficient resources and directs you to any bottlenecks (for example, low memory or insufficient CPU cores). This "smart sizing" approach enables you to maximize the resources in your dynaTrace environment (by adding Agents) without risking overload and data loss during peak usage times.

Multi-Year Performance History Available at your Fingertips

The Performance Warehouse DB stores time series system monitoring data (such as CPU and memory usage) and PurePath timings. Historical data can be consolidated to one of three levels of granularity following daily cleanup: high granularity (minute-by-minute data), medium granularity (hour-by-hour), and low granularity (day-by-day). For Oracle and Microsoft SQL Server, this cleanup now runs 4x faster than in previous releases, enabling you to store huge amounts of historical data. Based on your requirements for annual business transaction comparisons, data can be stored for weeks, months, and even years.

Product and Security Update Alerts

Although security updates and product issues are posted immediately to the APM Community, such updates can sometimes be overlooked. For this reason, dynaTrace 6 detects when important updates are available and notifies you immediately. FixPack notifications now appear automatically and include detailed information regarding updates. You'll know immediately if an issue comes up that affects you.

Stay in Control of Update Rollouts

Managing large environments can be a challenging and cumbersome task. Therefore it's critical that the configuration, rollout, and administration of your monitoring solution be stress-free. dynaTrace 6 lets you know when an update is available and guides you through a controlled rollout process, giving you options such as performing a complete update, or selectively updating bootstrapped Agents within Agent Groups or Hosts. In this way, dynaTrace now adapts to your rollout approach. You can now test a FixPack for a single application or host without affecting any other applications!

Know When Your Help Is Needed...

dynaTrace 6 comes with built-in smart notifications that will make life easier for dynaTrace administrators. Administrators no longer need to wonder "Is the dynaTrace Server low on disk storage or unable to connect to the Performance Warehouse?" "Has the license expired?" The dynaTrace Client now tells you when immediate action is required and provides a simple traffic light to convey dynaTrace Server health. Stay up-to-date with the status of the Memory A nalysis Server, Collectors, and expensive or broken business transactions and licenses.

2. Easy Enterprise-Grade APM for Everyone

Connecting Your Apps Has Never Been Easier

You'll be up and ready in minutes! For first-time users, we've simplified the setup process for connecting your application components to dynaTrace. A setup wizard guides you through all the necessary tasks and helps you resolve setup issues.

Gain Business Insight into Web Apps Within Seconds

Sometimes it's not required that you define complex business transaction rules to manage your critical transactions. If you're running a web application with clearly defined URI patterns, those patterns may fit well for your purposes. The new Business Transaction Configuration feature allows you to browse your requests in intuitively organized groups, with just enough metadata to enable you to create web-based business transactions in only a few clicks. 

Capitalize on the Industry's Only Accurate Business Transactions

What if a business transaction method needs to be grouped by customer, but the methods have signatures like addToCart(SessionStates, Item newItem?) Information about the customer is in a Customer object inside the SessionState object. With standard method argument capturing, the SessionState object could be retrieved, but the Customer object inside the SessionState object could not. Deep object access allows you to define an accessor that specifies how to reach such deep objects and capture them!

Portable Unzip-And-Go dynaTrace Client for Windows

Now you can conveniently run the dynaTrace Client on Windows from your memory stick or any other removable device – without any installation. The rollout of a new Client version or the ability to work with different versions on one machine has never been easier.

Save Time by Configuring Multiple Agent Groups at Once

With the new bulk change function, you can quickly apply changes from a certain sensor pack to all other available Agent Groups and related sensors. Changing and maintaining an active configuration is now done in three easy steps, saving you effort and cost.

  • Placement of sensors in all Agent Groups (where available).
  • Change sensor properties and apply changes to all Agent Groups.
  • Change sensor capture settings for sensor packs.

Be in Control of your License Consumption

The new license reservations feature gives you full control over which Agents are being consumed by which system. Finally you can make sure that each department has access to the amount of Agents they need and are entitled to. Agents can be reserved based on system profile down to specific Agent Groups in a simple configuration dialog box. Its also possible to overbook so that even before rolling out into production, you can make sure that the right amount of licenses gets assigned to the correct profiles.

 

3. Industry's First Support of Swift and Automatic Insight Into iOS Apps 

dynaTrace 6 provides full and seamless support of Apple's Swift, which is the easiest approach to create apps for iOS devices with iOS 8 and beyond.

Auto-Instrumentation for iOS Apps on Mobile and Tablet Devices

Auto-Instrumentation for iOS means that there is no need to change a single line of code. It's as simple as adding our Agent to your app. The Agent automatically captures user actions, network requests, and crashes – all the information you need to know whether or not your customers are satisfied. And if they're not satisfied, dynaTrace helps you figure out why.

4. Smart Analytics for Mobile Apps from Swipe-to-SQL

The release of dynaTrace 6 makes it even easier for you to monitor your mobile apps. We've greatly improved auto-instrumentation for Android and we've added auto-instrumentation for iOS, literally turning our mobile app ADKs into mobile app agents.

User Actions are Automatically Detected

We've made our mobile Agents smarter by programming them to detect user input and automatically create user actions. Automatically generated user actions contain all lifecycle events and network requests that have an impact on response time – similar to the user actions that are captured by the JavaScript Agent. Of course you can still use manual instrumentation to add any details that you need to see – for example when to report a certain error – though in most cases this isn't necessary.

Identify Slow Web Requests Called by Mobile Apps

Have you ever wondered if slow network requests were impacting the user experience of your applications? With dynaTrace it's easy to see which web requests are slowing down your user actions. We've added measures for web request response times, web request errors, and requests to third party hosts – all of which are now visible in the transaction flow.

Another significant feature is the ability to split visits by app versions. This allows you to perform calculations such as the crash rate for each of your app versions.

New JavaScript Agent for Hybrid Apps

With dynaTrace 5.6, we released the first APM solution that supports hybrid mobile apps. With dynaTrace 6, we've improved support for hybrid mobile apps. It's now possible to inject the JavaScript Agent into HTML content that's loaded by your application. This means that you get the same level of visibility into your hybrid mobile apps as you do with standard web applications – for example page loads and AJAX actions.

5. World's First Transactional APM Solution for IBM IMS

24/7 End-to-End Visibility into IBM IMS

dynaTrace was the first APM solution to offer PurePath for CICS. dynaTrace 6 now traces transactions into IMS with end-to-end visibility into each user request! With transaction triggering through IMS SOAP GatewayIMS Connect API and WebSphere MQ IMS Bridge  are followed automatically, showing each hop from the IMS control region to the IMS application region, including all DB2 and DL/I calls! 

Database Aggregation for IBM CICS and IBM IMS

It's not uncommon for a single mainframe transaction to have hundreds or even thousands of database statements. These statements are usually executed quickly, so it makes no sense to analyze and display each statement. The DB aggregation for CICS and IMS feature generates a database summary in which identical database statements are aggregated into a single node. This results in a clearly arranged PurePath and makes it easy for you to identify wasted MIPS (e.g., using multi -row f etch statements instead of single fetch statements)!

Handle IBM Mainframe Load with Ease

Mainframes are mature back-end systems for enterprise companies. Big and complex application landscapes, from mobile to green screen, make extensive use of z/OS based systems. This generates a huge number of transactions 24/7. This is why dynaTrace 6 comes with new defaults for CICS and additional configuration settings that focus on the most important data and minimize production overhead by up to 50%. The same defaults and settings are also used for IMS!

 

6. Most Powerful and Easiest Trace-Through Solution for NGINX

We are proud to announce the availability of the brand-new dynaTrace Agent for  NGINX. NGINX is a modern open-source web server that is gaining popularity because it provides high performance and uses little memory. Unlike other APM solutions, dynaTrace 6 does much more than just monitor NGINX – real user trace-through is automatically provided, failed network requests are detected and network timings are captured. Even when NGINX is used as a reverse proxy in front of application servers, transaction tracing instantly provides facts to resolve customer complaints.

PHP for Windows

In response to several customer requests, the PHP Agent is now available on Windows. Whether it's running behind an Apache, IIS or stand alone, the dynaTrace Agent for PHP gives you deep insight into your PHP applications with auto sensors.

7. In-Flight Real User Visibility For Holiday Readiness and Peak Events

With dynaTrace 6, real user visits appear immediately on the world map and allow in-flight visit analysis while customers are using the mobile or web app. Furthermore, all server-side web requests are attached to visits even without any user interaction; this drastically simplifies root-cause analysis. 

8. APMaaS Now More Scalable, More Secure and With More Deployment Options

In addition to all the exciting new features in version 6, we're offering new capabilities for our SaaS offering. We are happy to announce the introduction of new and bigger environments which allow you to run even more Agents and visits with the same performance on the dynaTrace side that you have come to expect. Newly supported technologies such as Nginx and iPlanet, together with all the other mobile, web servers, and back-end technologies available in dynaTrace, now enables complete end-to-end monitoring.

As part of our ongoing security initiative in dynaTrace 6 for both APMaaS and on-premise, we performed a complete overhaul of password handling. A separate secure keystore to manage dynaTrace passwords was added to significantly improve the security of our authentication system. We've also updated our encoding algorithms to adhere to current standards, including AES 256-bit encryption and refreshing our security certificates in the product to guarantee a 100% Heartbleed-free product.

 

More Deployment Options with Content Delivery Network Bypass

Customers who use content delivery networks like Akamai, Amazon Cloudfront or Limelight and don't want to send any real user metrics through an external service, can now bypass their CDN to retain 100% real user visibility. This saves cost by reducing the number of hits on your CDN and enables on-premise and cloud-based deployment options for real user monitoring where the monitor signal needs to be sent to a different web server.

For customers using the new environments, we're happy to offer new memory analysis features that enable you to perform memory snapshots and in-depth memory analytics as a unique feature in the APM as a service space, making our SaaS solution a 100% feature-to-feature match with our on-premise solution.  

dynaTrace 6 is available to all APMaaS customers. Upgrading takes a matter of minutes and requires minimum downtime, but is not mandatory. Please reach out to your Compuware Sales Representative to schedule your update.

9. Thread Analysis for .NET, Business Dashboards and PHP & Web Server Improvements

Thread Analysis for .NET

Thread dumps provide a snapshot of all .NET threads. They offer a powerful means of finding deadlocks, idle or busy thread pools, thread leaks, and more. Additional thread dumps can be used to diagnose performance bottlenecks by comparing the CPU usage of different thread dumps.  Thread dumps can be scheduled, persisted, searched, and grouped. Although this feature is in an early beta-release phase for dynaTrace 6, it's ready for use!

Show your Business Critical Numbers on the Big Screen!

A new dashlet has joined the family. With the new Text and Measurement dashlet, you can now display numeric measures and format them to your liking on custom dashboards. This has some cool applications. For example, you can configure the dashlet to use a low refresh rate. You then have a counter that can display your orders or overall revenue for each day.

PHP Agent Improvements

One of several smaller improvements, a new sensor is available for PHPUnit that integrates your unit tests with dynaTrace Test Automation. Tagging support for PHP Soap Client is also available. We reduced the PDO sensor overhead by 8%. To avoid batch jobs using up valuable PHP Agent licenses, the PHP Agent is now inactive by default for all jobs that are started from the command line. This behavior can be changed in the php.ini file. Also, the PHP Agent now captures memory usage both before PurePath and during peak transaction usage.

Web Server Agent Improvements

Due to some race conditions that arose when several Apache agents tried to launch the master agent at the same time, slave agents no longer attempt to start the master agent. Instead we've added an init.d script that should be used to start the master agent as a service. In order to make migration as easy as possible, this is achieved by adding a setting to the dtwsagent.ini file. If not available (for example, due to upgrade) the slave agents will still attempt to start the master agent.

Performance Warehouse Connection Test

To avoid Performance Warehouse connection issues, Administrators must run connection tests. A new feature validates the database user and all related statements (create, drop, etc.) to ensure that the connection works properly. If a connection test fails, a dialog explains what went wrong. Without a successful test result, connection to the Performance Warehouse is not possible.

UI for Android Auto-Instrumentation

To make auto-instrumentation even easier, we've created a UI that you can download from the Community page. Simply connect your Android phone with a USB cable and start the UI. The UI enables you to select an app, configure settings, and perform instrumentation without the need of an ADB or command line tools. 

PurePath Dashlet Hides Processing Paths

The PurePath dashlet hides processing paths by default to minimize response time on the Client and maximize Server performance. Processing paths can be displayed again by clicking a button above the PurePath table. 

New Defaults for Optimized dynaTrace Server Performance

Maximum PurePath nodes are reduced from 100,000 to 10,000 nodes for all editions.

   

Continuous transaction storage is enabled and optimized for dynaTrace Server throughput.

Filters for Custom Measures

The Measures dialog box now offers an option for displaying only custom created measures.
 

Search for Agent Group

Another usability improvement is the ability to search for an Agent Group in the Agent Group Overview.

Requested Product Enhancements

Based on suggestions and discussions in the Product Feedback and Enhancement Requests forum of the APM Community, we've implemented the following enhancement requests for this release:

10. Agent for iPlanet, TIBCO, Java 8, iOS 8, AngularJS,  NoSQL and much more

New iPlanet Agent

For enterprise-level customers, we're closing another blind spot by introducing the new iPlanet agent. The iPlanet agent handles UEM injection, captures web request timings and supports tagging to the next tier, e.g. to a Weblogic server.


End-to-End PurePath for TIBCO ActiveMatrix Business Works and TIBCO EMS

TIBCO ActiveMatrix BusinessWorks and TIBCO Enterprise Message Service (EMS for Java) are the most commonly used components of TIBCO's ActiveMatrix SOA platform. New support for these technologies provides end-to-end PurePath out-of-the-box, which is a prerequisite for application performance management and error analysis in complex enterprise environments.

On Technology's Cutting Edge: Oracle Java 8

dynaTrace 6 is built to support Oracle Java 8, which was released earlier this year on all platforms.

New Javascript Frameworks for AJAX Action Support 

Real user monitoring for mobile and web has been further improved with out-of-the-box detection of swipes, taps, clicks, and remote calls for AngularJSMooTools, and Prototype.

NoSQL and Big Data Enhancements

In dynaTrace 5.6, we introduced our Hadoop Monitoring dashboard within a community beta program. In version 6, we've taken the next step and completely integrated the Hadoop Monitoring dashboard into dynaTrace. You no longer need to install the Hadoop monitor separately – you get the full Hadoop monitoring experience directly out of the box.

We further extended our insight into Cassandra queries. With dynaTrace 6, you can monitor and troubleshoot Cassandra performance, including newly captured bind values.

We've also updated our support for all NoSQL solutions, including HBase, Casandra, MongoDb, and Hadoop – thereby ensuring that you can use the most recent NoSQL solutions with your favorite performance monitoring solution.

JDBC Connection Pool Support of GlassFish 3.1

dynaTrace 6 now supports GlassFish 3.1 connection pools, including information on URL, pool size, and occupied pool size.

News From the APM Community

Check out our series of Dynatrace Community Webinars. Look for the series called Performance Dashlets Explained as well as other recently recorded webinars that will show you how to become more productive with dynaTrace.

Also take a look at the APM Blog where customers and our Center of Excellence team provide insight into all things APM. For example, take a look at  Fixing Real Problems with Real User Monitoring  by guest bloggers Derek Abing and Brian Perrault.

Extend dynaTrace with the Plugins and Fastpacks provided by the dynaTrace Community.

If you have suggestions about dynaLearn Webinars or ideas about plugins, send us an email at apmcommunity@compuware.com

Featured Plugins

License Changes

Due to the extensive list of new features and improvements in dynaTrace 6, it's necessary that you obtain a new license to migrate from a previous version. As always you can upgrade an existing dynaTrace license on your own using the self-service license management capabilities of the dynaTrace customer portal at eservices.compuwareapm.com. If you require support or have questions, our Licensing team will gladly help you with upgrading your current license to a version 6 license.

Following an upgrade, please make sure that your current license is deactivated correctly. If you're using UEM, ensure that the correct amount of UEM Volume is reissued as UEM Vouchers.

dynaTrace for z/OS uses a MIPS based licensing model running on Compuware's License Management System (LMS) which is available on our download page.The z/OS licenses have to be requested through License_Mgt@compuware.com (not available through eservices.compuwareapm.com).

To align the licensing of the native agent (ADK) on z/OS with dynaTrace for z/OS CICS, IMS and Java, the model is switched from process based to MIPS based in dynaTrace 6.

Resolved Issues

This release contains a number of quality improvements, including the following issues that have been resolved:

  • In rare cases User Actions and User Action PurePaths reports had empty server and network contribution columns.

  • Problem with UEM injection when special none-w3.org-conform terminator tag was used.

  • PHP agent might crashed with UTFDataFormatException when another PHP extension sends error signal before php agent request initialization.

  • PHP agent crashed when curl_multi_exec function has NULL as argument
  • Fixed problem with large, manually recorded sessions (greater than 10GB) where some analyzer runs have been aborted.
  • There were rare cases of .NET agents being uninstrumented because of hash key collisions.
  • Bug in linux kernel version 3.5-rc5 till 3.7.1 could have lead to the memory corruption and VM crash, when using the native agent.

  • Sensor import could have failed, if a FixPack was installed before.

Known Issues

While the new release of dynaTrace has been tested extensively to ensure that it works with all supported platforms and technologies, certain issues cannot be addressed in the product. This section provides links to more information regarding such issues. Please refer to our Knowledge Base for other workarounds and tips.

  • Beginning with version 7, Windows may be installed out of the box with, for example, a 125% zoom level on portable computers.
    On higher zoom levels, the contents of dialogs in the dynaTrace Client may be cut off.
    A simple workaround for this issue is to manually increase the size of the dialogs, or just maximize them.
    Another workaround is to reset the Windows' zoom level back to 100%.
  • System profiles from dynaTrace versions < 4.2 need to be migrated to dynaTrace 5.6 before you can upgrade them to dynaTrace 6.0.
  • Java 7 does not accept weak certificates (i.e. certificates using weak hashing or signing algorithms, for instance MD2 or an RSA key of size < 1024) by default. 
    This might lead to refused connections e.g. when authenticating to a secure LDAP server with a weak certificate.  

Additional Information

Software and Hardware Requirements

Icon

This section describes the minimum system requirements for installing dynaTrace. Typically these minimum requirements are suitable for demonstration purposes only. Please refer to the Deployment Guide for production-ready hardware requirements that vary based on the size of your dynaTrace deployment.

The system requirements and supported technologies are bound to the dynaTrace Server version. Although discontinued/unsupported technologies might work, they aren’t supported. dynaTrace features might not work, if not all components are on the same version.

dynaTrace Agent

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

dynaTrace Server

The dynaTrace Server is only supported on operating systems that support Java 7. Only the included JRE is supported.

  • Windows x86/x64 8.1/8/7/Vista or Server >= 2003 with latest service pack; installer (.msi) does NOT need a JRE; package contains a private 32bit / 64bit JRE 1.7 for runtime.
  • Linux x86/x64 with a recent kernel >= 2.6; installation requires a pre-installed JRE, v1.6 or higher; package contains a private 32bit / 64bit JRE 1.7 for runtime.
  • LDAP for dynaTrace user authentication.
    • Active Directory
    • openLDAP

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

    Deployment SizeRecommended Disk SpaceRequired
    Memory for dynaTrace Server  
    Recommended
    Memory for machine (dT Server& OS)1
    Physical
    Cores2
    Minimum #
    dynaTrace Collectors3
    Demo
    5 Agents | 1 Client | 75 Transactions/sec
    1.5GB + 100GB Continuous Session Storage/day
    1.5GB2GB20
    Small
    10 Agents | 3 Clients | 150 Transactions/sec 
    3GB + 200GB continuous Session Storage/day
     
    3GB3.5GB41
    Medium
    100 Agents | 5 Clients | 1000 Transactions/sec  
    5GB + 1TB  Continuous Session Storage/day 6GB7GB81
    Large
    600 Agents | 10 Clients | 2,500 Transactions/sec      
    10GB +  2TB  Continuous Session Storage/day   12GB15GB166
    XLarge
    1200 Agents | 20 Clients | 3,200 Transactions/sec  
    20GB + >2TB  Continuous Session Storage/day 22GB30GB2412

    1) R equired memory for the dynaTrace Server and Operating System. If there are other processes running, then additional heap is required.
    2) No virtual cores (Hyper-Threading).

    3) These numbers are only valid for Java and Collectors with 2GB heap and 2 cores. For .NET the numbers are doubled (e.g. 600 Agents, 12 Collectors for .NET), also for Collectors with 2GB heap and 2 cores.


dynaTrace Collector

The dynaTrace Collector is only supported by operating systems that support Java 7.

  • Windows x86/x64 8.1/8/7/Vista or Server >= 2003 with latest service pack
  • Linux x86/x64 with a recent kernel >= 2.6
  • Solaris SPARC or x86/64 10.8+
  • AIX Power 6.1.5+ 
  • zOS z/Linux SLES 8 SP4
  • HP-UX IA64
  • Oracle (Sun) JVM 1.7+, IBM JVM 1.7+, HP JVM 1.7+
    Hardware Requirements
    See the Deployment Guide for detailed hardware recommendations specific to your load. 

     

dynaTrace Client

  • Windows: Windows 8.1/8/7/Vista/XP or Server >= 2003 with latest service pack (certified)
    Linux: SUSE/RedHat Linux with GTK (certified); other flavors with GTK supported
    Mac: OS X 10.6+ 64bit (supported)
  • 100MB disk space
  • 1GB memory
  • Minimum screen resolution: 1024x768px
  • JRE 1.7 required

dynaTrace Performance Warehouse

Long-term historical data is stored in the dynaTrace Performance Warehouse. The Performance Warehouse uses a relational database to store data. Out of the box, dynaTrace uses an embedded database for demo/testing purposes. Any production installation of dynaTrace must use one of the following database management systems with the specified minimum version (or greater) to host the Performance Warehouse database:

*) Support for partitioned tables used in high-load scenarios.

To determine disk-space requirements for the dynaTrace repository upfront, factor 15GB per 1,000 persistent measures (of all system profiles within the dynaTrace repository). You can find more details in the Deployment Guide.

dynaTrace zRemote Agent

The dynaTrace zRemote Agent is now fully supported for the following OS:

  • Windows x64 2008 R2 / 2012 R2
  • Linux x64

 Supported Java Virtual Machines1

OS

Architecture

Oracle (Sun) JVM
8.02, 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.23 32/64bit

HP JVM
6.0, 5.0, 1.4.23 32/64bit

SAP JVM
6.0 64bit
Fujitsu JVM
5.0, 1.4.2  32bit
Hitachi JVM
5.0 32bit

Windows

x86/x64

(tick)

(tick)

(tick)

-

(tick)

(tick)

(tick)

Linux

x86/x64

(tick)

(tick)

(tick)

-

(tick)

--
LinuxPPC 32/64-(tick)-----

Solaris 10+

SPARC 32/64

(tick)

-

(tick)

-

---

Solaris 10+

x86/x64

(tick)

-

(tick)

-

---

AIX 5.2, 6.1, 7.1

PPC 32/64

-

(tick)

-

-

---

HP-UX

IA64

-

-

-

(tick)

---

z/Linux

z/Architecture

-

(tick)

-

-

---

zOS

z/Architecture

-

(tick)

-

-

---

1) only bytecode created by the Java Programming Language Compilers ( javac ) from supported JVM vendors
2) c lasses using lambda expressions can't be instrumented, but they can be monitored through Auto Sensors
3) 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, 8, 8.5

IBM HTTP Server (IHS) 6, 7, 8, 8.5

Oracle Http Server 103, 11, 12

Nginx 1.4.7+iPlanet 7

Windows

x86/x64

(tick)

(tick) 2

(tick)

(tick)

--

Linux

x86/x64

(tick) 1

-

(tick)

(tick)

(tick) 4 (tick)

Solaris 10+

SPARC 32/64

(tick)

-

(tick)

(tick)

--

AIX 5.2, 6.1, 7.1

P32/P64

(tick)

-

(tick)

(tick)

--

1) includes support for PHP 5.2 (Linux only), 5.3, 5.4 and 5.5
2) IIS 6: The option "split large signals for IIS 6" for the dynaTraceMonitor signal must be enabled in User Experience Settings. Web server metrics are not available for IIS 6.
3) Underlying Apache must be version 2 or later.
4) The Nginx Agent is only available for Nginx 1.4.7 or later and Linux builds where the debug symbols are available.. Please refer to the download pages for details.

 Supported PHP Versions

OS

Architecture

PHP 5.2

PHP 5.3

PHP 5.4

PHP 5.5

Windows

x86/x64

-

(tick) 1

(tick) 1

(tick) 1

Linux

x86/x64

(tick) 2

(tick) 2

(tick) 2

(tick) 2

Solaris 10+

SPARC 32/64

-

-

-

-

AIX 5.2, 6.1, 7.1

P32/P64

-

-

-

-

1Apache Web Server 2.0, 2.2 and 2.4 and IIS 6 - 8.5

2) Apache Web Server 2.0, 2.2 and 2.4 and Nginx 1.4.7+

Supported Application Environments and Technologies

Servlet Containers & Application Servers

Databases, Connection Pools, and BigData Solutions

Operating Systems (Platforms)

Servlet Containers:
C Apache Tomcat 5/6/7
C Jetty 6/7/8/9

J2EE (>=1.4) Compliant App Servers:
C IBM WebSphere 6.1/7/8/8.5 1
C Oracle WebLogic 9/9.1/9.2/10/11g/12
C Oracle Application Server 9i, 10g   
C JBoss AS CE 5.0.1/6.0.0/7.1.12
S JBoss AS EAP 62
C SAP NetWeaver 7.3 AS Java
C Sun Java Application Server 9.1
C Fujitsu Interstage 8/9 
C Cosminexus 8
C Glassfish 3.1 Open Source
S Virgo/SpringSource dm Server 2.x


Others:
C WebMethods 8.2
C Sun Java Web Server 6.1
C Microsoft IIS/ASP.NET 6/7/7.5/8  
C Microsoft SharePoint
S MS COM+ Component Services for .NET
S Adobe LiveCycle
L other/proprietary Java/.NET Servers

1 ) IBM JVM 7.0 only on Windows & Linux
2)  not all JMX measures available

Databases:
C IBM DB2 8/9 1
C Oracle DB 9i/10g/11g 1
C MS SQL Server 2000/2003/2005/2008/2012  1
C PostgreSQL 1
C Derby 1
C ADO.NET data providers (e.g. ODP.NET)
L generic support is available for any Type4 JDBC driver


Connection Pools:
C WebSphere Connection Pool 6.1 - 8.5
C WebLogic Connection Pool 9-12.1
C JBoss Connection Pool 5.x-8.0 
C Apache DBCP 1.0-1.4
C Tomcat Connection Pool 1.0.6 - 1.1.0
C c3p0 0.8.5 - 0.9.5.0
C GlassFish 3.x-4.x
L generic support is available for all J2EE connection pools

NoSQL & BigData Solutions:
C Cassandra 1.0.x, 1.1.x, 1.2.x 2
C MongoDB 2.0.x, 2.2.x, 2.4.x 3
C HBase 0.90.6, 0.92.1, 0.94.6, 0.96.0
C Hadoop 0.2,1.x, 2.x 4

1 ) JDBC Type4 drivers only
2) Java Thrift based Clients (Hector 1.0/1.1, Astyanax 1.x) and
Datastax 1.0.2 for Cassandra 1.2.x
3) Java drivers only, v. 2.3 - 2.11.4
4) Tested with CDH3, CDH4, HDP 1.1, EMR, MapR M5...

C Windows 8.1/8/7/Vista/XP
C Windows 2003/20081/2012 Server
L Windows 2008 R2 Server >  64 logical processors

C Suse Linux 8+
C RedHat Linux 4+

C AIX 5.2/6.1/7.1 

C Solaris SPARC 10+
C Solaris 10+ x86/x64

C IBM zOS 1.12/1.13/2.1

C z/Linux SLES 8 SP4

C HP-UX IA64

 

1) Only for Windows Server 2008 R2 with <= 64 logical processors

ESBs and SOA

Remoting

Messaging

C IBM WebSphere Message Broker 71/82
C IBM Integration Bus 92
C Oracle Service Bus 10.3.4
C JBoss ESB 4.12
C WSO2 4.63
C Mule 1.x / 2.x / 3.x  
C  TIBCO ActiveMatrix BusinessWorks Service Engine 5.8.2 4  

S Oracle SOA Suite
S Apache OpenEJB
S Fuse ESB

L SOA Software Service Manager 5.2/6.1

1 ) on Windows & Linux 64bit
2) on AIX, Windows & Linux 64bit
3) HTTP communication only
4) Wired and unwired mode via Tibco Spline Messaging  

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 1.1
C IBM WebSphere MQ 6, 7
C Apache Active MQ 4.x / 5.x  
C Microsoft MQ 3.0
C TIBCO EMS1 
C TIBCO Rendezvous 8.3.2 - 8.4.3

 1) Only for JMS 1.1
place JMS sensor on sender and receiver
no agent needed on TIBCO EMS itself

Web Service Stacks

Frameworks

AJAX Frameworks for UEM

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 CXF 2.2/2.3/2.4/2.5/2.6
C Apache Wink 1.2.0
C Restlet 2.1.0
C RestEasy 2.3.5 - 3.0.6
C Jersey 1.15/2.x
C Spring Web Services 2.0
S WebMethods Glue

S Hibernate
S Struts 1.x/2.x
S AWT/Swing/RCP/WPF/WinForms
S Spring
S Applets

HTTP Frameworks

C JDK Http API
C Apache HttpClient 3.1/4.x
C Apache HttpAsyncClient 4.0.1
C Jetty Http Client 6/7/8/9
C NING Http Client 1.6.x / 1.7x / 2.x

 

UEM is compatible with all JavaScript frameworks, automatic click detection is available for: 
S dojo: 1.6.1 – 1.9.31
S extjs: 3.4.0 – 4.2.11
S icefaces: 2 & 31
S jquery: 1.3.2 – 1.10.1 & 2.0.21
S prototype: 1.6.0 – 1.71
S angular: 1.0 – 1.2.51
S mootools: 1.4.51

The following frameworks are covered with the basic XHR detection:
S GWT
S zk
S RichFaces
S ASP.net AJAX
S YUI

The following frameworks are covered with the jquery sensor:
S backbone.js

1) Other versions of these frameworks still will work, but certain measures might be missing. The Javascript ADK can be used to capture the missing data.

Browser Support for UEM

Browser Diagnostics (with plugin)

OS for Mobile ADK

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+

CORS Support:
S Safari 4+
S Internet Explorer 8+
S Firefox 3.5+
S Chrome 10+

S Firefox 17-28
S Internet Explorer 8/9/10/11

C Apple iOS 6+
C Google Android 2.3+

Hybrid App Frameworks
S PhoneGap
S Apache Cordova
S Custom WebViews 
S KonyOne on Android

Mainframe Environments

C IBM zOS 1.12/1.13/2.1
C IBM WebSphere MQ 7.0/7.1
C IBM DB2 v9/v10/v11  

C IBM CICS Transaction Server 3.2/4.1/4.2/5.1/5.2  
C IBM CICS Transaction Gateway1 7.22/8.0/8.1/9.0
C IBM CICS SOAP over HTTP

C IBM IMS 3 11, 12, 13
C IBM IMS  MQ Bridge4
C IBM IMS Soap Gateway  
C IBM IMS Connect API (Java) 4 2.1/2.2/3.1
 
 

1) CTG for zOS: EXCI and IPIC
CTG for Multiplatforms: IPIC
(no support for TCPIP or SNA)
2)  EXCI: PTF level UK56730 required
3)  MSC and shared queues support is limited to the same LPAR
4) Inbound only 

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

Supported Browsers for WebStart

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 JRE >= 1.7.0_25 32-bit or JRE >= 1.7.u51 64-bit .

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.5 & 5.6) as well as the last minor version of the previous major version (currently 5.6). 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. If you have any questions, our Enablement Services Team can assist you to ensure a smooth and predictable upgrade to a new version of dynaTrace.

Support Level Overview

dynaTrace
version

On-demand
support

Projected
end of life

6(plus)October 31,2015
5.6(plus)Summer 2016
5.5(plus)Fall 2014

5

(minus)

 

4.2

(minus)

 

4.1

(minus)

 

4

(minus)

 

3.x.x 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 6 release discontinues support for the following platforms and components:

  • dynaTrace Server on Solaris and AIX
  • dynaTrace Server & Collector on Windows XP
  • dynaTrace Viewer (use dynaTrace Client instead)
  • All dynaTrace components below version Solaris 10
  • System profiles from dynaTrace versions < 4.2
  • Apple iOS  5

With the next dynaTrace 6.x release, support for the following platforms will be discontinued:

  • All dynaTrace components running on Microsoft Windows XP
  • Multiple dynaTrace Server instances on one system
  • iPlanet 7 (due technical blockers, we were forced to discontinue support)

With the fall 2016 release of Dynatrace, support for the following platforms will be discontinued:

  • Java Virtual Machine 1.4.2, all JVM vendors
  • dynaTrace Client 32bit
  • dynaTrace Server 32bit

 

  1. Anonymous (login to see details)

    Are there any plans to support Sun Java Web Server 7.0 in dynaTrace 6.0?

  2. Anonymous (login to see details)

    Is dt 6.0 Server supported on Solaris 10/Spark/64bit?

    1. Anonymous (login to see details)

      It is not.

      From the text right above:
      "The dynaTrace 6 release discontinues support for the following platforms and components:

      • dynaTrace Server on Solaris and AIX"

      Best, Roman

  3. Anonymous (login to see details)

    Any plans to provide support for Oracle 12c in Databases and Connection Pools?  Oracle 11g will no longer be supported by Oracle at the end of the year.

    1. Anonymous (login to see details)

      Support is not Database specific, but JDBC driver specific. So if the JDBC does not change, it is supported.