Data Center Real User Monitoring 12.1.3 Release Notes

Application-Aware Network Monitoring and User Experience Management Data Center Real User Monitoring 12.1.3 Release Notes Highlights of DCRUM 12.1.3 Highlights of DCRUM 12.1.2 Localized Reporting and Documentation ICA Analyzer Enhancement Application Tier Definition Using Client IP Addresses HTTP Analyzer Enhancement Highlights of DCRUM 12.1.1 CAS Benchmark Tool Citrix Reporting Enhancements SMTP and LDAP Enhancements Highlights of DCRUM 12.1 Enhanced Information Delivery Mobile Application for Tablets and Smartphones Improved Reporting Ease of Use and Performance Synthetic Monitoring Data Integration with Gomez Synthetic Backbone Transactions Enhanced Presentation and Workflow for Synthetic Monitoring Unified Synthetic Monitoring and dynatrace DATM Troubleshooting Workflow Enhanced Analytics Automated Fault Domain Isolation Analytics Flexible Baseline and Baseline Corridors Application Intelligence Voice-Over-IP Support on the Agentless Monitoring Device New Analysis Modules - LDAP, CITRIX ICA Enhanced Analysis Modules - Oracle, SAP, Web, SQL DB, SSL Performance and Usability Improvements Zero-configuration Web Application Discovery

DCRUM Configuration Improvements Easier Use and Customization of BSM Improved BSM Portlet and Dashboard Functionality Compuware Security Server Also Included in This Release Additional Improvements and Changes Resolved Issues Known Issues Technical Notes Additional Information Service Pack Prerequisites Language Pack Installation Instructions Installation Requirements Customer Support Customer Support Information Reporting a Problem Obtaining the Latest Documentation 2

Highlights of DCRUM 12.1.3 DCRUM release 12.1.3 focused on resolving issues reported by customers. For more information, see Resolved Issues [p. 21]. Please review the Technical Notes section for additional information related to this release. For more information, see Technical Notes [p. 46]. Highlights of DCRUM 12.1.2 Localized Reporting and Documentation This DCRUM release (software and documentation) has been translated to Simplified Chinese, Japanese, and Korean. On the CAS, ADS, Enterprise Portal, and Compuware Security Server, you can set the language at logon. On the RUM Console, you can set the language after logon. As usual, all DCRUM analysis modules support international characters because of standard Unicode character set compatibility. For more information, see Language Pack Installation Instructions [p. 49]. To view localized online help, use the help icon on the individual reports. ICA Analyzer Enhancement The ICA (Citrix) analyzer has been enhanced in Release 12.1.2 to support WAN optimized environments. The ADCD metric can now be calculated more precisely for software services based on the ICA analyzer. This support is limited to Riverbed and Cisco WAAS optimizers. Application Tier Definition Using Client IP Addresses The RUM Console definition of the software service allows you to catalog and report traffic going to the same server IP and port by associating client group names with the originating client IP. On the report, the client group name is reported as a suffix to the software service name. For example, a software service named SQL configured on a server located at 10.1.1.10 can be configured the following way: 3

Client IP Address 10.1.1.1 10.1.1.2 Software Service name suffix _ATLANTA _BOSTON DCRUM will differentiate the SQL software service traffic going to the server based on the client IP definition and it will individually report data for software service SQL_ATLANTA and SQL_BOSTON individually. The default configuration that contains no client IP definitions results in an empty client group name. Similarly, an empty group name is used if a client IP is not included in any of the defined IP ranges. This configuration makes it possible to obtain only the client group name. The same client group name can be used in many client IP ranges. The configuration of each software service is individual through the client group name. No cross-relations or cross-checks are performed between the definitions. It is possible to use a different name for the same client IP in each of the software services. HTTP Analyzer Enhancement The HTTP analyzer has been enhanced in Release 12.1.2 to allow for searching in a binary POST body. By specifying any one of four parameters for a given URL definition in HTTP-based software service, you can create a regular expression to search the binary POST body in your HTTP traffic. To use this enhancement, select the Custom RegEx option for the Parameter match, and input your regular expression search pattern. Highlights of DCRUM 12.1.1 CAS Benchmark Tool The DCRUM Benchmark tool helps you estimate the speed of database server responses that would occur in a real Central Analysis Server (CAS) installation, if one was deployed on your system. 4

The CAS Benchmark Tool provides this information by measuring real database server responses on a database that would be similar in size and structure to a typical CAS database. Such performance information cannot be easily estimated based on readily available metrics such as CPU speed or memory size. This is because database performance depends to a large degree on the peripheral devices' access speed. The Benchmark tool does not replace the need for comprehensive capacity planning because it does not measure network traffic, detect traffic profiles, or help you determine what type of monitoring you require. For a discussion on these topics, refer to Data Center Real User Monitoring Capacity Planning and Performance Assessment User Guide. CAS Benchmark tool summary of features: CAS database speed assessment The tool assesses database response speed for a typical CAS deployment. Configuration flexibility The tool can operate on an existing database, including a CAS database, or it can create a new database. Required permissions The tool requires database administrator privileges to create a new database, but can be run on an existing database without database administrator credentials. Preserving existing database integrity and state The Benchmark tool does not alter any data that is has not created, and it automatically removes all of its own data at the end of each test. It also provides an option to remove the test database if one has been created. Two test options It provides two types of tests: quick and full. These tests take approximately two minutes and 15 minutes respectively when run on a benchmark system. Result evaluation The tool compares actual results with an benchmark result: performance is said to be higher if running time is shorter. 5

