RTI Quick Start Guide

Transcription

1 RTI Quick Start Guide This is the RTI Quick Start guide for new users or evaluators. It will help you get RTI installed and collecting data on your application quickly in an environment where you develop or test JBoss enterprise applications. Note If you are going to be integrating RTI with JBoss Operations Network 3.x or newer, or RHQ 4.x or newer, please see the RTI Quick Start Guide for JBoss Operation Network Users instead. The steps that you'll follow are: 1. Download and Install the RTI Console and RTI performance collectors. 2. Enable RTI performance collection on each application. 3. Profile your application by capturing the data RTI is collecting as you test your applications. 4. Deep Dive to determine exactly when, where and why your application was slow or resource-intensive. The diagram below shows how the RTI collectors and console fit into your enterprise application architecture. For full details and further information see the RTI User Guide. RTI-Enhanced Enterprise Architecture 1

2 1. INSTALL Install RTI Components and prepare for monitoring. Download RTI Components 1. Visit rtiperformance.com/download to request a download. In reply you will receive an explaining how to download each component. 2. Download Linux and/or Windows RTI performance collectors. 3. Download Linux, Mac or Windows RTI console application. Install RTI performance collectors. 1. Windows: Run the rti-enterprise win32-*.exe self-installer. 2. Linux: execute the installer with bash: sh rti-enterprise lx86-*.sh 3. See the user's guide for more information. Install RTI Console on your Desktop 1. Windows: Run the rti-console win32-*.exe self-installer 2. Mac: a. Unarchive the downloaded rti-console macosx86_64-*.tgz file. b. Open (run) the RTIEEConsole64/RTIAnalyzer application. 3. Linux: a. Unpack the tarball to create the RTIEE64Console directory: tar -zxf rti-console lx86_64-*.tgz b. Update path to include RTIEEConsole64, for example: export PATH=/opt/RTIEEConsole64:${PATH} c. Launch RTI with the RTIAnalyzer command, for example: /opt/rtieeconsole64/rtianalyzer 4. See the user's guide for more information. 2

3 2. ENABLE Finish Installation by enabling your JBoss, Tomcat or Fuse instance to be monitored by RTI. Before, during and after checklist. BEFORE - You must have already installed RTI Performance Collectors on your Linux or Windows Platforms. DURING - Your user has permissions to edit the JBoss, Tomcat or Fuse startup scripts and enable RTI performance monitoring. AFTER - Restart your RTI-monitored applications after installation and script-editing. Enable your JBoss, Tomcat or Fuse application for RTI Performance Monitoring 1. Open a shell or CMD window and "source" the RTI environment: Linux: Source the RTI setup env, for example:. ${RTI_HOME}/setup # notice dot, space Windows: Open an RTI CMD Window with Start>All Programs>RTI>RTI Enterprise Cmd. 2. Enable the JBoss, Tomcat or Fuse instance for monitoring with "rti edit", for example: rti edit -t jboss /opt/jboss-soa-p-5/jboss-as rti edit -t tomcat c:\apache-tomcat rti edit -t fuse /opt/jboss-fuse redhat-024 Note If you run JBoss domain mode or use a service wrapper to start your application server, you cannot use rti edit: See the user's guide for more information. 3. Start or restart JBoss, Tomcat or Fuse: RTI is now enabled and monitoring performance! 4. See the user's guide for more information. Connect the Console to Collectors 1. Start the RTI Console and select Connect to RTI Performance Collectors. 2. Enter login information for the remote host; click the Test button to verify the connection, then click Finish. 3. Verify the remote host appears in the RTI Console Collectors view; you can expand each host to see the running processes for each, if any. 4. See the user's guide for more information. 3

4 2. ENABLE 4

5 3. PROFILE Transaction profiling is the lightweight solution to analyze and diagnose the performance of your applications. With less than 2% overhead transaction profiling gives you 24/7 always on performance visibility, to show where your application is spending time. View transaction profiles Transaction profiling is available out of the box for Java applications such as JBoss, Tomcat and Fuse: 1. Select View Transaction Profile Snapshots. 2. Choose an application to profile. 3. See the call profile summary tree, sorted by the average business transaction time. 4. See the user's guide for more information. 5

6 3. PROFILE Analyze and identify problem transactions 1. Analyze business transactions, response times, counts and total times to identify the expensive transactions. 2. Decompose transaction call stack to identify bottlenecks at the method level. 6

7 4. DEEP DIVE Trace problem transactions across platforms and JVMs, pinpoint problems to the method level and see context. Enable Deep Dive for problem transactions 1. From a Call Profile Snapshot, select one or more problem transactions for Deep Dive 2. Choose which transactions to trace and for how long, then Start Trace. 3. Exercise your application as RTI applies deep dive performance monitoring. 4. See the user's guide for more information. Collect the data 1. Deep Dive data is logged locally to the applications monitored; gather for analysis across one or more performance collectors. 2. Download data from the collector(s) in the time range that you traced. 3. See the user's guide for more information. 7

8 4. DEEP DIVE Analyze the data 1. Use the Event Summary to get an overview of transactions and metrics collected. 2. Use the Transaction Chart to focus on peaks of Transaction time to see when it was slow. 8

9 4. DEEP DIVE 3. Filter, plot and drill down into specific Transactions in the Transaction tree to see what was slow. 9

10 4. DEEP DIVE 4. Use GC and JMX Charts and Metrics to understand why the app was slow. The GC and JMX charts below are shown "maximized" which can be achieved for any view by clicking the icon in the upper right of its frame. 5. See the user's guide for more information. 10

11 5. FAQ Frequently Asked Questions I have a question That s what we re here for. We take support seriously, us anytime at rti_support@ocsystems.com. What are the prerequisites for RTI? RTI can monitor any JBoss 4+. Tomcat 5+ or Fuse 6+ instance running Java 1.5+ on 32 or 64-bit Windows or Linux, and the RTI Console runs on Windows, Mac and Linux Desktops. A full list of prerequisites is available at rtiperformance.com/documentation. What can RTI monitor other than JBoss? RTI supports many performance collectors including: End-User Experience (IE / Firefox), test automation (JMeter, SoapUI), Apache Tomcat and JBoss Application Servers, and Fuse ESB. What is the overhead of running RTI? About 2% CPU overhead for transaction profiling, we recommend using this 24/7. Deep Dive is more depending on transaction load and application complexity, typically between 5->10%. How do I measure End-User Experience, JMeter or SoapUI transactions? This quick-start guide covers the most common scenario, full documentation and helpful videos are available at rtiperformance.com/documentation. Do you support WebSphere, WebLogic or other Application Servers? Not now, we are focused on being the best performance monitoring solution for Red Hat enterprise components. How much does RTI cost? RTI is licensed annually as a subscription, based on the number of JBoss/Tomcat/Fuse CPU cores to be monitored. See rtiperformance.com/pricing for more information. 11