Release Notes for Cisco Transaction Analyzer for SAP 2.0.1

Hardware Requirements for Transaction Analyzer Server

The server where Cisco Transaction Analyzer is installed must meet the following minimum hardware requirements:

• Pentium-compatible 2 GHz processor (dual processor recommended)
• 2 GB of RAM dedicated to Transaction Analyzer (4 GB or higher recommended)
• 1 GB of available hard disk space (refer to the Cisco Transaction Analyzer Installation and Configuration Guide for information on calculating disk space).
• Network adapter

Software Requirements for Transaction Analyzer Server

The server where Cisco Transaction Analyzer is installed must meet the following minimum software requirements:

• Supported Operating Systems:

– Microsoft Windows Server® 2008 (Standard, Enterprise, Datacenter or Web Editions) or above

• Supported Transaction Analyzer Databases:

– Microsoft SQL Server™ 2008 R2 or Microsoft SQL Server™ 2012 (Standard or Enterprise Edition)

Note The Transaction Analyzer database server should be set to the same time zone as the Microsoft SQL Server Reporting Service Server.

• Microsoft SQL Server™ Reporting Services 2008 R2 or Microsoft SQL Server™ Reporting Services 2012
• Windows® Internet Explorer® v6.0 or later is recommended (refer to the Microsoft SQL Server Reporting Services website at http://www.microsoft.com/Sqlserver/2005/en/us/reporting-services.aspx for information on supported browsers)

Note When viewing Transaction Analyzer reports in your browser, the data collection time displayed in the report is the local time on the Microsoft Reporting Service server. It is not the local time of the machine from which you are viewing the reports.

• Oracle® Client 9i, 10g, or 11g (64-bit) must be installed on the Transaction Analyzer server to monitor SAP Oracle databases; required components include Oracle Windows Interfaces and Oracle Net
• IBM® DB2® Connect 9.1 (64-bit) must be installed on the Transaction Analyzer server to monitor SAP DB2 databases on z/OS® or OS/390®
• IBM® DB2® Runtime Client 9.1 (64-bit) must be installed on the Transaction Analyzer server to monitor SAP DB2 databases on other platforms
• MDAC v2.6, v2.7, or v2.8
• Microsoft®.NET™ Framework v4.0 installed on the server where the Cisco Transaction Analyzer application is installed

Note The latest Windows update is required after installing.NET Framework 4.0.

Software Requirements for SAP ABAP Data Collection

• Supported SAP Versions:

– SAP® R/3 46c (Support Package 50), 46d (Support Package 15), 6.10 (Support Package 6), 6.20 (including 4.7), 6.30, 6.40, 7.0, 7.10, 7.11, 7.20, 7.30 and 7.40

Note Cisco recommends that you install the latest kernel patch for the installed SAP version.

• Supported SAP Databases (to collect SQL query details):

– Microsoft SQL Server 2000 SP1 through SP4 (Standard or Enterprise Edition), Microsoft SQL Server 2005 and Microsoft SQL Server 2008 (Standard or Enterprise Edition)

– Oracle Database v9i, v10g, and v11g (Standard or Enterprise Edition)

– IBM DB2 UDB v8.1 FixPak 4 or later, v8.2, v9.1, v9.5, and v9.7 (Enterprise Edition) on AIX, Linux, Unix®, and Windows

– IBM DB2 for z/OS and OS/390 v8 and v9

Note For SAP data collection, any type of database can be used.

Cisco Exporter for SAP Users Upgrade Issue

When upgrading Cisco Exporter for SAP Users to Transaction Analyzer v2.0.1, the Configuration.xml file is not copied if the installation path is different than the previous version. You must back up the Configuration.xml file located in the Cisco Exporter for SAP Users installation directory, upgrade to the latest version, and then copy the Configuration.xml file into the new installation directory.

SQL Server Agent Not Configured For Autostart

When installing Cisco Transaction Analyzer, the SQL Server agent is not automatically configured for Autostart. If the SQL Server agent is not running when the Cisco Transaction Analyzer database is created, the Cisco Transaction Analyzer jobs will not execute.

To resolve this issue, set the SQL Server Agent to Autostart after configuring the product and start the service.

Cisco Transaction Analyzer SQL Jobs May Fail to Run

When creating the Cisco Transaction Analyzer database, you specify the user account to connect to the database. This user account is set as the owner of the Cisco Transaction Analyzer SQL jobs. However, if the owner of the SQL jobs uses a domain account and the domain controller cannot be found, the SQL Server jobs may fail to run.

This is a known Microsoft issue and is documented in Microsoft Knowledge Base Article 241643.

To work around the issue, change the owner of the SQL jobs to “sa”.

For additional information, refer to Microsoft Knowledge Base Article 834124.

SAP Statistic Issues on SAP v7.0 and v7.10 Systems

On SAP v7.0 and v7.10, the function used to collect statistics is returning marshaling exceptions. Cisco Transaction Analyzer calls a pre-SAP v7.0 function to work around this issue. However, the workaround causes the following issues:

• The function does not return background job statistics.
• The Database Request Time values do not match the values in STAD.
• The function does not return RFC details information.

The marshaling exception is a known SAP Web AS ABAP 7.0 and 7.10 issue, and SAP is working on a Kernel patch to resolve it.

Cisco Transaction Analyzer controls which function to call via a registry value (MinimumPatch). The value in v1.9 is set by default to 999 so all 7.0 and 7.10 systems will not call the new function. When SAP releases a patch to resolve the marshaling issue, Cisco will release a hotfix to update the registry value.

Duplicate Transaction Analyzer Report Model

If you have Cisco Transaction Analyzer reports configured for different Transaction Analyzer databases on the same Reporting Services server, duplicate report models display with the same name (Transaction Analyzer).

Charts May Not Display Date and Time Properly in Reporting Services 2008

Cisco Transaction Analyzer reports that include charts may not display properly when running reports in Microsoft SQL Server Reporting Services 2008. For example, a chart may display only date instead of date and time.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

© 2015 Cisco Systems, Inc. All rights reserved.