Citrix Reporting Enhancements The following Citrix landing page metric enhancements have been implemented: A login operation data is available for metric charts. The Total Bandwidth Usage metric can be displayed for Software Service, Server and Published Applications reports. The Total Bytes metric is available for Citrix Channels and Login Performance reports. The Citrix Servers, Published Applications and Channels tables display a new column group, Commands, which contains Commands breakdown and Command delivery time metrics. Additional enhancements include: A drilldown from the Published Applications report to the Citrix Servers report, which allows you to determine the systems that serve a particular application. A link from Citrix Sites report to All Users report. A network metric chart of total bandwidth usage that illustrates the interferences of the interactive screen, keyboard, and mouse traffic with non-interactive data transfers within an ICA protocol such as printing or audio streaming. A network metric chart of total bandwidth usage per published application that displays conflicting applications on the same server or site. 6

SMTP and LDAP Enhancements Both SMTP and LDAP analyzers now support encryption. Encrypted operations for these analyzers are labeled encrypted. Additionally, the LDAP analyzer now is capable of processing and reporting user names. Highlights of DCRUM 12.1 Enhanced Information Delivery Mobile Application for Tablets and Smartphones Building upon the new fault domain isolation workflow in the Enterprise Portal that was part of Release 12.0, Compuware is extending this industry leading capability to your smartphone and tablet. Operations managers and staff can now instantly access Application Health information on their ios or Android smartphones and tablets. With a couple of taps and a few swipes, you can quickly check the health of your mission-critical application in real time, isolate the fault domain of an application problem, and hand it off to the appropriate team to isolate the root cause. 7

Improved Reporting Ease of Use and Performance Continuing the efforts started in 12.0, Compuware continues to invest in a modern look and feel of the Central Analysis Server (CAS) reporting interface. One of the improvements introduced in 12.1 is the ability to use the new, dynamic charting library that can help make any Data Mining Interface (DMI) report look more attractive. The new library also improves dynamic interactions between the user and the information delivered. Notable functional changes to CAS reports include the ability to zoom in and out, and the ability to hide or display metrics on charts with one click on a chart legend. It is also easier to hide or display chosen columns on DMI tables. With two clicks, the new DMI quick column selector allows you to hide or show any metric previously included in the DMI report definition. In addition to the usability improvements, Release 12.1 architecture improvements decrease report generation times for even the most complex reports. The DMI now offers access to trending data, memory caches in server cluster setup, and single-user data. These improvements help with the performance of reports for historical days, farm-aggregated reporting, and user-list reports. Synthetic Monitoring Data Integration with Gomez Synthetic Backbone Transactions DCRUM provides measurements on the performance of an application for all vital data center tiers up to the web front-end interface. The integration of Gomez SaaS Synthetic backbone transactions with DCRUM data provides a comprehensive view of global web application performance. 8

Synthetic transactions, which are executed on backbone nodes worldwide, provide visibility into an application s availability and performance. This synthetic data allows you to identify global issues in off-peak hours when there is minimal real-user data. It also helps analyze the root cause of performance issues that are caused by factors which are outside of the data center, such as issues with third party content. The data can be analyzed on both the test and the page level. Data from multiple Gomez accounts can be integrated into a single CAS server. Enhanced Presentation and Workflow for Synthetic Monitoring Reports for Synthetic Monitoring data have a new and improved presentation and workflow to better meet the users' needs. You now have three ways to access and view the Synthetic Monitoring data. As with previous releases, the workflow can be accessed from the context of a specific application from any of the CAS application/tier reports, or the Application Health Status report. These application-centric views provide a consolidated End User Experience (EUE) view of DCRUM and Synthetic data for a complete view of the application's availability. In addition, a new Synthetic Monitoring Overview report has been added that gives an overall status of only the Synthetic Monitoring data. This view makes it easier to ensure that all synthetic transactions across multiple applications and sites are available and performing within agreed upon response times. 9

From any of these starting points, the troubleshooting workflow has been simplified to enable faster fault domain isolation and enable you to drill down to deep-dive server and network root-cause analysis with no more than three or four clicks of the mouse. Unified Synthetic Monitoring and dynatrace DATM Troubleshooting Workflow The Synthetic Monitoring integration with dynatrace Deep Application Transaction Management (DATM) enables you to use dynatrace DATM to precisely analyze response times and failure rates of web-based transactions, such as URL-based automated checks and Agent Recorder scripts that monitor applications running in an Internet Explorer or Firefox web browser. This provides for 24x7 monitoring coverage of your application and faster Mean Time To Respond (MTTR) for identification and root cause analysis of a problem identified by the Synthetic Monitoring data. Synthetic Monitoring's integration with dynatrace requires that both products integrate with an existing CAS to create a unified reporting workflow. After configuring the integration, you can drill down from integrated EUE reports in the CAS in the context of applications, sites, and transactions to view a custom dynatrace dashboard in which you can analyze PurePaths for a selected transaction. 10

Enhanced Analytics Automated Fault Domain Isolation Analytics Leveraging years of field experience with Automated Fault Domain Isolation (FDI), release 12.1 now takes you to the next level. With the goal of providing answers instead of data, DCRUM employs the Advanced Diagnostics Server (ADS) to analyze dozens of the most important metrics for every single operation load. This capability lets you conclusively determine the responsible fault domain. Compuware analyzed numerous cases to make sure the results are as accurate as possible for both web and non-web applications. Now the system, not the user, determines the meaning and usage of all of DCRUM's advanced metrics. In addition, it analyzes them for you with a precision and bandwidth that is not available to a human operator. 11

