End-to-End Monitoring of SAP Applications

Transcription

1 IBM SmartCloud Application Performance Management End-to-End Monitoring of SAP Applications John Griffith September 2012 Copyright International Business Machines Corporation 2012.

2 Table of Contents Introduction... 3 Use Case Scenarios... 4 Use Case 1: End-user Monitoring... 4 Use Case 2: Introducing Resource monitoring... 6 Use Case 3: Introducing Deep-dive Analytics... 8 Solution Environment Overview and Deployment Software Components Overview Phase 1: End-user Monitoring Capability Phase 2: Introducing the Robotic Response Time capability Phase 3: Introducing the resource monitoring capability Phase 4: Introducing Deep-dive Transaction Tracking Configuring Web Response Time monitoring...22 Port mirroring Enabling network monitoring protocol on the WRT machine with Windows OS Verifying WRT is capturing data in the TEPS console Recording and Playing Back SAP Transactions Recording the transactions Setting up the playback agent Using the Application Management Console to Manage SAP Monitoring Define server components...27 Define clients Configure the Applications Monitoring with the SAP Agent...30 Instance configuration Troubleshooting Solution Manager for SAP and Process Integrator for SAP Using the Application Performance User Interface Configuring the data provider Creating an SAP application from a template Deep-Dive Analytics using Transaction Tracking Transaction Collector and Reporter J2EE Agent Managing Server Netweaver Data Collector Putting the deep-dive bits together Conclusion Appendix A: Architecture Appendix B: Information Centers Appendix C: Additional References... 46

3 Introduction The intended audience for this solution paper is the application owner that needs the ability to monitor the end-to-end experience for management of the performance and availability of their applications. This solution also provides a phased approach for installing and configuring the following monitoring and tracking functions: Real user monitoring using agentless network monitoring Active monitoring using robotics Resource monitoring of the database, operating system, and SAP instances Deep-dive analytics with transaction tracking End-to-end experience monitoring is a critical element of the overall Application Performance Management (APM) implementation. For additional information on APM, please refer to the Best Practices for Application Performance Management link in Appendix C. This solution also demonstrates a graphical user interface with immediately available, fastresponse dashboards for managing performance and availability of business applications. The user interface lis used to create highly customized dashboards for a business application through the use of templates. This solution and the use case scenarios, which are described in the next section, were tested and proven in our IBM lab.

4 Use Case Scenarios In this section we describe four use cases that use this solution s capabilities to enable the user to find the root cause of slow performance of a composite application. Use Case 1: End-user Monitoring SAP application owner, Tom, receives a trouble ticket stating that an SAP application is performing slowly and is unavailable at times. Tom uses a web browser and navigates to the Smart Cloud monitoring APM User Interface. He notices that the transactions and clients for this application are in critical state. Figure 1: Application Overview Tom follows the red and clicks on transactions to drill-down. This displays the transaction dashboard for that particular application.

5 Figure 2: Transaction Dashboard He notes that the first subtransaction shows critical status. Hecan obtain the problematic URL that might be causing the performance and availability issues. He also wants to understand which clients are affected, so Tom clicks the subtransaction. He sees that both the India and China operations teams are affected, according to the top ten client impact information. Figure 3: Transaction Dashboard

6 Tom feels confident that this might be a server-side resource issue focus around a particular URL. Use Case 2: Introducing Resource monitoring Resource monitoring, can help Tom narrow down the problem even further, either to the database and/or SAP instance. Tom owns the SAP solution manager for his area. He receives a problem ticket reporting that it is responding very slowly. Using the APM user interface, Tom sees that the application resources are in a critical state while his clients and transactions are fluctuating between critical and warning states. Figure 4: Application Dashboard He suspects that the resource issue might be affecting the application performance, so he clicks the resource link, which opens the resource dashboard. He notices a high number of critical alerts as well as a lower hit ratio. Figure 5: Resource Dashboard

