Skip to end of metadata
Go to start of metadata

January 15th 2014

Compuware is proud to present Compuware APM Application Monitoring and User Experience Management 5.6 powered by dynaTrace. 

 

1. Enterprise Grade UEM for Your Mobile Offerings

There are different ways for your users to interact with your system. Besides using traditional web applications on their desktops, they may also use mobile apps or mobile web sites on one or more mobile devices. dynaTrace provides a single user experience management solution for all these scenarios, helping you to meet your end users' expectations.

An Industry First: Hybrid Mobile App Support

Many vendors rely on hybrid app frameworks like PhoneGap to build a single HTML5 and JavaScript based mobile app that runs on multiple platforms and leverages all device capabilities. The drawback to this approach is obvious: Web technologies bring additional risk of performance problems, making user experience management even more important.

The Mobile App ADK provides an easy-to-use JavaScript interface for monitoring user actions within the WebView control. All web requests are tagged automatically. Moreover, the Mobile App ADK is now fully integrated with the JavaScript agent , so page actions that occur within a WebView are now merged with other mobile actions into the mobile visit.

Mobile App Monitoring Without Code Changes

Auto-Instrumentation for Android (soon also available for iOS) offers an easy means of injecting the Mobile App ADK into your existing apps. It reduces the complexity of manual instrumentation by automatically adding the instrumentation for lifecycle actions and network request tagging. It even gives you the power to instrument apps that were created by 3rd party vendors without touching the source code. If you develop your app in-house, that’s even better: auto-Instrumentation fits perfectly into your application lifecycle.

Get to the Root Cause of Crashes and Errors

Crash reporting is not enough. Every developer knows that there are many conditions that may not crash an app yet still pose problems. The Mobile App ADK lets you capture exceptions and errors that may indicate that something is going wrong, regardless of whether or not your app handles them without crashing.

When it comes down to analyzing crashes and errors, dynaTrace tells you exactly what the user did in the moments leading up to the error. Would you like to know if those users that experience crashes are on jailbroken or rooted devices? The Mobile App ADK captures this information along with a rich set of other attributes like application version and screen orientation.

Crash reports on iOS are most valuable when they are properly symbolicated. The iOS ADK now supports on-device-symbolication and even integrates with other crash reporting tools like HockeyApp.


Understand Network and Server Impact on Mobile Applications

Ever wonder where latency originates from when a user waits for a mobile action to complete? The Mobile App ADK measures the time spent waiting for network requests from the application side, while the web server agent measures the same request from the server side, helping you to understand the impact that network and server side performance has on your user experience.

The breakdown of client, network, and server wait times for web applications has also been improved to be consistent with the new visualization for mobile applications, assuring that you have comparable metrics across web and mobile users

2. UEM for the Web: Easier and Optimized 

Improved Out-of-the-Box Experience

dynaTrace 5.6 comes with pre-configured business transactions that let you monitor the response times of your user actions. Timings are divided intuitively by client type and action name. The UEM configuration dialogs have also been reworked to make setup easier. Also, if for some reason you cannot install a web server agent, the manual injection wizard will help you configure the JavaScript agent to your needs and add it to your web application.

Ensure That Your CDN Does What You're Paying Them to Do

dynaTrace lets you distinguish between 3rd party requests and requests that were sent to your content delivery network, providing you with the insight you need to confirm that your CDN investment is making a difference. Simply configure the domains of your CDN to automatically identify any problems.

Improved JavaScript Agent Uses Less Overhead and Bandwidth

The size of the JavaScript Agent has been reduced by 30% compared to the previous release, which will help you save bandwidth. Also, an overhead reduction of up to 70% for complex pages with a high number of DOM elements ensures that the JavaScript Agent won't impact user experience, even with extremely complex pages. 

An often requested improvement is the sending of captured data within the POST BODY of the dynaTraceMonitor signal. This feature is now enabled by default, but it can be disabled if necessary, for example for IIS 6 web servers.