Flexible Baseline and Baseline Corridors On a nightly basis, the CAS updates its baselines on a rolling average (the default is nine-day rolling average). These baselines are used by hundreds of customers around the world for effective performance management. But for some users, baselines are needed that account for variations in traffic on different days of the week, random anomalies in traffic load, or the need for a known baseline from a specified point in time. In Release 12.1, new capabilities that make our baselines more effective are introduced. Reports now allow a baseline corridor to be defined and show up visually on time-series charts. This allows you to visually identify abnormal performance conditions in an easy way. In addition, new baseline types effectively handle day-of-the-week performance patterns (weekly baselines), and static patterns (pinned baselines and manually imported baselines). Application Intelligence Voice-Over-IP Support on the Agentless Monitoring Device Release 12.1 adds native support for VoIP within DCRUM. The inclusion of the VoIP analysis module on the AMD greatly simplifies the DCRUM deployment. Separate Network Vantage VoIP probes are no longer needed. The scalable AMD architecture provides an opportunity to consolidate multiple probes to save resources and operations cost. VoIP support is now implemented through AMD-based VoIP traffic analysis, RUM Console based configuration, and out-of-the-box reports in the CAS and ADS. 12

The AMD implementation provides a SIP and H.323 ready solution that supports all common VoIP audio codecs. The reports allow for fast FDI through analysis of many standard metrics (MOS, loss rate, jitter, delay, and more). Metrics can be retrieved from RTCP streams and measured directly from the traffic. FDI analysis correlates the VoIP data in the context of other network applications that run over the same links. This analysis identifies any issues related to Quality of Service (QoS), bandwidth utilization, or other causes that mutually impact each other. New Analysis Modules - LDAP, CITRIX ICA New Citrix ICA Analysis Module The performance of Citrix XenApp and Windows Terminal Services, as perceived by end users, depends on the quality and speed of the network between the display and the XenApp/XenDesktop server. A new DCRUM Citrix analysis module provides insight into this connection. With the new Citrix ICA analysis module, DCRUM individually monitors the performance of each network session between end users in remote locations and the data center where the Citrix servers reside. Deep-dive insight enables DCRUM to recognize Citrix users by the login name for both XenApp and XenDesktop, and stamp all network traffic with the user name. Reporting is provided on the performance of each user individually, identified by name for each published application. This identification lets you understand how end users consume Citrix resources, know what business activities are affected by performance issues, and correlate network performance to concrete Citrix users issues. 13

Individual performance monitoring of ICA virtual channels enables the distinction between ICA channels that carry interactive traffic (updates in response to user actions) and those that carry non-interactive traffic (such as USB, disk, and printing traffic). Now you can troubleshoot network quality issues from network abuse by unwanted background traffic. You can also use the ICA analysis module to monitor complex environments with XenDesktop and XenApp in the presence of load balancers, proxies, and NAT devices that can break TCP sessions between the client and server and conceal the real end user identity. New LDAP Analysis Module LDAP response-time monitoring and error diagnostics are required to understand of how a web application processes critical user-visible operations. Practically every login operation in most web applications depends on LDAP performance somewhere in the application delivery chain. DCRUM is now equipped to precisely monitor LDAP and LDAPS operations identified by name, and to detect LDAP response errors that directly affect end users of the web application. Deep LDAP protocol analysis in DCRUM reveals issues that otherwise are difficult to spot and quantify in terms of business impact, especially when the LDAP environment is shared between many applications and built over the years using various architectures. DCRUM monitors LDAP request and response operation attributes. It matches response status and dozens of distinct error messages with specific request values. Such precise diagnostics lets you determine what happened within the LDAP infrastructure when a specific end-user transaction was waiting for authentication to complete. Enhanced Analysis Modules - Oracle, SAP, Web, SQL DB, SSL Oracle EBS Analysis Improvements A new multi-level reporting structure on the E-Business Suite (EBS) form name helps organize reports in a way that reflects the EBS application s business model and usage patterns. This reporting allows you to identify business processes that suffer from network quality issues or 14

EBS server response issues. The reporting model shows the windows that a user invokes to complete the tasks and its corresponding individual user actions with screen controls. The EBS analysis module now has the intelligence to track the X-Forwarded-For headers. EBS user activity is tracked through the load balancer, revealing the load balancer s influence on end-user experience. Intelligence was also added to detect all user-visible EBS errors while all individual activities for every EBS user are examined. New reports show error incidents in context of the related business process, user activity, and server load. If end-to-end monitoring is enabled to monitor the database tier of the EBS infrastructure, you can also correlate user-visible errors to database performance issues. SAP Analysis Improvements DCRUM 12.1 decrypts SAP SNC in the popular Kerberos environment. Decryption is performed on the AMD using the same Kerberos keys that the servers use. The keys are stored in the same secure manner as typical SSL key storage. DCRUM with SNC decryption support is the industry-first and only solution for complete SAP GUI performance monitoring using passive, non-intrusive agentless technology. SAP operation identification has been enhanced to better provide a precise business impact assessment of the user-visible performance issues. Now SAP operation names include T-Code and SAP UI status (that is, Window status). Optionally, SAP GUI Window titles or other information carried in the SAP GUI transaction requests can be set up as the operation identifier. 15

This extra level of detail in SAP operation identification assures that all differences in response time are captured precisely, regardless of the business context of the T-Code executed by the user. New diagnostic deep-dive analysis of the T-Code load sequence reveals and visualizes dependencies between SAP transaction design, SAP server performance, and network delivery. The load sequence diagram illustrates what happens during each SAP T-Code execution. This analysis identifies whether the issues are on the server or network. It also determines if the issue results from the way the transaction s network interactions have been designed, or because of a network and application characteristics mismatch. Other Enhancements Web, SQL DB, SSL Many other analysis modules have been updated and enhanced. Most notably: The Web analysis module has new intelligence for NTLM user name recognition and improved browser type categorization. The SQL Database analysis module has new intelligence that includes DRDA analysis module extensions, a more precise analysis of the aggregation queries, database server error detection and reporting, and smarter Top N query auto-learning. 16

