Persist “The Power Of Now”
                                 5 Reasons You Need History
                              to En...
SL Corporation and TIBCO Relationship

          SL has been a TIBCO alliance partner since 2002

          SL RTView was ...
Middleware Monitoring for TIBCO users
       EMS Manager            Rendezvous Monitor




       Hawk Monitor           R...
Partial TIBCO RTView Customer List
 •   A.G. Edwards               •   Harrahs                            •   R + L Carrie...
RTView for APM Architecture




5   Privileged and Confidential
RTView Historian
              RTView Historian is
              a server process
              Persists data to any
     ...
RTView Historian Data Compaction

                  Write Rules to manage history




7   Privileged and Confidential
RTView for TIBCO – EMS Manager
              An out-of-the-box
              application that is
              easy to con...
5 Reasons You Need History to Monitor EMS

                  Provisioning and Capacity Planning
                   • Littl...
5 Reasons You Need History to Monitor EMS

                   Provisioning and Capacity Planning

                   Charg...
5 Reasons You Need History to Monitor EMS

                   Provisioning and Capacity Planning

                   Charg...
5 Reasons You Need History to Monitor EMS

                   Provisioning and Capacity Planning

                   Charg...
5 Reasons You Need History to Monitor EMS

                   Provisioning and Capacity Planning

                   Charg...
RTView for APM | BW Monitor
               Dramatically speed identification
               and resolution of BusinessWork...
5 Reasons You Need History to Monitor BW

                   BW Engine Lifecycle Management
                    • Difficul...
5 Reasons You Need History to Monitor BW

                   BW Engine Lifecycle Management

                   Provisioni...
5 Reasons You Need History to Monitor BW

                   BW Engine Lifecycle Management

                   Provisioni...
5 Reasons You Need History to Monitor BW

                   BW Engine Lifecycle Management

                   Provisioni...
5 Reasons You Need History to Monitor BW

                   BW Engine Lifecycle Management

                   Provisioni...
Wrap Up

              RTView provides EMS and BusinessWorks
              users with critical historical context to:

   ...
To learn more about EMS Manager or
                          BW Monitor, please visit
                               www.s...
Upcoming SlideShare
Loading in …5
×

Persist the "Power of Now" - Five Reasons You Need History to Ensure the Performance of Your TIBCO-Based Applications

1,538 views
1,441 views

Published on