The Best of Both Worlds: Leverage dynaTrace UEM with DC-RUM

With the new UEM integration of dynaTrace and DC-RUM, you can now enrich the passive network-protocol analysis-based information provided by  DC-RUM with the agent-based information collected by dynaTrace. dynaTrace UEM data is integrated into the DC-RUM Central Analysis Server and user actions are  assigned to the business hierarchy. This provides another monitoring perspective that supplements DC-RUM with:

  • CDN and third-party content impact on performance
  • Web 2.0 (XHR calls), AJAX readiness
  • Visit recognition
  • W3C navigation timing metrics
  • Perceived Render Time

 

3. Pinpoint Bottlenecks in Big Data Environments

With the newest release of dynaTrace we further expand the insight and ease of analyzing your Hadoop deployments. New with the latest release is a Hadoop-focused dashboard that displays the core information of any Hadoop cluster: Jobs and Tasks. It delivers a quick overview of the performance of different jobs in relation to users running jobs and the time it takes to complete jobs.
As such it’s a great starting point for getting to the root cause of performance issues. With this release we've made it even easier to drill down to hotspots or, when necessary, to the method level to detect the root cause of slow or failing jobs. Basically we allow you to slice and dice your Hadoop cluster anyway you want, be it job distribution, cluster utilization, HDFS behavior, or any other Hadoop related metric.

Visualize Tasks and Users in Real-time

Just monitoring Hadoop processes and daemons is not enough. With direct correlation of map and reduce tasks and their related JVMs to the users, pools, queues, and jobs driving those JVMs, we allow you to directly analyze who and what is utilizing your cluster resources, empowering you to manage consumption and even build charge-back models for your Hadoop environment.  

Ensure Optimum HDFS Locality

Two of the major advantages of Hadoop and HDFS are that the data that needs to be processed is stored closely to where processing occurs and that HDFS breaks large data sets down into small pieces and distributes them across your cluster. This is great, but how can you ensure that the distribution is optimal? How can you identify the pieces that failed and had to be reprocessed? More importantly, what was the impact of those failures on the entire map reduce process? With the newest version of dynaTrace, you get all this information and more with our new HDFS dashboard.

 

Extended Big Data and NoSQL Technology Support

We have once again increased our support for various Big Data technologies; this includes support for the newest Datastax CQL3 Java Driver for Cassandra and Apache Commons Daemon support for Cassandra.

Additionally, we've added an all new Sensor for HBase, guaranteeing full product integration, and we updated our Mongo DB support to include the latest versions of this popular NoSQL database. 

4. Improved Visibility Into Your PHP Applications 

The PHP agent now comes with an extended number of sensors, enabling you to capture database calls to various databases and capture Zend framework log messages. It is now possible to capture PHP session variables. There is also a new PHP exception sensor that makes use of your PHP application's powerful error rules. Other functional improvements include tracing calls that are made via call_user_func and call_user_func_array and the tagging of PHP remote calls. If you want to chart the long-term trends of your PHP compilation, you can now use the new PHP compilation time measure.

Fully Leverage Business Transactions With Session Variable Capturing

To understand what happens inside your PHP applications, you need to capture domain specific data like the number of articles in or the value of a user's shopping cart. This is now possible by capturing session variables in the PHP server sensor. Combined with the powerful concept of business transactions, you can now see how performance and user satisfaction impact your business success.

Improved Visibility into DB, WordPress, and PHP 5.5

Although MySQL is the most commonly used database with PHP applications, there are also drivers for other databases. New database sensors for native Oracle and PostgreSQL database drivers have been added and a PDO sensor pack now brings full visibility into PDO accessed databases, including MySQL, PostgreSQL, SQLite, Firebird, Informix, Oracle, ODBC, FreeTDS, Sybase, Microsoft SQL Server, SQL Azure, IBM DB2, CUBRID, 4D SQL, Cassandra, and more.