The SSL analysis module has new intelligence for TLS 1.2 decryption and better SSL key diagnostics. Performance and Usability Improvements Zero-configuration Web Application Discovery The updated HTTP Express analysis module automatically recognizes all HTTP software services that are accessed by internal and external clients both within the monitored enterprise network as well as for Internet hosted services. Smarter top N URL monitoring provides accurate reporting on the most active URLs that have uneven usage levels throughout the day. A common pool for the top N URLs is shared by all auto-learned servers. This assures that the most used URLs always are shown at the top of the report, regardless of migrations from server to server on the web or in the virtualized environments. Further customizations for monitoring auto-learned web hosts are possible using more detailed URL auto-learning on selected hosts, or user-action recognition based on request parameters and response content data. DCRUM Configuration Improvements Release 12.1 continues improvements to the configuration console and guided configuration wizard. Standard and guided perspectives are integrated into a single, concise, and user friendly interface. From a single location you can configure your entire system, complete with step-by-step guidance. If you need a direct access to any configuration option, you can easily navigate there from a comprehensive top-level menu. After you complete the configuration, the console presents the health of the monitored system in a form that is easy to understand. 17

Easier Use and Customization of BSM Release 12.1 provides enhancements to Business Service Management (BSM) for better performance, scalability, and dashboard usability. These enhancements improve your ability to design and implement customized solutions. Innovations in 12.1 include: Faster, simpler deployment and configuration Improved performance for rendering dashboards Reduced overhead of database queries Improved migration procedures for preserving customized deployments Efficiency improvements for building and maintaining large scale models Improved BSM Portlet and Dashboard Functionality BSM has significantly improved performance for calculating and reporting metric statistics. All hourly, daily, weekly, and monthly metric statistics are automatically calculated and display ten times faster. Additional improvements include: Support for Chrome and IE 10 Use of Gauge and Traffic Light charts with raw BSM data New Matrix Table option for the DMI Portlet when using BSM data Ability to hide filter icons within the DMI Portlet Improved communication between the Service Tree and standard BSM portlets, including dimension improvements and the ability to specify channel names Enhancements to UPA portlet, including the ability to hide legends and other titles, and additional summary modes 18

Initiation of the Add-On portlets library with the Tab Navigator Improved dimension display in service tooltips, an option to display tooltips with a right-click, the ability to clone and modify standard templates, and easier editing of message translators Compuware Security Server The Compuware Security Server (CSS) added the following enhancements in Release 12.1: Optional support for Synthetic Monitoring 12.1. Administrators can also use the CSS auditing feature to view records for configuration changes made in the Synthetic Monitoring console. Client-side caching is available so existing users can continue to log into integrated product components if the CSS is temporarily down. Auditing enhancements allow an administrator to identify the component that was affected by the audit event. Administrators can now configure a default user group that is assigned to all new users. Support for Internet Explorer 10 and Chrome browsers. Performance improvements: A new client side caching feature allows users to log in when the CSS is temporarily unavailable and also lessens the number of requests to the server from the clients. LDAP caching has been optimized. The CSS uses the latest 1.6 JRE.. Information in the client - server calls has been consolidated. Also Included in This Release Additional Improvements and Changes Business Units Configuration Enhancement All traffic matching rules that are assigned directly to an application in the Business Units Configuration are presented on reports as the All other transaction. You cannot edit this transaction and it does not possess qualities such as steps that are part of regular DCRUM transaction configuration. The All other transaction plays an important role when you define applications and transactions. It can either carry an entire configuration or serve as a filter that enables you to see data pertaining to an application but not covered by more specific rules. Check for Updates New to Release 12.1 is the ability to check if there are product updates (in the form of Service Packs) available for your DCRUM deployment. You enable this capability from the RUM 19

Console's Help dropdown menu. From the menu, select Check for Updates. This will connect to Compuware's Update server and give you a report on all of your DCRUM components and whether there are major Releases available or Service Pack updates available for download. Further enhancements are planned in the future releases. Use the APM Community for Upgrade and Migration Guidance The APM Community's Upgrade and Migration Center has a number of resources to help you plan your upgrade or migration project: Product demonstrations, Technical Talks, release notes and product documentation. Questionnaires and planning templates to help you plan the upgrade project. The questionnaire will help you create an inventory of your current deployment so that you have a baseline from which to plan. Hardware recommendations are available so that you can assess resources you'll need for the new release. Migration and upgrade forums moderated by Compuware APM experts. Component Currency DCRUM components have been upgraded to work on or with the latest versions of the applicable supporting vendor technology, including: Microsoft SQL Server 2012 Windows Server 2012 Windows 8 Internet Explorer 10 Analysis Module Updates All dedicated DCRUM analysis modules have been updated to work with the latest releases of application servers and network protocols from the respective vendors. Most notable currency updates include monitoring support for: SAP GUI 7.3 DRDA level 5 Oracle Database 11G R2 Oracle EBS 12 Microsoft SQL Server 2012 TLS 1.2 20

