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.
dynaTrace 5 Highlights:
dynaTrace 5 also includes:
Additional Information and Software and Hardware Requirements
Migrate to dynaTrace 5 Today
up to 5 times faster Client response time
150+ quality improvements!
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.
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.
- 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.
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.
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.
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.
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
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.
- KB-327 Issues with certain JVM versions, options and parameters
- KB-365 PerfMon metrics are not visible
- KB-355 Older Websphere versions crash with OutOfMemory error
- KB-324 System.String objects do not show up in Selective Memory Dumps
- KB-314 Custom JMX metrics show double their real value on WebLogic
- KB-274 Cross AppDomain Remoting calls within one CLR will lead to incomplete PurePath
- KB-434 Exception when JMX sensor enabled with WebLogic 10
- KB-445 Agent crashes on HP-UX
- KB-447 Firefox agent doesn't capture rendering events when certain plugins are active
- KB-448 Network Sensor of the IE Agent not working when certain plugins are active
- KB-450 Static primitive values not captured with memory dumps on Sun JVM 7
- KB-451 dynaTrace Client UEM WorldMap may be slow on Linux
- KB-453 Web Server Agent may cause coredump on AIX
- KB-461 Limitation of placing AutoSensor based PurePath nodes
- KB-470 Java Web Requests Sensor is causing java.lang.IllegalStateException lines in the agent log
- KB-471 Disk space measures are off by a system-dependent factor on Solaris
- KB-473 Apache web server does not start after adding dynaTrace agent on AIX PPC32
- KB-475 Auto adjustment of server memory leads to incorrect settings
[KB-479 No UEM volume available after installing volume key
Software and Hardware Requirements
- 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
- 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.
- 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.
- 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:
- Oracle 10g/11g
- Microsoft SQL Server 2008/2012
- SQL Azure (see Windows Azure Best Practices [DEPRECATED])
- IBM DB2 Version 9.7, 10
- PostgreSQL 9.1, 9.2
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
Oracle (Sun) JVM
AIX 5.2, 6.1
*) these 64bit 1.4.2 JVMs are not supported by dynaTrace
Supported .NET Platforms*
n.a. = not applicable
*) .NET is not supported on the Itanium architecture
Supported Web Servers for UEM
Apache Web Server
IBM HTTP Server (IHS) 6, 7
Oracle Http Server 10, 11
AIX 5.2, 6.1
Supported Application Environments and Technologies
Databases, Connection Pools and BigData Solutions
Operating Systems (Platforms)
C IBM WebSphere 5.1/6/6.1/7/8/8.5
C Windows 7/Vista/XP
ESBs and SOA
C IBM WebSphere Message Broker 7 *
C RMI / IIOP
Web Service Stacks
LDAP (for User Authentication)
C IBM WebSphere 5.1/6/6.1/7/8
S Active Directory
AJAX Frameworks for UEM
Browser Support for UEM
Browser Diagnostics (with plugin)
S Firefox 3.6, 4-16
OS for Mobile ADK
C IBM z/OS 1.12, 1.13
C Apple iOS 4.2+
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
3.1 and earlier
*) 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