In addition, if you are running WordPress, you can start with our out-of-the-box WordPress sensor to get metrics for the most important WordPress methods and functions. PHP 5.5 was released over the summer and is fully supported with this release. 

  

5. Easier Rollout and Safer Administration 

Faster Time to Value

For first-time users, those who want to set up a new environment as quickly as possible, and also for occasional dynaTrace users, we have improved workflows beginning with the installation process and extending all the way through to deeper diagnostics. With Compuware APM you proceed quickly and easily from product installation to application performance monitoring of the details of your application.

Intuitive Navigation

Based on customer feedback we have improved the navigation for our out-of-the-box dashboards and dashlets. These changes have resulted in significant productivity and ease of use enhancements. 

On Demand Activation and Rollback for Critical FixPacks

FixPacks are now listed separately from Plugins, and we provide a full history of all installed FixPacks. Based on this history you can Activate/Deactivate any FixPack on the dynaTrace Server. It is also now possible to install a FixPack while postponing the FixPack's activation until later (for example, in situations when restart of affected dynaTrace components is only possible from a certain maintenance window). FixPack handling has never been easier!

6. PurePath for zOS

Leverage Compuware Abend-AID Fault Management for Efficient  CICS Exception Analysis 

The dynaTace CICS Agent automatically detects abends (abnormal ends) for all your CICS programs. Abends are captured and reported within PurePaths as exceptions. The new integration of dynaTrace and Compuware Abend-AID makes it easy to drill down into the Abend-AID Report of any particular exception (abend) for detailed code-level analysis. This eliminates the time-consuming and manual effort of cross-referencing PurePath CICS exceptions with corresponding abends on the mainframe. Abend-AID is Compuware's industry leading mainframe application failure resolution solution.  

 

Save MIPS on Your Mainframe

In this release, the footprint of dynaTrace on zOS has been significantly reduced. This was achieved with a fundamental re-tuning and re-architecting of the data collection model for the zOS Agents. The zOS Unix Agent (previously zDC USS Agent), which still resides on zOS, can now be extended using the optional dynaTrace z Remote Agent  which is hosted in distributed environments including Windows, Linux, AIX and z/Linux to reduce expensive data processing on zOS. It's still possible to configure the zOS Unix Agent to process all data on zOS and communicate directly to the dynaTrace Collector. In this scenario the dynaTrace z Remote Agent isn’t required.

  

7. Leading Edge Technology Support

dynaTrace 5.6 adds support for new technologies (for full details, see Supported Application Environments) including:


  • All dynaTrace components are now on Java 7 and support Windows 8 & 8.1
  • IBM WebSphere Message Broker 8 & 9 
  • WSO2 Enterprise Service Bus 4.6 using HTTP
  • JBoss Enterprise Service Bus 4.12
  • SAP NetWeaver 7.3 as Java running on SAP JVM 6.0
  • Cassandra Support for Datastax CQL3 Java Driver
  • JAX-RS via XCF 2.5.X, Jersy 2.X, RestEasy 3.X
  • JAX-WS async WebService calls for GlassFish 3.1, IBM WebSphere 8.5, WebLogic 12 and JBoss 7.1.1
  • PHP 5.5
  • Internet Information Server (IIS) 8.5

Implemented Requests From Our User Community

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

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 new ways. Here are the most important improvements:

dynaTrace is now on Java 7

Due the fact that Oracle won't deliver additional security updates for Java 6, all dynaTrace components are now optimized for Java 7. Since Java 7 utilizes different memory management, it is recommended that you increase the maximum available memory of the dynaTrace Server and Collector by about 20%. The maximum recommended memory settings for the dynaTrace Server have been increased to 14GB.

Test Automation - Parallel Test Execution

Using this unique id, the dynaTrace Server can now distinguish between parallel test executions. You no longer need to set test information across different agent groups.

Automated Memory Dumps and Incident Downtime

The dynaTrace Server offers several REST interfaces for managing memory dumps (for example, create, get, delete, post process of status of memory dumps).