Resolved Issues Central Analysis Server and Advanced Diagnostics Server 12.1.3 Table 1. CAS and ADS 12.1.3 Resolved Issues APMODCRUM-1639 APMODCRUM-8590 771425 APMODCRUM-10657 813758 APMODCRUM-10727 815267 APMODCRUM-10963 819065 APMODCRUM-10987 00819744 APMODCRUM-11147 APMODCRUM-11177 824387 APMODCRUM-11200 825172 APMODCRUM-11229 825709 APMODCRUM-11302 823253 831433 APMODCRUM-11340 827997 APMODCRUM-11430 741892 APMODCRUM-11435 829882 APMODCRUM-11609 833035 Reporting group definitions with a page name and URL are not synchronized with ADS. Installation fails when special characters are used in the user password. Bulk insert fails intermittently while the index maintenance is in progress. Operation hierarchy causes a report problem. CAS upgrade from release 11.7 leads to a database issue caused by non-standard change of DB user name. No operation count is stored for Citrix Data Center Tier-Application-Trans aggregates. Unauthorized access to UserCfg by Custom_Report_user. ADS creates a problem when the hpdata host field is empty. ADS - Unexpected client IP address is listed on the reports and indicating 0.0.0.0 value. The PurePath filter is too wide when drilling down from application->transaction->tier. Business Units configuration was changed by the CAS after a daily maintenance task. Synchronization of transactions is not based on page names between CAS and ADS in release 12.1. SNMP traps are not firing completely. URLs are not prefixed by page names. The software service filter on DMI is blank. 21

Table 1. CAS and ADS 12.1.3 Resolved Issues (continued) APMODCRUM-11639 833650 APMODCRUM-11722 APMODCRUM-11740 822896 834125 APMODCRUM-11753 835386 APMODCRUM-11754 833013 APMODCRUM-11756 835995 APMODCRUM-11781 837466 APMODCRUM-11833 APMODCRUM-11834 APMODCRUM-11835 APMODCRUM-11852 840676 APMODCRUM-11860 841243 APMODCRUM-11905 843599 APMODCRUM-11943 00828703 00846052 APMODCRUM-11975 847741 APMODCRUM-11989 APMODCRUM-12071 APMODCRUM-12133 852956 APMODCRUM-12193 The ADS / CAS 12.1.1 and 12.1.2 service pack changes the server service log on settings. There is a potential memory leak. A high memory usage is occurring in the CAS. Alert notification traps do not work properly and get null pointer exceptions. Scheduled reports are using incorrect time. CAS stops responding after a change in the Business Units configuration. DCRUM 12.1.1 Business Unit configurations disappear after a server reboot. Inadequate access control to Web Services WSDL. Inadequate access control for the REST method. Cross-site scripting vulnerability in LSServlet for the dmiaction parameter. The outgoing packets metric for NFC link is zero. Program that calls Webservices APIs to retrieve data from the CAS using the Java API sometimes gets stuck. SNMP traps are not being sent. Business Unit Configuration is incorrectly initialized on server start-up which causes erroneous rules with typeoperation and label "*". DMI report text export provides different data than the original report. Error upon loading the User Activity Details DMI report for user name with WINS. Missing access control for the REST method. Synchronization of Business Units leads to a deadlock causing inability to generate reports. Disk space usage acquisition for localhost fails. 22

Table 1. CAS and ADS 12.1.3 Resolved Issues (continued) APMODCRUM-12273 CAS stops saving data when it reaches the server cache limit. Central Analysis Server and Advanced Diagnostics Server 12.1.2 Table 2. CAS and ADS 12.1.2 Resolved Issues APMODCRUM-2119 APMODCRUM-2454 APMODCRUM-7852 APMODCRUM-10031 801224 APMODCRUM-10071 802220 APMODCRUM-10094 802998 APMODCRUM-10125 803606 APMODCRUM-10154 804045 APMODCRUM-10155 804146 APMODCRUM-10217 805303 APMODCRUM-10236 794170 800943 APMODCRUM-10264 805807 APMODCRUM-10309 806996 APMODCRUM-10720 814962 APMODCRUM-10721 SAPGUI: WAN optimization network and server times are calculated incorrectly. SAP WAN optimization: differences in operation time between page data and zdata in the case of an ADCD adjustment. Unjustified low level of data monitoring on the AMD. Lack of server limit license should be indicated on the report server. No drilldown from CAS report to HTTP header on ADS for SAPGUI operations. Drilldowns from CAS User Activity to ADS flowcharts are passing always the current time range instead of the period of time selected on User Activity. Lag in user propagation from CSS to CAS. Timestamp in task-based files is incorrect. The default Citrix dashboard "published application" is slow. One HTTP operation with many HTTP request methods causes discrepancies in reports. First-time LDAP login to the CAS fails. If a particular user is not already defined in CSS and the user tries to log in using LDAP authentication for the first time, it fails. The next attempt is successful. Attachments are not visible on ios (iphone). Alarms are displayed in milliseconds after upgrade. CAS stopped processing data after CSS had a database connectivity issue. CAS did not restart after it lost the connection to the database. 23

Table 2. CAS and ADS 12.1.2 Resolved Issues (continued) 815119 APMODCRUM-10752 815622 APMODCRUM-10801 816363 APMODCRUM-10809 816562 APMODCRUM-10912 APMODCRUM-10936 818852 APMODCRUM-7336 738954 APMODCRUM-7549 741892 APMODCRUM-7565 742291 APMODCRUM-8093 APMODCRUM-8191 00760595 00767983 APMODCRUM-8199 759252 APMODCRUM-8381 765663 APMODCRUM-8410 00766384 00792614 APMODCRUM-8424 766754 APMODCRUM-8539 APMODCRUM-8684 774278 APMODCRUM-9057 781588 The CAS installation could not recognize the SQL service name. CAS does not use an imported reporting hierarchy for SOAP. Netflow network monitoring inconsistency in metrics when displayed in 12.1 CAS. DMI filter results in 500 error. Logging into the report server takes a long time. Cannot publish down to AMD from Console - Error 500. SNMP traps are not firing completely. CAS primary key violation occurs on the rtmuser table. Metric charts for Client/Server Bandwidth Usage Breakdown - error in chart definition. Business Units - Tiers rule filter is not working. Java NullPointerException is given while saving the vdata on the ADS. Germanic umlaut is not correctly displayed in a DMI table. Updating the list of business units fails because RESTServlet is not available. AMD cannot identify the IP address of the TimeSynch server. Number of errors are inconsistent with detailed errors report. Business Unit supports the username. MQ tier is not populated with operations data. MQ operations data is not present on the top level view of the Tiers report while drilling down into the MQ tier. 24