7 Tom clicks the SAP summary to drill-down, which opens the SAP dashboard. He sees very low hit ratios with values violating his thresholds. Figure 6: SAP Details Dashboard Low hit ratios are directly related to database performance. He navigates back to the resource summary and drills down into the database dashboard. He identifies the critical situations and notes that the table space utilization for the Solution Manager database is very high. Also, the sort overflows percentage is going way over the threshold.

8 Figure 7: DB2 Detail Dashboard He confirms with the DB administrator that the database needs servicing to restore access performance. After servicing, the Solution Manager performance is restored and in good health. Use Case 3: Introducing Deep-dive Analytics In this scenario, the SAP Solution Manager JavaTM 2 Platform, Enterprise Edition (J2EE) application itself is having performance problems. The problematic URL of the transaction has been identified. Using the transaction view in the Tivoli Enterprise Portal console, Tom can launch to the transaction topology and see the relationships.

9 Figure 8: Transaction Links

10 Figure 9: Transaction Topology Tom identifies that there is an Enterprise JavaBeans (EJB) to JDBC call with a high response time deviation in the transaction path. From this node's context menu, he can link to different work views such as transaction details. He clicks the link for the Transaction Details where Tom notices high response time deviation peaks for the transaction over time.

11 Figure 10: Transaction Details in TEP console Back at the transaction topology, Tom clicks a link that takes him to a workspace showing the OS processes running on the database server. From his experience, some running processes can affect the database performance. Tom identifies a process taking up a considerable amount of CPU cycles and memory usage. Figure 11: OS processes

12 It turns out the process is a performance database test script that is inadvertently scheduled to run every two hours. Ultimately, stopping and removing this process from the cron table, restored the database and SAP solution manager performance.

13 Solution Environment Overview and Deployment This section provides an overview of the software components, architectural overview, and deployment procedures to describe how to deploy the solution to an existing IBM Tivoli Monitoring infrastructure to achieve the results in the use scenarios. Software Components Overview To monitor end user response time, the following components are used: IBM Tivoli Monitoringserver infrastructure ITCAM for Transactions Agents: o Web Response Time o Robotic Response Time o Application Management Console (AMC)Collector o Reporter IBM Tivoli Monitoring OS monitoring (bundled with Tivoli Monitoring) ITCAM for Applications: DB2 database agent or Oracle database agent ITCAM for Applications: SAP agent ITCAM for Application Diagnostics: o J2EE agent for Netweaver o Managing Server In our testing of the solution, most components were installed as Red Hat Enterprise Linux on 64-bit systems and Windows 2008 R2 64-bit. Phase 1: User Monitoring Capability This section describes the architectural overview and deployment procedures for the user capability of this solution. Architectural Overview Figure 12 shows an SAP environment and an existing Tivoli Monitoring infrastructure. The items in orange are the components needed to enable the user response time capability and the Application Performance Management User Interface (APM UI). The APM UI can be installed into an existing Tivoli Integrated Portal server. Otherwise, the portal server is installed along with the APM UI. Figure 12 also shows an agentless setup for the Web Response Time (WRT) agent, which is installed on a remote system to monitor TCP and HTTP traffic. For agentless monitoring, the WRT agent should be on the same network switch as the SAP server. The switch must be configured with port mirroring. The agentless data collected by this agent is retrieved by the ITCAM Transaction. Agent-less configuration is recommended because the WRT agent can be resource intensive.

14 Figure 12: Phase 1 End-user monitoring User Response Time Component Deployment In this section, we summarize the basic installation for this capability. If applicable, special notes or nuances are explained. Tivoli Integrated Portal Server portal server The portal server is required for the APM UI. As mentioned, if you want to use your own server, ensure it is at the required maintenance level. After the GA version of the portal server server is installed, install any required fix packs. For more details on product version and maintenance levels, refer to the Tivoli Integrated Portal entry in Appendix A. For more details on installing and configuring the Tivoli Integrated Portal server, refer to the Tivoli Integrated Portal entry in Appendix B. Application Performance Management User Interface (APM UI) Install the APM UI on the same machine as the portal server.