Incident downtime can now also be fully managed via the dynaTrace Server REST interface including functionality like list, add, update, or delete incident downtime. 

Database Connection Aggregation

By turning on "Statement Aggregation" in the JDBC/ADO.NET sensor properties, PurePaths now not only contain aggregated summaries of database statements, but also aggregated summaries of database connection acquisitions (such as Java getConnection()). This significantly reduces the communication between Agents and Server and the overall length of PurePaths, thus providing an overhead reduction for these sensors. We highly recommend that you turn this setting on for production environments or if you have long PurePaths due to database statements. For newly created system profiles this setting is turned on by default.

Ensure Maximum File Handles Setting on Linux

To prevent stability issues on certain Linux systems, the dynaTrace Server now validates that the maximum number of open files is set to at least 2048. If necessary, adjust this setting before upgrading to dynaTrace 5.6

Continuous Transaction Storage is Optimized for dynaTrace Server Throughput by Default

Continuous Transaction Storage in "Optimize for dynaTrace Server throughput" mode prevents the caching of transactional information in memory. This reduces garbage collections on the dynaTrace Server and increases throughput by up to 25%. This mode is now enabled by default.  DC-RUM integration doesn't support this mode. Please switch to "Optimize for user triggered transaction analysis" when using the DC-RUM integration.

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.

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

  • A recent addition to the plugin list is an extended SNMP Action Plugin that provides additional information in SNMP traps for integration with central incident management systems. The Plugin can be used alongside the already built-in SNMP Action Plugin and will likely replace this plugin in the future.
  • The Rabbit MQ Monitor Plugin provides several metrics for monitoring this messaging platform with dynaTrace.

License Changes

dynaTrace 5.6 licensing is compatible with previous releases. Therefore you don't need to upgrade your license when you migrate from dynaTrace 5.5 to 5.6.

However, migration from much earlier dynaTrace versions (version 5.0 or earlier) requires a license upgrade. 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. For details, please have a look at the license upgrade documentation. If you need help, our Licensing team will gladly support you in upgrading your existing license to a 5.6 license.

Please note: We recommend that you read the upgrade and migration documentation prior to migration to dynaTrace 5.6.

Resolved Issues

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

  • dynaTrace WebStart Client no longer starts after upgrading to Java 7 update 45

  • JDBC Statement Aggregation can cause an unexpected NullPointerException in the JDBC Sensor

 

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 by the product. This section provides links to more information regarding issues you may 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 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 and PPC; Solaris SPARC 32/64 and x86/x64; AIX 32/64 Power 5, 6 and 7 architectures; z/Linux 32/64; zOS 32/64 (no host health information available); HP-UX IA64
  • .jar installers suffice with a JRE 1.4
  • Oracle (Sun) JVM, IBM JVM, JRockit JVM, HP JVM
  • 10MB disk space

dynaTrace Server

The dynaTrace Server is only supported on operating system which support Java 7.

  • Windows 8.1/8/7/Vista/XP or Server >= 2003 with latest service pack (certified); 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 (certified); installation needs a pre-installed JRE 1.6 or later; package contains a private 32bit / 64bit JRE 1.7 for runtime
  • Solaris SPARC and x86/64; AIX Power 5, 6 and 7 (supported); packages do NOT contain a (Server-) private JRE 1.7 and require a pre-installed J2SE 7.0 / IBM JRE 1.7 or later respectively
    Solaris / AIX limited to medium environments with a maximum of 100 Agents and 500 requests per second

Other requirements:

  • Minimum 1.5 GB disk space (additional storage is required for continuous session recording)
  • Minimum 2 GB, typical 4-12 GB memory
  • LDAP for dynaTrace User Authentication
    • Active Directory
    • openLDAP

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

dynaTrace Collector