Table 2. CAS and ADS 12.1.2 Resolved Issues (continued) APMODCRUM-9317 785804 APMODCRUM-9387 APMODCRUM-9454 789348 APMODCRUM-9488 790286 APMODCRUM-9499 790620 APMODCRUM-9473 789829 APMODCRUM-9537 791296 APMODCRUM-9548 784892 APMODCRUM-9558 792468 APMODCRUM-9622 793981 APMODCRUM-9629 794153 APMODCRUM-9848 APMODCRUM-9636 794204 APMODCRUM-9650 794422 APMODCRUM-9666 794718 APMODCRUM-9739 APMODCRUM-9744 794238 APMODCRUM-9799 797147 Export to PDF does not work with dynamic charts on Windows Server 2012 or Windows 8, and produces an exception. Problem with IP address input. No validation performed. Improper handling of HTTP operations with a request method breaks the URL hierarchy. CAS is processing transdata samples from Active Manager for too long. Cannot add an AMD to the CAS in the EUE console. Chart legend items are cut off. Login fails for new users when logging into the CAS. MQ tiers are grayed out in the Enterprise Portal. The uninstall button is wrongly displayed when changing server settings. Some report servers cannot connect to the CSS after an upgrade. Transaction size for SMTP analyzer. Some licenses do not work on CAS-Web and require a CAS-Enterprise license. CAS security scan has detected flaws. Applying business hours configuration works improperly in Asian time zones. Request for Business Units to be configured for user IP ranges. The redirect time metric changes after adding the http redirect time metric to the report. Korean characters in software service. 25

Table 2. CAS and ADS 12.1.2 Resolved Issues (continued) APMODCRUM-9843 797914 APMODCRUM-9844 797919 APMODCRUM-9869 APMODCRUM-9877 APMODCRUM-9879 798410 APMODCRUM-9880 798430 APMODCRUM-9912 Reports scheduled for sending in release 11.x are not being sent after the upgrade to release 12.1. Long alarm processing with zero traffic events. Synthetic backbone tier is marked as front-end. However, it is not listed on application view. CAS does not process zdata samples (NumberFormatException). The DMI report configuration interface hangs when downloading a list of dimensions and metrics. Selecting "Fit to Screen" in Chart Settings results in a redirect to an unformated HTML page. DMI "Operations" report error: "Cannot filter by data in this view". Central Analysis Server and Advanced Diagnostics Server 12.1.1 Table 3. CAS and ADS 12.1.1 Resolved Issues APMODCRUM-2064 APMODCRUM-2433 570003 APMODCRUM-3639 APMODCRUM-4863 APMODCRUM-5166 699063 APMODCRUM-5738 APMODCRUM-6968 732981 APMODCRUM-7044 734055 APMODCRUM-7492 740963 APMODCRUM-7581 The installation process should not require administrator "sa" user if CAS/ADS database already exists. CAS memory issue. Provide a list of possible options to transform user names and IP addresses in CAS, using MAP_CLASS_IPUserForce-map and adjacent properties. Incorrect value of unique users on all aggregated types of View (from cache). Unable to save "User Defined" alerts in a MIB file via RUM Console. Blank CAS report when you click the Reference URL link in the SyM-CAS built in email alerts. The Auto refresh option stops refreshing an open report after several days. CAS - MHT report in browser issue. Number of operations does not match the sum of Operation load time (range x) metrics in report. The DMI reports email was reported as a virus and blocked. 26

Table 3. CAS and ADS 12.1.1 Resolved Issues (continued) 742435 APMODCRUM-7879 749836 APMODCRUM-8051 APMODCRUM-8052 APMODCRUM-8135 757820 APMODCRUM-8174 APMODCRUM-8209 761251 APMODCRUM-8227 APMODCRUM-8283 762464 APMODCRUM-8291 APMODCRUM-8370 APMODCRUM-8373 APMODCRUM-8392 00765865 00768376 APMODCRUM-8408 766361 APMODCRUM-8426 766823 APMODCRUM-8443 767385 APMODCRUM-8477 767918 APMODCRUM-8487 768376 APMODCRUM-8489 768511 Generating DMI reports for a previous day takes more than 20 minutes. Reports on Oracle Forms errors do not display error strings. Reports on LDAP errors do not display error strings. Unable to save a DMI report definition. No data for users for "last period" and "today" in applications front-end tier context. Error upon loading DMI report "User Activity Details". Delay in data display on charts, and wrong date format. After the upgrade from 12.0.2 to 12.1, the server memory limit is reverted back to default, not the value set before the upgrade. CAS upgrade problem. CAS performance issue when waiting for timeout from non-reachable slave server. Update CAS 12.1.1 to use NTLM v2; SQL server roles/permissions needed for installation. Dynamic charts do not render when there are more than 1000 rows to display. URLs are not being aged. CAS - upgrade halting. The new bulk insert test breaks previously working configurations. CAS 12.1 cannot to log on to VantageView 11.5. PDF export of a DMI report does not contain charts. The drilldown doesn't work for username (ip+wins). 27