15 For more details on product version and maintenance levels, refer to the APM UI entry in Appendix A. For more details on installing and configuring the APM UI, refer to the APM UI entry in Appendix B. ITCAM for Transactions: Application Management Console agent The AMC agent is required to help manage clients, server components, applications, and transaction recordings. For more details on product version, refer to the AMC entry in Appendix A. For more details on installing and configuring the AMC agent, refer to the AMC entry in Appendix B. ITCAM for Transactions: Web Response Time agent In this solution, the WRT agent was installed on a dedicated system. This is recommended because the agent can potentially process large amounts of TCP data. For more details on product version, refer to the WRT entry in Appendix A. For more details on installing and configuring the WRT agent, refer to the WRT entry in Appendix B. Phase 2: Introducing the Robotic Response Time capability This section describes the architectural overview and deployment procedures to enable the robotic response time capability of this solution. Architectural Overview Figure 13 introduces the robotic playback capability with the Robotic Response Time agent that you use to record and play back key transactions of your application. Robotic Response Time agents can be deployed to different geographic locations in order to distinguish client and server issues.

16 Figure 13: Phase 2 - Robotic Monitoring Robotic Response Time Component Deployment In this section, we summarize the basic installation for this capability. If applicable, special notes or nuances are explained. Robotic Response Time agent you can use the Robotic Response Time (RRT) agent to play back your recorded SAP GUI and J2EE transactions. The RRT agent can be installed along with the AMC agent. However, it is not recommended to install it with the Web Response time agent. The RRT agent can be installed in different locations where clients are accessing your applications. For more details on product version and maintenance levels, refer to the RRT entry in Appendix A. For more details on installing and configuring the RRT agent, refer to the RRT entry in Appendix B. Rational Performance Tester To record web and SAP GUI transactions, install the Rational Performance Tester on any system except on the system containing the WRT agent. In our tests, we installed RPT on Windows 2008 R2 64-bit.

17 For more details on product version and maintenance levels, refer to the RPT entry in Appendix A. For more details on installing and configuring the RPT refer to the RPT entry in Appendix B. SAP GUI If you will be recording and playing back SAP R/3 transactions, you must install SAP GUI on the systems with RPT and the RRT agents. As a best practice, it is recommended to dedicate the RRT agents for SAP R/3 playback only. For more details on product version and maintenance levels, refer to the RRT entry in Appendix A. Phase 3: Introducing the resource monitoring capability This section describes the architectural overview and deployment procedures to enable the resource monitoring capability of this solution. Architectural Overview Finally, the resource monitoring can be phased in as shown in the Figure 14. It is important to note that the resource monitoring can be added at any phase of this solution. Resource agents can include OS agents to monitor the underlying operating system where the application server resides, database agents to monitor the application server data repository, and the SAP agent that monitors instance, system, Solution Manager, and Process Integrator components.

18 Figure 14: Phase 3 Resource Monitoring Resource Monitoring Component Deployment In this section, we summarize the basic installation for this capability. If applicable, special notes or nuances are explained. Operating system agent OS agents can be installed on the SAP servers. Agentless OS monitors can also be installed but do not provide as much details as non-agentless monitors. In our tests, we installed Linux agents on all of our SAP servers in our test environment. For more details on product version and maintenance levels, refer to the Linux agent entry in Appendix A. For more details on installing and configuring the Linux agent, refer to the Linux agent entry in Appendix B. Database agent The ITCAM for Applications DB2 or Oracle agent is installed to monitor the SAP databases. In our environment, we installed DB2 agents to monitor our SAP databases. For more details on product version and maintenance levels, refer to the DB2 agent entry in Appendix A.