The dynaTrace Collector is only supported on operating system which support Java 7.

  • Windows 8.1/8/7/Vista/XP or Server >= 2003 with latest service pack (certified); installer (.msi) does NOT need a JRE; package contains a private 32bit / 64bit JRE 1.7 for runtime
  • Linux x86/x64 with a kernel >= 2.6; z/Linux; zOS; HP-UX IA64 (certified); installation needs a pre-installed JRE 1.6 or later; package contains a private 32bit / 64bit JRE 1.7 for runtime
  • Solaris SPARC and x86/64; AIX Power >= 6.1.5 (supported); packages do NOT contain a (Collector-) private JRE 1.7 and require a pre-installed J2SE 7.0 / IBM JRE 1.7 or later respctively

Other requirements:

  • min. 1GB disk space
  • min. 128MB, typical 1-2GB memory

See the Deployment Guide for more specific hardware recommendations.

dynaTrace Client

The dynaTrace Client is only supported on operating system which support Java 7.

  • Windows 8.1/8/7/Vista/XP or Server >= 2003 with latest service pack (certified); installer (.msi) does NOT need a JRE; package contains a private 32bit / 64bit JRE 1.7 for runtime
    Linux: 32 bit SUSE / Red Hat Linux with GTK (certified); no official support on 64 bit Linux (32 bit GTK2 runtime, libXtst-32,... required - see dynaTrace Forum); installation needs a pre-installed JRE 1.6 or later; contains a private 32bit / 64bit JRE 1.7 for runtime
  • Mac OS X 10.6+ 64bit (supported); installation does NOT need a JRE; requires a JRE 1.7 for runtime

Other requirements:

  • 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 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:

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, factor 15GB per 1000 persistent measures (of all System Profiles within the dynaTrace repository). You can find more details in the Deployment Guide.

dynaTrace z Remote Agent

The dynaTrace z Remote Agent is in an experimental phase in version 5.6. Please contact Support to determine if your environment can support a deployment!

  • Windows x64 2008 R2 / 2012 R2
  • z/Linux 64
  • Linux x64

 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

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)

  

Solaris 9+

SPARC 32/64

(tick)

 

(tick)

 

   

Solaris 10+

x86/x64

(tick)

 

(tick)

 

   

AIX 5.2, 6.1, 7.1

P32/P64

 

(tick)

 

 

   

HP-UX

IA64

 

 

 

(tick)

   

z/Linux

z32/z64

 

(tick)

 

 

   

zOS

z32/z64

 

(tick)

 

 

   

*) only bytecode created by the Java Programming Language Compilers ( javac ) from supported JVM vendors

**) 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

Oracle Http Server 10, 11

Windows

x86/x64

(tick)

(tick) 2

(tick)

(tick)

Linux

x86/x64

(tick) 1

 

(tick)

(tick)

Solaris 9+

SPARC 32/64

(tick)

 

(tick)

(tick)

AIX 5.2, 6.1, 7.1

P32/P64

(tick)

 

(tick)

(tick)

1) incl. support for PHP 5.2, 5.3, 5.4 and 5.5
2) IIS 6: "split large signals for IIS 6" for the dynaTraceMonitor signal must be enabled in the User Experience Settings. Web server metrics are not available for IIS 6. 

 Supported PHP Versions

OS

Architecture

PHP 5.2

PHP 5.3

PHP 5.4

PHP 5.5

Windows

x86/x64

 

 

 

 

Linux

x86/x64

(tick) *

(tick) *

(tick)  *

(tick)  *

Solaris 9+

SPARC 32/64

 

 

 

 

AIX 5.2, 6.1, 7.1

P32/P64

 

 

 

 

*) Apache Web Server 2.0, 2.2 and 2.4

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 Compliant App Servers:
C IBM WebSphere AS 6.1/7/8/8.5*
C Oracle WebLogic AS 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.1**
S JBoss AS EAP 6**
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

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