Table 3. CAS and ADS 12.1.1 Resolved Issues (continued) APMODCRUM-8499 768613 APMODCRUM-8502 768646 APMODCRUM-8559 770300 APMODCRUM-8560 770301 APMODCRUM-8590 771425 APMODCRUM-8597 771673 APMODCRUM-8663 APMODCRUM-8709 APMODCRUM-8736 00775722 00777453 APMODCRUM-8872 APMODCRUM-8970 780413 The section tabs cannot be modified in DMI. CAS log full of exceptions. Date format issue with scheduled DMI reports. CAS - server names are already in use. CAS version 12.1: install fails with special chars in user password. DMI chart does not export to PDF. The upper memory limit for SQL server set for the database upgrade is not reverted back to the original value but instead set to 16 MB only. Gomez SaaS performance views should be improved to reduce the CAS hardware requirements for SaaS data only. Bulk insert fails while executed on local SQL. Bulk insert failures blocked data processing. The task generated report name contains a literal timestamp string instead of the actual time. Central Analysis Server and Advanced Diagnostics Server 12.1 Table 4. CAS and ADS 12.1 Resolved Issues APMODCRUM-1030 APMODCRUM-112 APMODCRUM-1186 APMODCRUM-1216 APMODCRUM-1224 'All other' SAP transactions from a slave server not presented on the master server. Different metric values on TierData and MTView. Add ability to perform hierarchical reporting for Oracle Forms. When enhanced user name recognition is used and the users are recognized using the session ID context, users are not assigned to individual hits in the ADS Hit details. Business transactions are removed from CAS slave server. 28

Table 4. CAS and ADS 12.1 Resolved Issues (continued) APMODCRUM-1365 APMODCRUM-1609 APMODCRUM-1632 APMODCRUM-1639 APMODCRUM-1839 APMODCRUM-1924 APMODCRUM-2064 APMODCRUM-2151 APMODCRUM-2222 APMODCRUM-2229 APMODCRUM-2291 APMODCRUM-2298 APMODCRUM-2303 APMODCRUM-2311 APMODCRUM-2325 APMODCRUM-2336 APMODCRUM-2349 APMODCRUM-2392 APMODCRUM-2433 APMODCRUM-2508 APMODCRUM-2515 APMODCRUM-2881 Username mapping doesn't work on Page Analysis and Transactions View. When a SQL Server is not installed on a CAS/ADS server, the installation puts a non-working path in the DB path. For SAP: data should not be aggregated for Operations belonging to different Task/Modules/Services. Report Group definitions with page name and URL are not synchronized with ADS. Java scripts run too slow - message within Internet Explorer (Metric Chart report). Loss of report rights after logging to CAS using a user login with letters of different case. Installation process should not require sa user if CAS/ADS database already exists. Baselines on charts do not show for whole day. When launching the CAS installation from a remote machine on a local network and Windows User Account Control (UAC) is on, the The publisher could not be verified. Are you sure you want to run this software? message appears. SQL error while displaying report with Operation requests metric chosen. Different values Aborts in breakdown metrics tooltip (export) and 'standalone' value. Fatal error during opening report with Network tiers. 'Client optimized network' tier contains different values of Errors and TCP Errors. CAS - Step names for SAP T-Code are not available. Make the list of HTTP errors configurable. CAS service could not load the Java application after upgrading to release 12.0. Display user filter on User Diagnostics report. Server restarts: OutOfMemoryError: Java heap space CAS memory issue. CAS - IP filter next button returns none. After upgrading to the release 12, the CAS user was not migrated to the CSS successfully. Drill down from User Activity report for Cerner MQ analyzer to User activity details report provides no data. 29

Table 4. CAS and ADS 12.1 Resolved Issues (continued) APMODCRUM-3037 APMODCRUM-3117 APMODCRUM-3170 APMODCRUM-3285 APMODCRUM-3351 APMODCRUM-344 APMODCRUM-3478 APMODCRUM-3583 APMODCRUM-3639 APMODCRUM-3658 APMODCRUM-3665 APMODCRUM-3794 APMODCRUM-3985 APMODCRUM-4213 APMODCRUM-4366 APMODCRUM-4375 APMODCRUM-4447 APMODCRUM-4450 APMODCRUM-4511 APMODCRUM-4628 APMODCRUM-4633 APMODCRUM-4648 APMODCRUM-4653 APMODCRUM-4863 alarm LOAD_TIME_4_URL works only for some URLs. Distributions thresholds for NRB have confused metrics. User details show no specific URLS for users in realized bandwidth distribution aggregates. When transaction rule is based on 'Operation mask', then reporting group in ADS will not be created for that transaction. CAS not importing users from CSS. Long execution time for task daily (command TrendsImpl). Username pulled from CAS to Enterprise Portal. ADS - user mapping file not working. Documentation: provide a list of possible options to transform user names and IP addresses in CAS, using MAP_CLASS_IPUserForce-map and adjacent properties. Not seeing transactions from the Cerner RTMS Tier. Report scheduling after changing email. AMD interface utilization on module status. Post release 12 upgrade - CAS is slow to log in and in some cases not able to log in at all. No data on report in Transaction Load Sequence because of filter. Software Service DMI report is not returning full amount of data from two slaves. Unable the pass the URL from the CAS to ADS. Page URL is incorrect - opstatus field is not available, presented in the reports as null. NumberFormatException during sample processing. Application performance incorrectly calculated - ClientLevelDetailsOnDemand dataview. opstatus field is not available in cpdata samples - Operation names in CAS and ADS are different for the same item. Unable to use fixed performance thresholds for locations. Operations with opstatus are not classified correctly vs technical hierarchy. Operation name for SAP GUI analyzer contains only SAP-Tcode value, opstatus field is not shown (but available in zdata samples). Incorrect value of unique users on all aggregated type of view - from cache. 30