Learn how you can easily and cost-effectively provide historical context to the monitoring and troubleshooting of TIBCO EMS and TIBCO ActiveMatrix BusinessWorks, and optimize the performance of your critical TIBCO-based applications.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,538
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
35
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Persist the "Power of Now" - Five Reasons You Need History to Ensure the Performance of Your TIBCO-Based Applications

  1. 1. Persist “The Power Of Now” 5 Reasons You Need History to Ensure the Performance of Your TIBCO-Based Applications June 2010 Privileged and Confidential
  2. 2. SL Corporation and TIBCO Relationship SL has been a TIBCO alliance partner since 2002 SL RTView was added to the TIBCO price list in April 2005 A TIBCO-branded version of RTView was introduced in June 2005 Privileged and Confidential
  3. 3. Middleware Monitoring for TIBCO users EMS Manager Rendezvous Monitor Hawk Monitor RTView for APM | BW Monitor Privileged and Confidential
  4. 4. Partial TIBCO RTView Customer List • A.G. Edwards • Harrahs • R + L Carriers • Agilent • Intuit • Royal Bank of Scotland • Allstate Insurance • J.C. Penny • SAC Capital Advisors • Amgen • Laureate Education • Seagate • AT&T • Lehman • SI Mobil • Banco Azteca • LexisNexis • Smart & Final • Bank of America • Merial • Southwest Airlines • Carphone Warehouse • Mobilkom Austria • SUN International • Citigroup National • New York ISO • Telecom Italia • Citigroup Global Markets • New York Power Authority • T-Mobile • CLSA Limited • OfficeMax • Telstra • CompuCredit • OOCL • Tennessee Valley Authority • CSPI Korea • OSLO Stock Exchange • Two Sigma • Delta Technology • OTA Management • UBS • Deutsche Bank • PIT Telecommunications Indonesia • VIPnet • Dimension Data • R.L. Polk • Wachovia • Elcoteq • Payless Shoes Source Worldwide • Wells Fargo • Fujitsu Siemens • Pepsi • Grupo Elektra • Pirelli • H&R Block • Prysmian Privileged and Confidential
  5. 5. RTView for APM Architecture 5 Privileged and Confidential
  6. 6. RTView Historian RTView Historian is a server process Persists data to any SQL database Historical data can be accessed as a data source to combine with real- time data for analysis and contextual presentation Compatible with any RDBMS (Oracle, SQL Server, Sybase, DB2, etc) 6 Privileged and Confidential
  7. 7. RTView Historian Data Compaction Write Rules to manage history 7 Privileged and Confidential
  8. 8. RTView for TIBCO – EMS Manager An out-of-the-box application that is easy to configure, maintain and customize Provides views and of platform, server, transaction and message-level status Enables TIBCO EMS administrators to monitor their EMS installation to ensure it is operating optimally 8 Privileged and Confidential
  9. 9. 5 Reasons You Need History to Monitor EMS Provisioning and Capacity Planning • Little information available • Understand peak usage periods and levels 9 Privileged and Confidential
  10. 10. 5 Reasons You Need History to Monitor EMS Provisioning and Capacity Planning Chargebacks • Often don’t have statistics from an application perspective • Understanding where resources are being used facilitates better business decisions 10 Privileged and Confidential
  11. 11. 5 Reasons You Need History to Monitor EMS Provisioning and Capacity Planning Chargebacks Performance Optimization • Often vague whether it’s even necessary to look at performance optimization • Understand when the system is in stressful conditions 11 Privileged and Confidential
  12. 12. 5 Reasons You Need History to Monitor EMS Provisioning and Capacity Planning Chargebacks Performance Optimization Trusted Alerts • Hard limits for alerts creates too many false positives • Get trusted alerts on deltas based on actual behavior 12 Privileged and Confidential
  13. 13. 5 Reasons You Need History to Monitor EMS Provisioning and Capacity Planning Chargebacks Performance Optimization Trusted Alerts Failure Correlation and Analysis • Complex distributed applications very difficult to troubleshoot • Deep analysis across all metrics/servers in one centralized view is key to rapid resolution 13 Privileged and Confidential
  14. 14. RTView for APM | BW Monitor Dramatically speed identification and resolution of BusinessWorks issues by having immediate access to operational information Discover issues by observing real- time and historical throughput, and response times across multiple BW engines, servers, processes and activities in a single view Quickly look back to see when and where issues started – the BW monitor provides a centralized view of BW metrics over user-defined time intervals 14 Privileged and Confidential
  15. 15. 5 Reasons You Need History to Monitor BW BW Engine Lifecycle Management • Difficult to understand usage with multiple consumers of services provided by each BW engine • Historical metrics of usage patterns signals possible decommissioning 15 Privileged and Confidential
  16. 16. 5 Reasons You Need History to Monitor BW BW Engine Lifecycle Management Provisioning and Capacity Planning • Difficult to determine how much memory to allocate for the JVM • Historical information re: engine memory usage vs. allocated memory aids provisioning and capacity planning 16 Privileged and Confidential
  17. 17. 5 Reasons You Need History to Monitor BW BW Engine Lifecycle Management Provisioning and Capacity Planning Performance Optimization • Difficult to understand when there have been performance degradations and where issues started • Historical information key to making the right decision to resolve a degradation 17 Privileged and Confidential
  18. 18. 5 Reasons You Need History to Monitor BW BW Engine Lifecycle Management Provisioning and Capacity Planning Performance Optimization Trusted Alerts • Fixed thresholds make it difficult to track performance times • Understand performance by comparing real-time data to a “normal” time-based bandwidth 18 Privileged and Confidential
  19. 19. 5 Reasons You Need History to Monitor BW BW Engine Lifecycle Management Provisioning and Capacity Planning Performance Optimization Trusted Alerts Failure Correlation and Analysis • Looking at log files and correlating the information is tedious, and too slow for troubleshooting • Historical views across multiple BW engines provides all information in a single console 19 Privileged and Confidential
  20. 20. Wrap Up RTView provides EMS and BusinessWorks users with critical historical context to: Know when systems are operating under stressful conditions, and for how long Understand peak usage periods and levels in order to provide more accurate provisioning and capacity planning Understand what resources are being used/not used Provide trusted alerts based on more realistic behavior Correlate information across multiple EMS servers or BW engines Provide deep analysis and better problem resolution 20 Privileged and Confidential
  21. 21. To learn more about EMS Manager or BW Monitor, please visit www.sl.com - or - contact SL Corporation at (415) 927-8400 Privileged and Confidential

×