19 For more details on installing and configuring the DB2 agent, refer to the DB2 agent entry in Appendix B. SAP agent The SAP agent can be installed on the SAP server or it can be installed on a computer system while remotely monitoring the SAP server. In the case of this solution, a single agent was installed on a Windows bit based system remotely monitoring four instances. Installing the SAP agent requires an SAP administrator to install the transport files and to perform other administrative functions. For more details on product version and maintenance levels, refer to the SAP agent entry in Appendix A. For more details on installing and configuring the SAP agent, refer to the SAP agent entry in Appendix B. Phase 4: Introducing Deep-dive Transaction Tracking This section describes the architectural overview and deployment procedures to enable the transaction tracking and J2EE monitoring capability of this solution. Architectural Overview Install the components to enable deep-dive transaction and J2EE tracking, which can help locate a root cause in an SAP J2EE-based application. Figure 15 shows these new components in orange. Netweaver data collectors have been deployed to the SAP Netweaver servers. They are configured to communicate with the transaction and J2EE agents. IA managing server is also deployed to collect data, provide services to the data collectors, and serves as a virtualization engine to view JavaTM Virtual Machine (JVM) and heap details in real-time.

20 Figure 15: Phase 4 Transaction tracking and J2EE monitoring (Deep-dive) Deep-dive Analytics Component Deployment In this section, we summarize the basic installation for this capability. If applicable, special notes or nuances are explained. Transaction Tracking Collector and Reporter agents For this solution, the transaction-tracking agents are required in the transaction tracking deep-dive phase. However, they can be used in conjunction with web response time and youcan see the basic transaction, component, application, and server topologies. For more details on product version and maintenance levels, refer to the Reporter/Collector entry in Appendix A. For more details on installing and configuring the Reporter/Collector agents, refer to the Reporter/Collector entry in Appendix B. Netweaver J2EE data collectors The data collectors collect J2EE monitoring data from the SAP server. The data collectors are installed into the SAP server, so the cdata collectorsinstallation user must have the correct authorization. The installation step is simple because it simply lays down the files. IThe configuration of the cdata collector is discussed later in this paper.

21 For more details on product version and maintenance levels, refer to the Netweaver cdata collectorentry in Appendix A. For more details on installing and configuring the Netweaver cdata collector, refer to the Netweaver Data Collectorentry in Appendix B. J2EE agent The J2EE agent works in conjunction with the data collector. The cdata collectorsends data to the agent and the agent forwards the data to the Tivoli Enterprise Management Server. The J2EE agent can be installed remotely on any computer system. For this solution test, it was installed on the same system as the AMC, RRT, and SAP agents. For more details on product version and maintenance levels, refer to the J2EE agent entry in Appendix A. For more details on installing and configuring the J2EE agent, refer to the J2EE agent entry in Appendix B. Managing Server The Netweaver data collector also works with the managing server. The cdata collectorcan be configured using the managing server, and the managing server can also display deep-dive J2EE data from the Netweaver server. The managing server requires the WebSphere server and a database like a DB2 database; you can reuse an existing WebSphere or DB2 server. In this solution test, the managing server and DB2 server were installed on the same computer system. For more details on product version and maintenance levels, refer to the Managing Server entry in Appendix A. For more details on installing and configuring the Managing Server,refer to the Managing Server entry in Appendix B.

22 Configuring Web Response Time monitoring In this section, you configure the ITCAM for Transaction components to enable agentless transaction tracking of you applications. For additional details on agentless transaction tracking, click the source link Agent-less Transaction Tracking in ITCAM for Transactions in Appendix C. For agentless monitoring using WRT, you must have a single dedicated system for the WRT agent. It is highly recommended to use the agentless configuration because the WRT agent can be resource intensive and can negatively affect the server. The following sections describe some of the prerequisite steps that you must complete to enable agentless tracking. Port mirroring The WRT agent must be installed on the same switch as the application server that is to be monitored. The switch must be configured for port mirroring. In Appendix C, click the What is Port Mirroring linkf or more details. The TCP traffic that is generated by the robotic response time agent hitting the application server wis analyzed by the WRT agent as shown in Figure 16.