Table 4. CAS and ADS 12.1 Resolved Issues (continued) APMODCRUM-4864 APMODCRUM-490 APMODCRUM-4947 APMODCRUM-5046 APMODCRUM-5115 APMODCRUM-5166 APMODCRUM-5323 APMODCRUM-5679 APMODCRUM-568 APMODCRUM-587 APMODCRUM-6770 APMODCRUM-6814 APMODCRUM-6823 APMODCRUM-7069 APMODCRUM-7232 APMODCRUM-7303 APMODCRUM-7521 DT 00000 75112 DT 00000 75624 DT 00000 76715 DT 00000 77740 Large amount of data being transmitted between CSS and ADS. Incorrect value of Xmx setting after upgrade. Server cannot start after upgrade from 12.0 GA. Apache server side include cross site scripting vulnerability. HTTP errors different value between TDView (appl, trans, no tier) and MTView. Unable to save "user defined" alerts in a MIB file via EUE Console. CAS release 12 indicates licensing message when no AMD is present. Transaction Load Sequence Report not working after installing SP1 on top of 12.0 GA. Client IP is shown as username, when we want to hide it. Users entered into the Enterprise Portal are not available in the CAS User list until those users have logged into the CAS. IE 10: JavaScript error on every page: Expected identifier, line 1, character 9. HTTP request method keeps changing for some URLs. Upgrade from 12.x to 12.1 of SQL operation hierarchy does not work. Gaps in data. CAS and Enterprise Portal performance issue. Flood of Java exceptions seems to cause restarts daily during nightly tasks. Client site displayed as joined 'location + region' when report from cache. Long execution time for daily task (command TrendsImpl). In some SAP user sessions, the Server RTT metric will be lower than for other sessions. User loses the report rights when logging in to the CAS by using a user name in a different case, for example: User and user. DMI report drilldowns defined in Release 11.1 or earlier disappear after upgrading the report Release 12.0 or later. Agentless Monitoring Device 12.1.3 Table 5. AMD Resolved Issues 12.1.3 APMODCRUM-6912 The "all other" records for all analyzers except HTTP contain invalid network metrics. 31

Table 5. AMD Resolved Issues 12.1.3 (continued) APMODCRUM-8482 768189 APMODCRUM-9946 800250 APMODCRUM-9991 800800 APMODCRUM-10386 808626 APMODCRUM-10523 811178 APMODCRUM-10988 819751 819658 APMODCRUM-11061 806190 APMODCRUM-11068 APMODCRUM-11073 APMODCRUM-11164 APMODCRUM-11692 823775 834670 834107 APMODCRUM-11187 824458 APMODCRUM-11355 828334 APMODCRUM-11443 APMODCRUM-11503 APMODCRUM-11511 836210 831266 APMODCRUM-11529 APMODCRUM-11597 832871 AMD release 12.1.1 restarts in the Exchange analyzer, causing high memory consumption and memory corruption. MQ operations are too unique. Elements of a page include components that are not part of the page. The AMD creates core dumps for the Citrix ICA analyzer in the 12.1.1 release. CAS reports URL encoded SQL queries. AMD jumps to sampling mode and drops to 1/20. AMD receives restarts few times a day with a core dump and crashes because of assertion HTTP frames code. AMD restarts frequently with stack traces directing on VoIP. AMD often crashes and dumps core files. AMD restarts due to UriParser::normalizeChars Sensitive data masking in the vdata file does not work. AMD restarts several times during 24 hours without any obvious reason. Creating a sequence transaction based on SAP operation does not work. AMD log file indicates ERROR: incorrect AMD ID in line x. AMD generates a core dump every few weeks. AMD release 12.0.3 switches to sampling mode for no apparent reason. AMD generates a stack trace when processing invalid XML document. 32

Table 5. AMD Resolved Issues 12.1.3 (continued) APMODCRUM-11602 832895 APMODCRUM-11759 APMODCRUM-11810 APMODCRUM-11904 845827 APMODCRUM-11992 846296 APMODCRUM-12056 APMODCRUM-12081 852119 AMD crashes in MQ analyzer. Upgrade of AMD OS from 5.5 to 5.9 appears to have broken/disabled the RTM to connect to the SCA keystore. Refresh ixgbe_rtm custom driver to provide support for modern 10 gigabit cards. The incoming packets and bytes are different. Netflow analyzer reported different incoming/outgoing speed based on other monitoring tools. HTTP decode does not offer the same capabilities as are available for user recognition. Oracle analyzer causes the AMD to restart. Agentless Monitoring Device 12.1.2 Table 6. AMD Resolved Issues 12.1.2 APMODCRUM-10023 801143 APMODCRUM-10105 803276 APMODCRUM-10291 APMODCRUM-10437 809603 APMODCRUM-10605 APMODCRUM-10658 813873 APMODCRUM-10809 816562 APMODCRUM-10882 APMODCRUM-5704 APMODCRUM-7185 AMD 12.1.2.35 - Core dumps due to MQ analyzer. Core dumps on AMD for Transport Layer Security version 1.1 and 1.2. AMD restarts with core dumps for Transport Layer Security version 1.1 and 1.2. Monitoring software restarted and generated core. Support for Java 7 for the AMD. Masking out parameters in HTTP header data does not work. Netflow network monitoring inconsistency in metrics when displayed in 12.1 CAS AMD is filling up rtmgate.log with Sending command messages (9 GB). AMD does not install when /tmp is full. Changes in removing_compuware_user script. 33