Databases:
C IBM DB2 1 8/9
C Oracle DB 1,2 9i/10g/11g
C MS SQL Server 1,2 2000/2003/2005/2008/2012
C PostgreSQL 1
C Derby 1
L generic support is available for 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-7.x
C Apache DBCP 1.0-1.4
C Tomcat Connection Pool 1.0.6+
C c3p0 0.8.5+
L generic support is available for all J2EE connection pools

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

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

C Windows 8.1/8/7/Vista/XP
C Windows 2003/2008/2012 Server
C Suse Linux 8+
C Red Hat Linux 4+
C AIX 5.2/6.1/7.1 
C Solaris SPARC 9+
C Solaris 10+ x86/x64
C IBM zOS 390
C z/Linux SLES 8 SP4
C HP-UX IA64

ESBs and SOA

Remoting

Messaging

C IBM WebSphere Message Broker 7*/8**
C IBM Integration Bus 9**
C Oracle Service Bus 10.3.4
C JBoss ESB 4.12
C WSO2 4.6***
C Mule 1.x / 2.x / 3.x  

 S Oracle SOA Suite
S Apache OpenEJB
S Fuse ESB 

 L SOA Software Service Manager 5.2/6.1  



*) on Windows & Linux 64bit
**) on AIX, Windows &  Linux 64bit
***) HTTP communication only 

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

S TIBCO Rendezvous 8.4

L TIBCO ActiveMatrix BusinessWorks Service Engine 5.8.2*






*) Wired mode via Tibco Spline Messaging only

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/2.7
C Apache Wink 1.2.0
C Restlet 2.1.0
C RestEasy 2.3.5
C Jersey 1.15/2.0
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.0/4.1/4.2
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 jQuery
S Dojo
S ICEfaces
S extJS
S ZK

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+

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

C Apple iOS 6+
C Google Android 2.3+

Hybrid App Frameworks

S PhoneGap
S Apache Cordova
S Custom WebViews 

Mainframe Environments

C IBM zOS 1.12/1.13/2.1
C IBM CICS Transaction Server 3.2/4.1/4.2/5.1    
C IBM WebSphere MQ 7.0/7.1  
C IBM DB2 v9/v10/v11
C IBM CICS Transaction Gateway* 7.2**/8.0/8.1/9.0
C IBM CICS SOAP over HTTP

*) CTG for zOS: EXCI and IPIC
CTG for Multiplatforms: IPIC
(no support for TCPIP or SNA) 

**)  EXCI: PTF level UK56730 required

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 32-bit JRE 1.7.0_25 or higher.

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 & 5.5) 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. 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

5.5(plus) 

5

(plus)

 Spring 2014

4.2

(plus)

 Spring 2014

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 5.6 release discontinues support for the following platforms:

  • HP UX on PA-RISC
  • dynaTrace Collector/Server, because no Java 7 is available on these platforms
    • AIX < 6.1.5 (no Java 7 available)
    • Solaris < 10.8 (no Java 7 available)
    • Red Hat Enterprise Linux < 5.5 (no Java 7 available)
    • Suse Linux Enterprise Server < 10 SP2
  • Application Server
    • IBM WebSphere Application Server < 6.1
    • Oracle WebLogic 8.1 (SP3+)
    • JBoss 4
    • Oracle Application Server 6.5
    • Borland Enterprise Server 6.5 
    • Borland Application Server 6.7
    • Sun Java Application Server < 9.1

With the next release, dynaTrace will discontinue support for the following platforms:

  • dynaTrace Server on Solaris and AIX
  • dynaTrace Server 32bit


  • No labels
  1. Anonymous (login to see details)

    Is support for The Browser Agent up to IE 11 and FF 25 in this release? If so, these release notes need to be updated.

  2. Anonymous (login to see details)

    IE11 and FF25 are not included in this release. We have experienced some stability problems that need to be addressed before providing support for these browsers.

  3. Anonymous (login to see details)

    To clarify my request, I do see that Windows>=2003 is supported but I need verification that dT has been installed and tested in a Windows 2012 environment.

    1. Anonymous (login to see details)

      Gavin, Windows Server 2012 is supported & tested!