23 SAP server Computer System with WRT agent Shared TCP traffic Shared TCP traffic Router RRT agent playback Switch with port mirroring Figure 16: Port Mirroring showing WRT and SAP Server as an example Enabling the network monitoring protocol on the WRT system with Windows OS For WRT agents running on a Windows OS, install the network-monitoring driver. To do this, complete the following steps: 1. Click Control Panel->Add or Remove Programs. 2. Select Add/Remove Windows Components. 3. Select Network Monitoring Protocol. Remember: This is only necessary for WRT agents running on Windows OS. Verifying WRT is capturing data in the Tivoli Enterprise Portal Server console To verify that WRT is capturing data, log into the portal server console, and navigate to the Network view in the WRT workspaces. TFigure 17 shows a workspace containing WRT data.

24 Figure 17: Network workspaces in WRT In these example workspaces, you see a summary of components, servers, and connections based like the HTTP server, DB2 server, and NetWeaver.

25 Recording and Playing Back SAP Transactions In this section, record the transactions and configure the Robotic Response time agent playback to generate TCP traffic for agentless transaction tracking. For a thorough example that outlines in detail how to record transactions and distribute the transactions to the playback agents, click the link Monitoring Applications with Rational Performance Tester and ITCAM for Response Time in Appendix C. Recording the transactions You will need to target important enterprise transactions that capture key performance and availability for your enterprise. To record transactions, use Rational Performance Tester (RPT ). For Netweaver-based application, ensure that you can log into your web application before recording. For R/3 applications, ensure that the SAP client and SAP server are SAP GUI enabled. In our solution, we recorded HTTP and SAP GUI based transactions with 5 10subtransaction steps. Setting up the playback agent Using the Application Management Configuration editor in the Tivoli Enterprise Poprtal Server console, create an RRT profile for each script. Configure each subtransaction s number of retries or response time thresholds if necessary, as shown in figure 18. Assign the playback to agents in the Distribution tab.

26 Figure 18: RRT profile in AMC editor In this view, you can edit some of the transaction defaults such as minimum and maximum response time for overall transactionsand the subtransactions. After the transactions are distributed to the agents, the each will begin to play back the transaction. In the next section, we look at defining clients, applications, and servers using the AMC.

27 Using the Application Management Console to Manage SAP Monitoring In this section, we will define server components, applications, and clients. The Application Management Console agent support provides many server components and applications that are immediatley available to use. However, in this section we discuss how to create these definitions to help you monitor the enterprise using the APM UI. Refer to the link to the ITCAM User s Guide for more information on configuring the Application Management Console. The URL is referenced in Appendix C. Define server components To identify the server components containing your business applications, you can define them in the AMC under the components menu. For example, define the protocol for the server using an IP address and port. In this example, we ve defined a Tivoli Service Request Manager server as shown in Figure 19: Figure 19: Defining a HTTP protocol in the AMC

28 Define clients To identify remote playback agents in different regions and networks, define them as client filters in the AMC. In the following example, a playback agent in Austin is defined by the IP address. Figure 20: Defining a client for RRT agent in Austin

29 Configure the Applications The AMC contains some default definitions for applications such as Siebel and SAP. Also, when you create a RRT playback profile, it automatically creates an application based on your profile as shown in the following example. Figure 21: Applications in the AMC

30 Monitoring with the SAP Agent This section describes the configuration and how the agent is used to monitor the SAP applications. Refer to the elink to the ITCAM for Applications: SAP User s Guide for more information and details. This URL is referenced in Appendix C. Instance configuration In our solution environment, a single agent remotely monitored four SAP server instances. The following figures show examples of the instance configuration windows: Figure 22: SAP agent configuration window 1

31 Figure 22: SAP agent configuration window 2 Version 7.1 of the SAP agent adds the ability to test the connection, which is extremely useful. Troubleshooting If you see that you are missing data in the workspaces, ensure that the dates, times, and time zones are synchronized between the agent, SAP servers, and Tivoli Monitoring servers. If the dates, times, and time zones are synchronized and you still do not see some data in the workspaces, refer this tech-note which helped us during our testing: Tech-note Solution Manager for SAP and Process Integrator for SAP ITCAM for Applications SAP V7.1 added new workspaces that show data from Solution Manager for SAP and Process Integrator for SAP. TFigure 23 shows the landscape and solution manager views for Solution Manager. There are more nodes available depending on what is in your Solution Manager:

32 Figure 23: Landscape Directory in the SAP agent Figure 24 shows the views for Process Integrator for SAP. Again, more nodes can be displayed depending on what is available in your SAP instance.

33 Figure 24: Process Integrator in SAP agent For more details on views, workspaces, and metrics, refer to the ITCAM for Applications: SAP User s. This URL is referenced in Appendix C.

34 Using the Application Performance User Interface In this section, we use the Application Performance Management (APM) UI to manage performance and availability of our business applications. We then configure and customize the APM UI to use the Tivoli Monitoring and ITCAM monitoring infrastructure and business application definitions covered in the previous sections. Configuring the data provider To connectthe APM UI to Tivoli Monitoring, the Common UI Rest Interface (CURI) must be enabled on the Tivoli Enterprise Management Server. In Tivoli Integrated Portal, create a connection as shown in Figure 25: Figure 25: Connection Panel in TIP The connection in the summary table should display WORKING as shown in Figure 26. Figure 26: Connection Summary in TIP

35 Launch the APM UI, and click Settings to configure the data provider. The data provider is automatically displayed in the list of available providers. Figure 27: Provider Configuration in APM UI Next, let s create an application with a dashboard. Creating an SAP application from a template Add a new application, create a name and description, select an application from the list, and select the SAP application template. For each node, select one or more resources as shown in tfigure 28:

36 Figure 28: Application Configuration Panel in APM UI Repeat this for other applications that are running in your environment. Figure 29 shows a list of SAP applications in the Application Overview.

37 Figure 29: Application Summary Dashboard Now, you can drill into each category and view the various dashboards. For instance, Figure 30 shows the resource dashboard for one of the SAP applications: Figure 30: SAP Resource Dashboard The APM UI provides basic application and resource monitoring. Now, we ll take a look at deep-dive analytics to determine relationships and deeper root cause analysis.

38 Deep-Dive Analytics using Transaction Tracking In this section, we describe how to configure and utilize the J2EE and transaction tracking features of this solution. We reference pertinent documentation and present important topics that might be crucial to this solution. Figure 31 shows the deep-dive components where the arrows represent the data flow. We use this diagram as a reference in the following sections. Figure 31: Deep-dive component data flow Transaction Collector and Reporter The reporter is the Tivoli Monitoring agent that provides the transaction topology workspaces in the Tivoli Enterprise Portal console. The reporter is configured to listen to collector agents. You can configure more than one collector agent per reporter. The collector agent receives data from data collectors such as the Netweaver Data Collector and the Web Response Time agent as shown in Figure 32. In our solution testing, we enabled transaction tracking for the WRT and pointed to the collector agent. The reporter agent was configured to listen to the collector agent. After the collector and reporter agents collect transaction-tracking data, you can see some topology data from the Web Response Time agent:

39 Figure 32: Transaction Topology in the Tivoli Enterprise Portal console For more details on configuring the transaction tracking components, refer to the ITCAM for Transactions User s Guide. Use the URL link in Appendix C. J2EE Agent As shown in figure 33, the J2EE agent receives metric data from the Netweaver Data Collector. Ensure that the workspaces in the Tivoli Enterprise Portal console contain data. If they do not, it is very likely the Data Collector is not configured or incorrectly configured to send data to the agent. For more details on configuring the J2EE agent, refer to the ITCAM for Application Diagnostics User Guide. Use the URL link in Appendix C. Managing Server After installation, the managing server listens for data collector connections. This is described in the next section. For more details on configuring the Managing Server, refer to the ITCAM for Application Diagnostics User Guide. Use the URL link in Appendix C.

40 Netweaver Data Collector Now that you ve configured the transaction topologies, the J2EE agent, and the managing server, configure the Netweaver Data Collector. For more details on configuring the Netweaver Data Collector, refer to the ITCAM for Application Diagnostics User Guide. Use the URL link in Appendix C. Here are some important points: During configuration, point the Data Collector to the collector agent, J2EE agent, and the managing server as shown in the data paths in Figure 33. You can always reconfigure the Data Collector if you do not want to enable some of these features. If the configuration tool does not detect your SAP Netweaver server, ensure that the correct maintenance level is applied to the data collector as described in Appendix A. Ensure all times, dates, and time zones are synchronized between the systems containing the SAP server, J2EE agent, transaction collector agent, and the Tivoli Monitoring core servers. The SAP server also has an internal time zone that can be configured in the SAP GUI. Make sure it also matches the system time zone. Follow the pre-configuration and post-configuration steps in the J2EE data collector Installation Guide very carefully. SAP Performance metrics must be enabled. In the Managing Server, under Administration > Monitoring on Demand, configure the monitoring level to L2 or higher. You might have to modify the toolkit_custom.properties and restart the SAP instance. Putting the deep-dive parts together After configuring transaction and application diagnostics components, the transaction tracking topology now shows some of the deep-dive elements which should be stitched the WRT data:

41 Figure 33: Transaction Topology showing JDBC nodes The J2EE agent workspaces in the Tivoli Enterprise Portal console should show data. For instance, Figure 34 shows metric data on the SAP data sources: Figure 34: J2EE Datasources workspaces

42 The managed SAP Netweaver view in the managing server user interface should provide some detailed JVM and response time data as shown in Figure 35: Figure 435: Managing Server view

43 Conclusion After you deploy this phased solution, i you twill realize significant value towards your overall application performance management strategy. You will be able to proactively detect performance and availability issues that impact the end-to-end monitoring. In phases one and two of this solution, we have seen how to deploy end-user and robotic transaction monitoring. We introduced resource monitoring in phase three and observed the powerful features of the SAP agent such as Solution Manager and Process Integrator monitoring. Finally, phase four introduced deep-dive analytics using transaction tracking and J2EE monitoring. All this lays the foundation for introducing more advanced application performance management using DevOps.

44 Appendix A: Architecture Computer Product/Release Maintenance Level OS/Arch ITCAM for Transactions Response and Transaction v7.3 GA Red Hat bit / Windows bit ITCAM for Application Diagnostics ITCAM 7.1 Netweaver Data Collector, J2EE agent, Managed Server Fixpack 4 Red Hat bit Application Performance Management User Interface APM UI v7.5 GA Red Hat bit ITCAM for Applications ITCAM for Apps 7.1 SAP GA Red Hat bit DB2 (Tivoli Monitoring & SAP) DB2 Enterprise Edition Fixpack Red Hat bit SAP Netweaver SAP NW v7.01 Red Hat bit N/A

45 Appendix B: Information Centers Sourc e URL ITCAM for Transacti ons %2Fcom.ibm.itcamt.doc_7.3%2Fic-homepage.html ITCAM for Applicati on Diagnosti cs /sap/sap_landing_user.html APM UI ITCAM for Applicati ons 101/ic-homepage.html

46 Appendix C: Additional References Source URL Application Performance Management User Interface on DeveloperWorks scapm/index.html Monitoring Applications with Rational Performance Tester and ITCAM for Response Time ng/monitoring+sap+applications+with+rational+performance+ Tester+and+ITCAM+for+Response+Time?decorator=printable Agentless Transaction Tracking in ITCAM for Transactions 587adbc f-8c adea11ed/entry/agentless_transaction_tracking_in_itcam_for_transactions_7.3? lang=en What is Port Mirroring Best Practices for Application Performance Management scapm/index.html

47 Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-ibm product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan, Ltd , Shimotsuruma, Yamato-shi Kanagawa Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-ibm websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who want to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation 2Z4A/ Burnet Road Austin, TX U.S.A.

48 Such information may be available, subject to appropriate terms and conditions, including in some cases payment of a fee. The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. If you are viewing this information softcopy, the photographs and color illustrations may not appear. Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at "Copyright and trademark information at Windows is a trademark of Microsoft Corporation in the United States, other countries, or both. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.