Download AutoPilot® TransactionWorks® Transaction Analyzer

TWORKS/TA 655.001
AutoPilot TransactionWorks
Transaction Analyzer
Version 6.5.5
Installation and User’s Guide
CONFIDENTIALITY STATEMENT: THE INFORMATION WITHIN THIS MEDIA IS PROPRIETARY IN NATURE AND IS THE SOLE PROPERTY OF
NASTEL TECHNOLOGIES, INC. ALL PRODUCTS AND INFORMATION DEVELOPED BY NASTEL ARE INTENDED FOR LIMITED DISTRIBUTION
TO AUTHORIZED NASTEL EMPLOYEES, LICENSED CLIENTS, AND AUTHORIZED USERS. THIS INFORMATION (INCLUDING SOFTWARE,
ELECTRONIC AND PRINTED MEDIA) IS NOT TO BE COPIED OR DISTRIBUTED IN ANY FORM WITHOUT THE EXPRESSED WRITTEN PERMISSION
FROM NASTEL TECHNOLOGIES, INC.
© 1998-2016 Nastel Technologies, Inc. All rights reserved.
PUBLISHED BY:
RESEARCH & DEVELOPMENT
NASTEL TECHNOLOGIES, INC.
48 SOUTH SERVICE ROAD, SUITE 205
MELVILLE, NY 11747
COPYRIGHT © 1998-2016. ALL RIGHTS RESERVED. NO PART OF THE CONTENTS OF THIS DOCUMENT MAY
BE PRODUCED OR TRANSMITTED IN ANY FORM, OR BY ANY MEANS WITHOUT THE WRITTEN PERMISSION OF
NASTEL TECHNOLOGIES.
DOCUMENT TITLE: AUTOPILOT TRANSACTIONWORKS TRANSACTION ANALYZER INSTALLATION AND
USER’S GUIDE
VERSION: 6.5.5
DOCUMENT RELEASE DATE: DECEMBER 2016
NASTEL DOCUMENT NUMBER: TWORKS/TA 655.001
CONFIDENTIALITY STATEMENT: THE INFORMATION WITHIN THIS MEDIA IS PROPRIETARY IN NATURE AND IS THE
SOLE PROPERTY OF NASTEL TECHNOLOGIES, INC. ALL PRODUCTS AND INFORMATION DEVELOPED BY NASTEL ARE
INTENDED FOR LIMITED DISTRIBUTION TO AUTHORIZED NASTEL EMPLOYEES, LICENSED CLIENTS, AND AUTHORIZED
USERS. THIS INFORMATION (INCLUDING SOFTWARE, ELECTRONIC AND PRINTED MEDIA) IS NOT TO BE COPIED OR
DISTRIBUTED IN ANY FORM WITHOUT THE EXPRESSED WRITTEN PERMISSION FROM NASTEL TECHNOLOGIES, INC.
ACKNOWLEDGEMENTS:
THE FOLLOWING TERMS ARE TRADEMARKS OF NASTEL TECHNOLOGIES CORPORATION IN THE UNITED STATES OR OTHER COUNTRIES
OR BOTH: TRANSACTIONWORKS, AUTOPILOT M6, AUTOPILOT/IT, AUTOPILOT M6 FOR WMQ, AUTOPILOT/WMQ, M6 WEB
SERVER, AUTOPILOT/WEB, M6 WEB CONSOLE, MQCONTROL, MQCONTROL EXPRESS, AUTOPILOT/TRANSACTION MONITOR,
AUTOPILOT/WAS, AUTOPILOT/OS MONITOR
THE FOLLOWING TERMS ARE TRADEMARKS OF THE IBM CORPORATION IN THE UNITED STATES OR OTHER COUNTRIES OR BOTH: IBM,
MQ, MQSERIES, WEBSPHERE, WEBSPHERE MQ WIN-OS/2, AS/400, OS/2, DB2, AND AIX, Z/OS
THE FOLLOWING TERMS ARE TRADEMARKS OF HEWLETT-PACKARD IN THE UNITED STATES OR OTHER COUNTRIES OR BOTH:
OPENVIEW, HP-UX
COMPAQ, THE COMPAQ LOGO, ALPHASERVER, COMPAQ INSIGHT MANAGER, CDA, DEC, DECNET, TRUCLUSTER, ULTRIX, AND
VAX REGISTERED IN U.S. PATENT AND TRADEMARK OFFICE. ALPHA AND TRU64 ARE TRADEMARKS OF COMPAQ INFORMATION
TECHNOLOGIES GROUP, L.P IN THE UNITED STATES AND OTHER COUNTRIES
SNMPC, SNMPC, WORKGROUP, AND SNMPC ENTERPRISE ARE TRADEMARKS OF CASTLE ROCK COMPUTING IN THE UNITED STATES
OR OTHER COUNTRIES, OR BOTH.
SUN, SUN MICROSYSTEMS, THE SUN LOGO, IFORCE, JAVA, NETRA, N1, SOLARIS, SUN FIRE, SUN RAY, SUNSPECTRUM, SUN
STOREDGE, SUNTONE, THE NETWORK IS THE COMPUTER, ALL TRADEMARKS AND LOGOS THAT CONTAIN SUN, SOLARIS, OR JAVA, AND
CERTAIN OTHER TRADEMARKS AND LOGOS ARE TRADEMARKS OR REGISTERED TRADEMARKS OF SUN MICROSYSTEMS, INC. IN THE
UNITED STATES AND OTHER COUNTRIES.
INSTALLANYWHERE IS A REGISTERED TRADEMARK OF ZEROG SOFTWARE IN THE UNITED STATES OR OTHER COUNTRIES, OR BOTH.
THIS PRODUCT INCLUDES SOFTWARE DEVELOPED BY THE APACHE SOFTWARE FOUNDATION (HTTP://WWW.APACHE.ORG/). THE
JAKARTA PROJECT" AND "TOMCAT" AND THE ASSOCIATED LOGOS ARE REGISTERED TRADEMARKS OF THE APACHE SOFTWARE
FOUNDATION
INTEL, PENTIUM AND INTEL486 ARE TRADEMARKS OR REGISTERED TRADEMARKS OF INTEL CORPORATION IN THE UNITED STATES, OR
OTHER COUNTRIES, OR BOTH
MICROSOFT, WINDOWS, WINDOWS NT, WINDOWS XP, AND THE WINDOWS LOGOS ARE REGISTERED TRADEMARKS OF THE MICROSOFT
CORPORATION.
UNIX IS A REGISTERED TRADEMARK IN THE UNITED STATES AND OTHER COUNTRIES LICENSED EXCLUSIVELY THROUGH X/OPEN
COMPANY LIMITED.
"LINUX" AND THE LINUX LOGOS ARE REGISTERED TRADEMARKS OF LINUS TORVALDS, THE ORIGINAL AUTHOR OF THE LINUX KERNEL.
ALL OTHER TITLES, APPLICATIONS, PRODUCTS, AND SO FORTH ARE COPYRIGHTED AND/OR TRADEMARKED BY THEIR RESPECTIVE
AUTHORS.
SCO CUSA, SCO DOCTOR, SCO DOCTOR FOR NETWORKS, SCO DOCTOR LITE, SCO GLOBAL ACCESS, SCO MPX, SCO
MULTIVIEW, SCO NIHONGO OPENSERVER, SCO OK, THE SCO OK LOGO, SCO OPENSERVER, SCO OPEN SERVER, SCO PORTFOLIO,
SCO POS SYSTEM, SCO TOOLWARE, AND THE WORLD NEVER STOPS ARE TRADEMARKS OR REGISTERED TRADEMARKS OF CALDERA
INTERNATIONAL, INC. IN THE U.S.A. AND OTHER COUNTRIES, ALL RIGHTS RESERVED.
ORACLE® IS A REGISTERED TRADEMARK OF ORACLE CORPORATION AND/OR ITS AFFILIATES
OTHER COMPANY, PRODUCT, AND SERVICE NAMES, MAY BE TRADEMARKS OR SERVICE MARKS OF OTHERS.
© 1998-2016 Nastel Technologies, Inc.
A
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Table of Contents
Contents
CHAPTER 1: INTRODUCTION .............................................................................................................................. 1
1.1
HOW THIS GUIDE IS ORGANIZED .................................................................................................................. 1
1.2
HISTORY OF THIS DOCUMENT ...................................................................................................................... 1
1.3
RELATED DOCUMENTS ................................................................................................................................. 2
1.4
RELEASE NOTES ........................................................................................................................................... 2
1.5
INTENDED AUDIENCE ................................................................................................................................... 2
1.5.1 User Feedback ......................................................................................................................................... 2
1.6
SYSTEM REQUIREMENTS............................................................................................................................... 3
1.7
TECHNICAL SUPPORT .................................................................................................................................... 3
1.8
TERMS AND ABBREVIATIONS ........................................................................................................................ 3
1.9
CONVENTIONS .............................................................................................................................................. 3
CHAPTER 2: ABOUT TRANSACTION ANALYZER .......................................................................................... 5
2.1
2.2
2.3
AUTOPILOT TRANSACTIONWORKS/TRANSACTION ANALYZER FEATURES ................................................... 5
AUTOPILOT TRANSACTIONWORKS ARCHITECTURE ..................................................................................... 5
AUTOPILOT TRANSACTIONWORKS DEFINITIONS.......................................................................................... 7
CHAPTER 3: INSTALLATION ................................................................................................................................ 9
3.1
BEFORE INSTALLATION ................................................................................................................................ 9
3.1.1 Technical Documents............................................................................................................................... 9
3.1.2 Installation Requirements ........................................................................................................................ 9
3.1.3 Contents of AutoPilot TransactionWorks Distribution ............................................................................ 9
3.2
INSTALLING THE TRANSACTION ANALYZER AS AUTOPILOT EXPERT ......................................................... 10
CHAPTER 4: CONFIGURATION.......................................................................................................................... 13
4.1
TRANSACTIONWORKS DATABASE .............................................................................................................. 13
4.1.1 JDBC and ODBC Drivers ..................................................................................................................... 13
4.1.2 TransactionWorks Database Administration ......................................................................................... 14
4.1.2.1
4.1.2.2
4.1.2.3
4.1.2.4
4.1.2.5
Creating the Database ................................................................................................................................... 15
Updating the Database .................................................................................................................................. 15
Loading Database Stored Procedures ............................................................................................................ 16
Optimizing Tables and Indexes ..................................................................................................................... 16
Oracle Database Permissions ........................................................................................................................ 16
4.2
TRANSACTION MONITOR OPTIMIZATION .................................................................................................... 18
4.2.1 Memory Optimization ............................................................................................................................ 19
4.2.2 CPU Optimization ................................................................................................................................. 20
4.2.3 SQL Database Optimization .................................................................................................................. 21
CHAPTER 5: USING AUTOPILOT TRANSACTIONWORKS/ TRANSACTION ANALYZER................... 23
5.1
DEPLOYING TRANSACTION ANALYZER EXPERT ......................................................................................... 23
CHAPTER 6: TRANSACTION ANALYZER METRICS .................................................................................... 45
6.1
ANALYZERSTATS........................................................................................................................................ 45
6.2
DBSTATS .................................................................................................................................................... 49
6.3
HOPSTATS .................................................................................................................................................. 50
6.4
PROBESTATS............................................................................................................................................... 53
6.5
TRACKING .................................................................................................................................................. 58
6.5.1 Tracking Violation ................................................................................................................................. 59
6.6
TRANSACTIONSTATS .................................................................................................................................. 62
CHAPTER 7: DATABASE CONFIGURATION ................................................................................................... 65
7.1
DATABASE CONFIGURATION TABLES ........................................................................................................ 65
7.1.1 Reference Tables.................................................................................................................................... 65
7.1.1.1
7.1.1.2
7.1.1.3
7.1.1.4
Message Formats........................................................................................................................................... 65
Message Types .............................................................................................................................................. 66
Transport Types ............................................................................................................................................ 67
Logical Unit of Work (LUW) Types ............................................................................................................. 67
TWORKS/TA 655.001
i
© 1998-2016 Nastel Technologies, Inc.
Table of Contents
7.1.1.5
7.1.1.6
7.1.1.7
7.1.1.8
7.1.1.9
7.1.1.10
7.1.1.11
7.1.1.12
7.1.2
Servers .......................................................................................................................................................... 72
Client Users .................................................................................................................................................. 72
Applications .................................................................................................................................................. 73
Resource Managers ....................................................................................................................................... 73
Logical Units of Work (LUW) ...................................................................................................................... 74
Messages ....................................................................................................................................................... 74
Properties ...................................................................................................................................................... 76
Transaction Group Definitions...................................................................................................................... 76
Transaction Milestones ................................................................................................................................. 77
Transaction Group Milestones ...................................................................................................................... 77
Transaction Correlators ................................................................................................................................. 77
Transaction Search Tags ............................................................................................................................... 78
Analysis Tables ......................................................................................................................................78
7.1.3.1
7.1.3.2
7.1.3.3
7.1.3.4
7.1.3.5
7.1.3.6
7.1.3.7
7.1.3.8
7.1.3.9
7.1.3.10
7.1.3.11
7.1.4
Logical Unit of Work (LUW) Statuses ......................................................................................................... 67
API Operation Types .................................................................................................................................... 68
Resource Manager Types .............................................................................................................................. 68
Resource Types ............................................................................................................................................. 69
Property Types .............................................................................................................................................. 70
Transaction Status Types .............................................................................................................................. 70
Completion Code Types ............................................................................................................................... 70
Operation Severity Levels ............................................................................................................................. 71
Data Tables ............................................................................................................................................72
7.1.2.1
7.1.2.2
7.1.2.3
7.1.2.4
7.1.2.5
7.1.2.6
7.1.2.8
7.1.2.9
7.1.2.10
7.1.2.11
7.1.2.12
7.1.2.13
7.1.3
AutoPilot TransactionWorks TA
Analysis Info ................................................................................................................................................. 78
Transaction Members.................................................................................................................................... 78
Tagged Transaction Groups .......................................................................................................................... 79
Transaction Metrics ...................................................................................................................................... 79
Transaction Applications .............................................................................................................................. 80
Transaction Users ......................................................................................................................................... 80
Transaction Resource Managers ................................................................................................................... 80
Transaction Resources .................................................................................................................................. 80
Transaction Logical Units of Work (LUW) .................................................................................................. 81
Transaction Messages ................................................................................................................................... 81
Tagged Transaction Milestones .................................................................................................................... 81
Administration Tables ............................................................................................................................82
7.1.4.1
7.1.4.2
Database Schema Version ............................................................................................................................. 82
Database Schema Update History ................................................................................................................. 82
CHAPTER 8: MAINTAINING COLLECTED DATA ..........................................................................................83
8.1
HOW MUCH DATA TO KEEP ........................................................................................................................83
8.2
PURGING DATA ...........................................................................................................................................83
8.2.1 Sample Purge Usage ..............................................................................................................................84
8.3
TROUBLESHOOTING ....................................................................................................................................85
8.3.1 Incomplete Purge ...................................................................................................................................85
8.3.2 Out of Space ...........................................................................................................................................85
APPENDIX A: REFERENCES ................................................................................................................................87
A.1
A.2
NASTEL DOCUMENTATION ..........................................................................................................................87
OTHER DOCUMENTATION ...........................................................................................................................87
APPENDIX B: CONVENTIONS .............................................................................................................................89
B.1
TYPOGRAPHICAL CONVENTIONS .................................................................................................................89
GLOSSARY ...............................................................................................................................................................91
INDEX ........................................................................................................................................................................97
© 1998-2016 Nastel Technologies, Inc.
ii
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Table of Contents
Figures
FIGURE 2-1. AUTOPILOT M6/TRANSACTIONWORKS ARCHITECTURE ........................................................ 6
FIGURE 3-1. TA FILE PATH INPUT SCREEN ...................................................................................................... 10
FIGURE 3-2. DETAIL OF INSTALLED LIBRARY LIST ...................................................................................... 11
FIGURE 4-1. GRANTED PRIVILEGE ..................................................................................................................... 16
FIGURE 4-2. OBJECT PRIVILEGES ....................................................................................................................... 17
FIGURE 5-1. VERIFY INSTALLATION ................................................................................................................. 23
FIGURE 5-2. DEPLOY TA EXPERT ....................................................................................................................... 23
FIGURE 5-3. TA EXPERT: GENERAL ................................................................................................................... 24
FIGURE 5-4. TA EXPERT: ABOUT ........................................................................................................................ 24
FIGURE 5-5. TA EXPERT: ANALYSIS .................................................................................................................. 25
FIGURE 5-6. TA EXPERT: DATABASE ................................................................................................................. 26
FIGURE 5-7. TA EXPERT: DATABASE – PAYLOADS........................................................................................ 27
FIGURE 5-8. TA EXPERT:: DEPENDENCIES ....................................................................................................... 28
FIGURE 5-9. TA EXPERT: FACT OPTIONS .......................................................................................................... 29
FIGURE 5-10. TA EXPERT: HTTP OPTIONS ........................................................................................................ 30
FIGURE 5-11. TA EXPERT: LOGGING .................................................................................................................. 31
FIGURE 5-12. TA EXPERT: MESSAGE PROCESSING ........................................................................................ 32
FIGURE 5-12A. TA EXPERT: MESSAGE PROCESSING-SUPRESSION ............................................................ 33
FIGURE 5-13. TA EXPERT: RECORDING ............................................................................................................. 34
FIGURE 5-14. TA EXPERT: RESTART-RECOVERY............................................................................................ 35
FIGURE 5-15. TA EXPERT: SECURITY ................................................................................................................ 36
FIGURE 5-16. TA EXPERT: STATISTICS - GENERAL ........................................................................................ 37
FIGURE 5-17. TA EXPERT: STATISTICS – HOPS ................................................................................................ 38
FIGURE 5-18. TA EXPERT: STATISTICS – PROBE ............................................................................................. 39
FIGURE 5-19. TA EXPERT: TCP OPTIONS ........................................................................................................... 39
FIGURE 5-19A. TA EXPERT: TNT LOGGING ...................................................................................................... 40
FIGURE 5-20. TA EXPERT: TRACE LOGGING .................................................................................................... 41
FIGURE 5-21. TA EXPERT: TRACKING ............................................................................................................... 42
FIGURE 5-22. TA SERVICE DEPLOYED .............................................................................................................. 43
FIGURE 5-23. DEPLOY EXPERT ON MULTIPLE NODES .................................................................................. 43
FIGURE 5-24. DEPLOYED TA EXPERT ................................................................................................................ 43
FIGURE 6-1. TRANSACTION ANALYZER ANALYZERSTATS METRICS ...................................................... 45
FIGURE 6-2. TRANSACTION ANALYZER DBSTATS METRICS ...................................................................... 49
FIGURE 6-3. TRANSACTION ANALYZER HOPSTATS METRICS.................................................................... 50
FIGURE 6-4. TRANSACTION ANALYZER PROBESTATS METRICS ............................................................... 53
FIGURE 6-5. TRANSACTION ANALYZER PROBESTATS/MESSAGE PAYLOADS ....................................... 56
FIGURE 6-6. TRANSACTION ANALYZER TRACKING METRICS ................................................................... 58
FIGURE 6-7. TRANSACTION ANALYZER TRACKING VIOLATION METRICS ............................................ 59
FIGURE 6-8. TRANSACTIONSTATS METRICS ................................................................................................... 63
TWORKS/TA 655.001
iii
© 1998-2016 Nastel Technologies, Inc.
Table of Contents
AutoPilot TransactionWorks TA
Tables
TABLE 1-1. DOCUMENT HISTORY ....................................................................................................................... 1
TABLE 4-1. SUPPORTED DATABASES AND CORRESPONDING JDBC DRIVERS .......................................13
TABLE 5-1. TA EXPERT: GENERAL .....................................................................................................................24
TABLE 5-2. TA EXPERT: ABOUT ...........................................................................................................................24
TABLE 5-3. TA EXPERT: ANALYSIS ....................................................................................................................25
TABLE 5-4. TA EXPERT: DATABASE...................................................................................................................26
TABLE 5-5. TA EXPERT: DATABASE – PAYLOADS .........................................................................................28
TABLE 5-6. TA EXPERT: DEPENDENCIES ..........................................................................................................28
TABLE 5-7. TA EXPERT: FACT OPTIONS ............................................................................................................29
TABLE 5-8. TA EXPERT: HTTP OPTIONS ............................................................................................................30
TABLE 5-9. TA EXPERT: LOGGING......................................................................................................................31
TABLE 5-9A. TA EXPERT: MESSAGE PROCESSING .........................................................................................32
TABLE 5-9B. TA EXPERT: MESSAGE PROCESSING-SUPRESSION ................................................................33
TABLE 5-10. TA EXPERT: RECORDING...............................................................................................................34
TABLE 5-11. TA EXPERT: RESTART-RECOVERY .............................................................................................35
TABLE 5-12. TA EXPERT: SECURITY ..................................................................................................................36
TABLE 5-13. TA EXPERT: STATISTICS - GENERAL ..........................................................................................37
TABLE 5-14. TA EXPERT: STATISTICS - HOPS ..................................................................................................38
TABLE 5-15. TA EXPERT: STATISTICS - PROBE................................................................................................39
TABLE 5-16. TA EXPERT: TCP OPTIONS .............................................................................................................40
TABLE 5-16A. TA EXPERT: TNT LOGGING ........................................................................................................40
TABLE 5-17. TA EXPERT: TRACE LOGGING ......................................................................................................41
TABLE 5-18. TA EXPERT: TRACKING .................................................................................................................42
TABLE 6-1. FACTS PUBLISHED BY TA: ANALYZERSTATS ...........................................................................46
TABLE 6-2. FACTS PUBLISHED BY TA: DBSTATS ...........................................................................................49
TABLE 6-3. FACTS PUBLISHED BY TA: HOPSTATS/MSG_STATS .................................................................51
TABLE 6-4. FACTS PUBLISHED BY TA: HOPSTATS/OPR_STATS ..................................................................51
TABLE 6-5. FACTS PUBLISHED BY TA: HOPSTATS/OPR_SUMMARY ..........................................................52
TABLE 6-6. FACTS PUBLISHED BY TA: HOPSTATS GENERIC .......................................................................52
TABLE 6-7. FACTS PUBLISHED BY TA: PROBESTATS .....................................................................................54
TABLE 6-8. PROBE-SPECIFIC FACTS PUBLISHED BY TA: PROBESTATS/MESSAGEPAYLOADS ...........56
TABLE 6-9. FACTS PUBLISHED BY TA: TRACKING VIOLATION ..................................................................60
TABLE 6-10. FACTS PUBLISHED BY TA: TRACKING VIOLATION – TRANSACTION GROUP .................60
TABLE 6-11. FACTS PUBLISHED BY TA: TRACKING VIOLATION – TRANSACTION GROUP –
MILESTONE ......................................................................................................................................................61
TABLE 6-12. FACTS PUBLISHED BY TA: TRANSACTIONSTATS ...................................................................64
TABLE 7-1. DATA DEFINITION OF REFERENCE TABLES ...............................................................................65
TABLE 7-2. REF_MSG_FORMATS ........................................................................................................................65
TABLE 7-3. REF_MSG_TYPES ...............................................................................................................................66
TABLE 7-4. REF_TRANSPORT_TYPES.................................................................................................................67
TABLE 7-5. REF_LUW_TYPES ...............................................................................................................................67
TABLE 7-6. REF_LUW_STATUSES .......................................................................................................................67
TABLE 7-7. REF_API_TYPES .................................................................................................................................68
TABLE 7-8. REF_RES_MGR_TYPES .....................................................................................................................68
TABLE 7-9. REF_RES_TYPES ................................................................................................................................69
TABLE 7-10. REF_PROPERTY_TYPES .................................................................................................................70
TABLE 7-11. REF_TRAN_STATUS_TYPES ..........................................................................................................70
TABLE 7-12. REF_OP_COMPLETION_CODES ....................................................................................................70
TABLE 7-13. REF_OPERATION_SEVERITIES .....................................................................................................71
TABLE 7-14. DATA DEFINITION OF TW_SERVERS ..........................................................................................72
TABLE 7-15. DATA DEFINITION OF TW_CLIENT_USERS ...............................................................................72
TABLE 7-16. DATA DEFINITION OF TW_APPLICATIONS ...............................................................................73
TABLE 7-17. DATA DEFINITION OF TW_RESOURCE_MGRS .........................................................................73
TABLE 7-18. DATA DEFINITION OF TW_LOGICAL_UNIT_WORK ................................................................74
TABLE 7-19. DATA DEFINITION OF TW_MESSAGES .......................................................................................74
TABLE 7-20. DATA DEFINITION OF TW_OPERATIONS ...................................................................................75
TABLE 7-21. DATA DEFINITION OF TW_PROPERTIES ....................................................................................76
© 1998-2016 Nastel Technologies, Inc.
iv
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Table of Contents
TABLE 7-22. DATA DEFINITION OF TW_TRAN_GROUPS............................................................................... 76
TABLE 7-23. DATA DEFINITION OF TW_MILESTONES .................................................................................. 77
TABLE 7-24. DATA DEFINITION OF TW_TRANSACTION_ANALYSIS_FILTER .......................................... 77
TABLE 7-25. DATA DEFINITION OF TW_TRAN_CORRELATORS .................................................................. 77
TABLE 7-26. DATA DEFINITION OF TW_TRAN_SEARCH_TAGS .................................................................. 78
TABLE 7-27. DATA DEFINITION OF TW_ANALYSIS_INFO ............................................................................ 78
TABLE 7-28. DATA DEFINITION OF TW_TRAN_MEMBERS ........................................................................... 78
TABLE 7-29. DATA DEFINITION OF TW_TAGGED_TRAN_GROUPS ............................................................ 79
TABLE 7-30. DATA DEFINITION OF TW_TRANSACTIONS ............................................................................. 79
TABLE 7-31. DATA DEFINITION OF TW_TRAN_APPLICATIONS .................................................................. 80
TABLE 7-32. DATA DEFINITION OF TW_TRAN_USERS .................................................................................. 80
TABLE 7-33. DATA DEFINITION OF TW_TRAN_RESOURCE_MGRS ............................................................ 80
TABLE 7-34. DATA DEFINITION OF TW_TRAN_RESOURCES ....................................................................... 80
TABLE 7-35. DATA DEFINITION OF TW_TRAN_LUWS ................................................................................... 81
TABLE 7-36. DATA DEFINITION OF TW_TRAN_MSGS.................................................................................... 81
TABLE 7-37. DATA DEFINITION OF TW_TAGGED_TRAN_MILESTONES ................................................... 81
TABLE 7-38. DATA DEFINITION OF TWADM_VERSION ................................................................................. 82
TABLE 7-39. DATA DEFINITION OF TWADM_UPDATE_HISTORY ............................................................... 82
TABLE A-1. NASTEL DOCUMENTATION ........................................................................................................... 87
TABLE B-1. TYPOGRAPHICAL CONVENTIONS ................................................................................................ 89
TWORKS/TA 655.001
v
© 1998-2016 Nastel Technologies, Inc.
Table of Contents
AutoPilot TransactionWorks TA
This page intentionally left blank.
© 1998-2016 Nastel Technologies, Inc.
vi
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 1: Introduction
Chapter 1: Introduction
Welcome to the Nastel AutoPilot TransactionWorks Transaction Analyzer Installation and User’s Guide.
This guide describes deploying, database configuration, and use of the Transaction Analyzer (TA).
Please review this guide carefully before using the product.
1.1 How This Guide is Organized
Chapter 1:
Identifies the users and history of the document. System requirements are outlined in
addition to supplying support and reference information.
Chapter 2:
Contains a functional description of the AutoPilot TransactionWorks TA.
Chapter 3:
Provides instructions for new installations of the AutoPilot TransactionWorks TA.
Chapter 4:
Provides instructions for configuring and optimizing the TA expert.
Chapter 5:
Provides instructions for deploying the TA expert.
Chapter 6:
Defines the TA metrics.
Chapter 7:
Outlines the TA database configuration.
Chapter 8:
Provides information for purging data.
Appendix A: Provides a list of reference information for using the AutoPilot TransactionWorks TA.
Appendix B: Contains conventions used in this document.
Glossary:
Contains a listing of unique and common acronyms and words and their definition.
Index:
Contains an alphanumeric cross-reference of all topics and subjects of importance.
1.2 History of This Document
Table 1-1. Document History
Release Date
Document Number
AutoPilot
TransactionWorks
Version
Summary
March 2009
TWORKS/TA 600.001
6.0
Initial release
April 2009
TWORKS/TA 600.002
6.0.3
Errata
April 2009
TWORKS/TA 600.003
6.0.4
Changes to Transaction Analyzer
properties
May 2009
TWORKS/TA 600.004
6.0.5
Update program version number
July 2009
TWORKS/TA 600.005
6.0.6
Added Hop Statistics
August 2009
TWORKS/TA 600.006
6.0.7
Enable/disable writing of probe transaction
data to the database, interface updates
August 2009
TWORKS/TA 600.007
6.0.8
New TA facts and properties
October 2009
TWORKS/TA 600.008
6.0.9
Miscellaneous updates
December 2009
TWORKS/TA 600.009
6.0.11
Message overflow
January 2010
TWORKS/TA 600.010
6.0.12
Probe runtime statistics
August 2010
TWORKS/TA 600.011
6.0.14
Added CICS/DB2 support
November 2010
TWORKS/TA 600.012
6.0.16
TrueSight added
May 2011
TWORKS/TA 600.013
6.0.17
Additional statics added
TWORKS/TA 655.001
1
© 1998-2016 Nastel Technologies, Inc.
Chapter 1: Introduction
AutoPilot TransactionWorks TA
Table 1-1. Document History
Release Date
Document Number
AutoPilot
TransactionWorks
Version
Summary
September 2011
TWORKS/TA 600.014
6.0.18
Added transaction milestones
January 2012
TWORKS/TA 600.015
6.0.19
Added control over extraneous
transactions
February 2012
TWORKS/TA 600.016
6.0.19
Errata
April 2012
TWORKS/TA 600.017
6.0.19
Changes to database configuration tables
June 2012
TWORKS/TA 600.018
6.0.20
Added TA expert Analysis tab
May 2013
TWORKS/TA 650.001
6.5
Support for deadline-based (absolute)
SLAs, separate processing for transaction
message payloads, revised fact hierarchy
October 2013
TWORKS/TA 650.002
6.5.1
Updated for V6.5.1. Mantis 8787
November 2013
TWORKS/TA 650.003
6.5.2
Updated for V6.5.2
November 2015
TWORKS/TA 653.001
6.5.3
Updated for V6.5.3
July 2016
TWORKS/TA 653.002
6.5.3
Added additional information about
purging data.
December 2016
TWORKS/TA 655.001
6.5.5
Mantis 14172 (fixed typo on Figure 5-5)
1.3 Related Documents
A complete listing of related and referenced documents is in Appendix A of this guide.
1.4 Release Notes
See README.htm files on your installation media or AutoPilot TransactionWorks installation directory.
Release notes and updates are also available through the Nastel Resource Center at:
http://www.nastel.com/resources.
1.5 Intended Audience
This document is intended for personnel using and customizing Nastel’s AutoPilot TransactionWorks
products. The user should be familiar with:
 Java Run Time Environment 1.5 (JRE 1.5) or higher (included in AutoPilot M6 and higher, for
Solaris, AIX, HP-UX and Linux)
 Target operating system environment
 The user may need administrative privileges for the target platform; consult your system
administrator
 Nastel AutoPilot TransactionWorks terms, concepts, and architecture.
1.5.1
User Feedback
Nastel encourages all users of AutoPilot TransactionWorks to submit comments, suggestions, corrections,
and recommendations for improvement for all AutoPilot Transaction Works documentation. Please send
your comments via mail or e-mail. Send e-mail messages to [email protected]. You will receive a
written response, along with status of any proposed change, update, or correction.
4
© 1998-2016 Nastel Technologies, Inc.
2
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 1: Introduction
1.6 System Requirements
The Transaction Monitor consists of three components; the TA, Transaction Probe (TP), and Explorer.
The TA can be installed on any AutoPilot M6 managed node in the AutoPilot M6 network. The TA must
be installed where it can access the target application within the same network.
 100MB of disk space
 4GB available memory, 32GB+ for high volume transactions (exceeding 1000 msgs/sec)
 Quad-core CPU or higher recommended for high volume transactions
 Dedicated server for high volume transactions
 All servers participating in transaction monitoring must be time synchronized
 SQL-compliant database for storing transaction metrics (MySQL, Oracle).
The TP must be individually installed and configured at each location. Refer to probe specific
documentation for more detail about requirements, installation, and configuration.
The AutoPilot TransactionWorks TA prerequisites are:
 Java 1.6 or higher
 MySQL Server, Version 5.5 or Oracle 11g R2
 Nastel’s AutoPilot M6, Version 6.0 Service Level SU9+
 Nastel’s AutoPilot AIM plugin, Version 6.0.25+
1.7 Technical Support
If you need additional technical support, you can contact Nastel by telephone or by e-mail.
 To contact Nastel technical support by telephone, call 800-963-9822 ext. 1. If you are calling
from outside the United States, dial 001-631-761-9190 or +44 20 7084 6205.
 To contact Nastel technical support by e-mail, send a message to [email protected].
 To contact Nastel technical support through the support website (user ID and password are
required), go to http://support.nastel.com/btracker, or visit the Nastel Resource Center at:
http://www.nastel.com/resources.
Contact your local AutoPilot TransactionWorks administrator for further information.
1.8 Terms and Abbreviations
A list of terms and abbreviation used in all AutoPilot TransactionWorks documentation is located in the
Glossary.
1.9 Conventions
Refer to Appendix B for typographical and naming conventions used in all AutoPilot TransactionWorks
documentation.
TWORKS/TA 655.001
3
© 1998-2016 Nastel Technologies, Inc.
Chapter 1: Introduction
AutoPilot TransactionWorks TA
This page intentionally left blank.
© 1998-2016 Nastel Technologies, Inc.
4
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 2: About TA
Chapter 2: About Transaction Analyzer
The AutoPilot TransactionWorks Transaction Analyzer detects, gathers, and then analyzes transactions
and message data in real time, on demand, and then summarizes the collective data into useful
facts/metrics. The TA also logs transaction data to a database. The transaction and message data is
obtained from Transaction Probes (TPs) for transaction processing applications.
2.1 AutoPilot TransactionWorks/Transaction Analyzer
Features







Tracks transaction groups end-to-end
Detects delayed and incomplete transactions
Analyzes transaction throughput and message volume in real time
Identifies performance bottlenecks
Detects transactions with monetary value using rules set in the user-configured transaction probe
User-defined, rule-based policies for real-time monitoring of all message exchanges
Proactive notification and automated actions based on user-defined criteria.
2.2 AutoPilot TransactionWorks Architecture
The AutoPilot TransactionWorks has three major components:
 Transaction Probes (TPs)
 Transaction Analyzer (TA)
 AutoPilot TransactionWorks Explorer.
TPs are application programs that are executed at a user-defined place in transaction processing
applications and collect transaction-related data. TPs intercept the transaction message data and publish it
to the TA.
TA is an AutoPilot M6 expert (can also be executed as a Web Service or Standalone application) that
collects the transaction message data (published by TPs), analyzes it in real-time, and publishes metric
facts to the AutoPilot M6 facts board as summary statistics. The facts collected can then be recorded in a
database for report generation, and/or used to build business views that address your specific needs.
TA has two transport options:
 TCP/IP (Java, .NET, WMQ, and Direct Feed)
 HTTP (Java and Direct Feed)
TA can be configured to collect transaction details via either one, or all of the transports simultaneously
depending on the transaction probes configuration.
Explorer provides a graphical view of transaction processing network metrics.
TWORKS/TA 655.001
5
© 1998-2016 Nastel Technologies, Inc.
Chapter 2: About TA
AutoPilot TransactionWorks TA
M6 Web Server
AutoPilot M6 Console
Reports
Facts
Business View
AutoPilot M6
CEP Server
Transaction
Analyzer
Database
3
Monitored
Node
Probe
2
API Exit
Handler
TAComm
Application
Queue
1
Queue
Queue
Manager
Transaction
1 = API exit handler (nsqmqprb) intercepts API exits.
2 = API exit handler sends API exit msg to TAConn.
3 = TAConn connects to TA and sends the filtered API exit fact
msg.
Figure 2-1. AutoPilot M6/TransactionWorks Architecture
© 1998-2016 Nastel Technologies, Inc.
6
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 2: About TA
2.3 AutoPilot TransactionWorks Definitions
AutoPilot TransactionWorks defines the following concepts as follows:
Activity – Represents a collection of events that should be considered to be a single application activity.
Application – Represents a logical collection of software components that perform a business function
running on a specific server.
Duration – The “clock” time that a transaction took to complete. This is the difference between the time
of the first send operation and the end of the last LUW.
Logical Unit of Work (LUW) – Represents a collection of operations and messages that should be
considered to be a single unit of work (all or nothing property). These are generally delimited by
START/COMMIT calls.
Message – Represents a physical message being transported through the network.
Message Age – The time that a message was in a resource waiting to be processed.
Operation – Represents a specific operation, such as send, receive, connect, commit, etc.
Resource – An entity on which transactions are executed or a medium of exchange (e.g., Queue, DB
table, file, JMS topic, etc.).
Resource Manager – An entity that is managing a collection of resources. Examples include a WMQ
Queue Manager, Application Server, and Database Server.
Runtime – The period during which the program is executing.
Transaction – A group of activities targeted at achieving a common goal or a task. It is represented by a
collection of related LUWs. This relationship is determined based on the messages exchanged between
the LUWs.
Wait Time – The time that a receive operation was blocked waiting for a message to arrive.
Workload – The sum total of the execution times of all LUWs in a transaction.
TWORKS/TA 655.001
7
© 1998-2016 Nastel Technologies, Inc.
Chapter 2: About TA
AutoPilot TransactionWorks TA
This page intentionally left blank.
© 1998-2016 Nastel Technologies, Inc.
8
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 3: Installation
Chapter 3: Installation
This chapter provides instructions for a typical installation and setup requirements for the AutoPilot
TransactionWorks Transaction Analyzer.
The steps and procedures covered in this chapter are described in the following sections:
 3.1 Before Installation
 3.2 Installing the Transaction Analyzer as AutoPilot Expert.
3.1 Before Installation
The installation procedures in this chapter cover the installation of the Transaction Analyzer (TA)
component of TransactionWorks.
For probe installation instructions see the documentation for the specific probes you will be installing. A
list of available documents can be found in Appendix A, or on the Nastel Resource Center
(http://www.nastel.com/resources).
3.1.1
Technical Documents
Prior to installation you should review all text files and installation procedures. You should print, as
needed, all of the installation-related materials to give yourself quick access to any required information
during any installation or migration procedures. Additional sets of printed documents are available from
your Nastel representative or Nastel Support.
3.1.2
Installation Requirements
If installing the TA into AutoPilot M6, it should be installed on the AutoPilot M6 domain server or any
managed node within the AutoPilot M6 network. If not integrating with AutoPilot M6, then it can be
installed on any server that is accessible from all nodes that contain transaction probes.
The associated transaction probes must be installed and configured properly on every node. The nodes
where the probes are deployed do not require the AutoPilot M6 managed node component to operate.
The nodes only have to be accessible by the managed node or domain server where the TA is installed.
If the physical machines involved in transaction processing are distributed across the network, the system
clocks of those machines must be synchronized. If they are not synchronized, it is necessary to use a
reliable Network Time Protocol (NTP) service.
3.1.3
Contents of AutoPilot TransactionWorks Distribution
The AutoPilot TransactionWorks distribution package consists of the following:




explorer – AutoPilot TransactionWorks Explorer files
probes – AutoPilot TransactionWorks Probes files, organized by probe type
analyzer – AutoPilot TransactionWorks Transaction Analyzer files
samples – sample applications for demonstrating AutoPilot TransactionWorks features.
TWORKS/TA 655.001
9
© 1998-2016 Nastel Technologies, Inc.
Chapter 3: Installation
AutoPilot TransactionWorks TA
3.2 Installing the Transaction Analyzer as AutoPilot
Expert
NOTE:
AutoPilot M6 with Service Update 22 MUST be installed prior to installing the Transaction Analyzer.
1. Save your work and log off AutoPilot M6.
2. Stop nodes and/or CEP servers that will be updated as specified in the AutoPilot M6 User’s Guide.
3. Copy AP_TWORKS_TA-<version_number>.pkg into [AUTOPILOT_HOME]\updates
directory.
4. At the command prompt run:
[AUTOPILOT_HOME]\bin\pkgman [AUTOPILOT_HOME]\updates\AP_TWORKS_TA<version_number>.pkg
~
Figure 3-1. TA File Path Input Screen
5. Verify plug-in installation: [AUTOPILOT_HOME]\bin\pkgman –info. The details of Package
Manager are listed. Verify AutoPilot TransactionWorks –Plug-in (TWORKS-TA) has been listed
into Pkgman output. Make sure there are no errors posted at the bottom of the screen.
© 1998-2016 Nastel Technologies, Inc.
10
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 3: Installation
Figure 3-2. Detail of Installed Library List
6. Also verify that the tworks-api.jar, tworks-logger.jar, tworks-net.jar,
tworks-ta.jar, tworks-util.jar, and tworks-dbutil.jar files have been copied
into the lib directory. Use command console to cd to the lib directory.
TWORKS/TA 655.001
11
© 1998-2016 Nastel Technologies, Inc.
Chapter 3: Installation
AutoPilot TransactionWorks TA
This page intentionally left blank.
© 1998-2016 Nastel Technologies, Inc.
12
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 4: Configuration
Chapter 4: Configuration
4.1 TransactionWorks Database
4.1.1
JDBC and ODBC Drivers
The Transaction Analyzer (TA) works with any database using JDBC compliant drivers. Any JDBC
driver must be in the AutoPilot M6 classpath by copying it to the [AUTOPILOT_HOME]/lib directory.
The Data Source Name (DSN) and JDBC driver values, as given by the JDBC provider, must be
configured in DB Logging in TA properties.
If an ODBC compliant database is used for logging, you may use ODBC:JDBC bridge driver. However,
you must configure ODBC DSN name on the managed node in accordance with the ODBC driver
provider’s instructions.
It is recommended to use native JDBC drivers for better performance. The following table contains
JDBC drivers that are supplied as part of AutoPilot M6 JR1.5.
Table 4-1. Supported Databases and Corresponding JDBC Drivers
Database
JDBC Driver
Data Source Name (DSN) Format
Oracle
(lib/ojdbc5.jar)
oracle.jdbc.OracleDriver
jdbc:oracle:thin:@hostname:port:sid
MySQL (lib/mysqlconnector.jar)
com.mysql.jdbc.Driver
jdbc:mysql://host:port/dbname
NOTE:
It may be required to update JDBC drivers with the newest drivers supplied with your database. It is
usually required when installed JDBC drivers fail or generate errors about database compatibility.
Please refer to database vendor documentation for more information. Be sure to replace AutoPilot M6
database drivers with the versions supplied with your database package.
TWORKS/TA 655.001
13
© 1998-2016 Nastel Technologies, Inc.
Chapter 4: Configuration
4.1.2
AutoPilot TransactionWorks TA
TransactionWorks Database Administration
NOTE:
The database user being used to run database maintenance must have full DBA access to the
TransactionWorks database, as well as read (select) access to the schema containing the data
definition objects for the TransactionWorks database.
The files for administering the database can be found in [AUTOPILOT_HOME]/sqlscripts/tworks. This directory contains the following files:

dbmaint.bat – Windows command file for executing the database creation scripts

dbmaint.sh – UNIX shellscript for executing the database creation scripts
 tworks_dbmaint.xml – ant script to execute administration tasks.
The following administration tasks are supported:
 (Re)Create database – creates a new database instance, deleting any existing data
 Update database – updates the database to the latest schema version, preserving existing data
(with the option of deleting all existing transaction data while preserving user-defined entities)
 Reload stored procedures – reloads stored procedures and referential information, making no
changes to schema or existing data
 Optimize tables/indexes – runs native administrative commands to optimize table memory usage
and index behavior

Purge transactions – purges old data.
The database administration can be run in one of two modes:
 Graphical, wizard-based (default)
 Console-based.
To run wizard-based, run dbmaint.bat (or dbmaint.sh) with no arguments. In this mode, a
standard wizard-based set of screens is displayed prompting for the necessary information. Over telnet or
other remote sessions where it cannot locate a presentation manager, it will also run in console mode.
To force it to run console-based, run dbmaint.bat (or dbmaint.sh) with “-console” argument.
In this mode, a set of prompts will be displayed, allowing the necessary information to be specified.
The UNIX shellscript, dbmaint.sh, requires execute permission. This can be accomplished by
executing the command: chmod +x dbmaint.sh.
NOTE:
In order to execute the ant scripts, Apache Ant must be installed. Apache Ant is included with the M6
distribution
This directory also contains subdirectories for each of the supported database server types. Each serverspecific directory contains the following files (where <dbtype> is the database server type). Not every
file is applicable for all database server types.







tworks_tables_<dbtype>.sql – SQL script for creating database tables
tworks_<dbtype>_properties.xml – Ant script properties containing definitions for
this specific server type
tworks_procs_<dbtype>.sql – SQL script for creating stored procedures
tworks_refs_<dbtype>.sql – SQL script for creating reference tables
tworks_admin_<dbtype>.sql – SQL script containing administrative procedures
tworks_init_schema_<dbtype>.sql – SQL script for initializing the schema that
TransactionWorks objects are created in
tworks_sequences_<dbtype>.sql – SQL script for creating database sequence definitions
© 1998-2016 Nastel Technologies, Inc.
14
TWORKS/TA 655.001
AutoPilot TransactionWorks TA




Chapter 4: Configuration
tworks_set_schema_<dbtype>.sql – SQL script for setting the default schema that
database commands are run against
tworks_utils_<dbtype>.sql – SQL script for creating utility functions, procedures, and type
tworks_validate_<dbtype>.sql – SQL script for validating all schema objects
tworks_purge_trans_<dbtype>.sql – SQL script for purging all existing transaction
data.
4.1.2.1 Creating the Database
NOTES:
1. If you are upgrading an existing version of TransactionWorks and want to maintain your current
transaction information, refer to section 4.1.2.2, Updating the Database.
2. Before creating the database, refer to section 4.2.3, for properly configuring and tuning of database
server.
Before using TransactionWorks, the TransactionWorks database must be created.
To create the database:
1. Use the appropriate administrative tool provided with the database server to create a new database.
2. Create a database user (or choose an existing user) for the Transaction Analyzer to use to log onto the
database server and give this user full access to the database.
3. Run dbmaint.bat (or dbmaint.sh) file and choose the Create option.
4.1.2.2 Updating the Database
If upgrading from a previous version of TransactionWorks and you’d like to maintain the current data,
you can use the update procedure to apply the necessary database schema changes required for this
version of TransactionWorks. The upgrade script files for updating the database can be found in
[AUTOPILOT_HOME]\sql-scripts\tworks\<dbtype>\updates (where <dbtype> is the
database server type).
To update the database:
NOTE:
It is highly recommended that you back up the database before updating it.
1. Stop the TransactionWorks Analyzer if it is running.
2. Windows: Run dbmaint.bat file and choose the Upgrade Database option.
Non-Windows: Run dbmaint.sh file and choose the Update option.
To purge all existing transactions and their associated data items, choose the Purge Transactions
suboption for Update. To maintain all existing transactions, make sure the Purge Transactions
option is not selected.
3. Stop and restart any running copies of TransactionWorks Explorer (APODWeb). Refer to AutoPilot
On-Demand Web Installation and Administration Guide, section 3.2.6 for instructions.
NOTE:
Depending on the size of your database, the update process could take several hours.
TWORKS/TA 655.001
15
© 1998-2016 Nastel Technologies, Inc.
Chapter 4: Configuration
AutoPilot TransactionWorks TA
4.1.2.3 Loading Database Stored Procedures
Loading the stored procedure definitions is done as part of the database Create and Update procedures,
so there is generally no reason to have to do this on its own. One reason would be to apply a patch to the
stored procedure definitions. Note that this will replace all current definitions for the procedures.
To load database stored procedures:
NOTE:
It is highly recommended that you back up the database before updating it.
1. Stop the TransactionWorks Analyzer if it is running.
2. Windows: Run dbmaint.bat file and choose the Reload option.
Non-Windows: Run dbmaint.sh file and choose the Load option.
3. Stop and restart any running copies of TransactionWorks Explorer (APODWeb). Refer to
AutoPilot On-Demand Web Installation and Administration Guide, section 3.2.6 for instructions.
4.1.2.4 Optimizing Tables and Indexes
Over time, it’s possible that the database tables and indexes can become fragmented, resulting in a
degradation of database performance, which will have a negative effect on the TransactionWorks
Analyzer. So periodically, it is recommended to optimize the tables and indexes to remove the
fragmentation.
To optimize tables and indexes:
NOTE:
It is highly recommended that you back up the database before optimizing it. Also, the optimization
procedure can take a significant amount of time, during which the data will NOT be accessible.
1. Stop the TransactionWorks Analyzer if it is running.
2. Run dbmaint.bat (or dbmaint.sh) file and choose the Optimize option.
4.1.2.5 Oracle Database Permissions
User Privilege
A user privilege is the right to run a particular type of SQL statement, or the right to access an object that
belongs to another user, run a PL/SQL package, and so on. The types of privileges are defined by the
Oracle Database.
For instance, a user “TWORKSDBA” needs a dba role to (re)create Tworks schema and tables, carry
out maintenance tasks such as upgrade database, reload store procedures, and optimize tables/indices.
Another user “TWORKS” is needed for the Transaction Analyzer and TransactionWorks Explorer to
have full access to the “TWORKS” schema; i.e., to connect to the Tworks database and accomplish the
current task successfully. See necessary Tworks user “TWORKS” privileges below.
Figure 4-1. Granted Privilege
© 1998-2016 Nastel Technologies, Inc.
16
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 4: Configuration
For instance, user “TWORKSDBA” is created with dba role for use in the database create utility
(dbmaint) to create the database in the schema named “TWORKS”. In Oracle the user name and schema
name are the same. The user “TWORKS” created with grant privileges will connect to Oracle database
using schema “TWORKS” via UI TransactionWorks Explorer and Transaction Analyzer.
For example, a user privilege to CONNECT to DB will suffice as a role granted to user “TWORKS”. In
fact grant CONNECT privilege retains only CREATE SESSION system privilege.
Object Privileges
Each type of object has privileges associated with it. For example, the “TWORKS” user will only need
the following user privileges granted:
 grant create table to TWORKS

grant create procedure to TWORKS

grant create view to TWORKS

grant create sequence to TWORKS

grant create trigger to TWORKS

grant create packages to TWORKS

grant create functions to TWORKS.
Figure 4-2. Object Privileges
TWORKS/TA 655.001
17
© 1998-2016 Nastel Technologies, Inc.
Chapter 4: Configuration
AutoPilot TransactionWorks TA
4.2 Transaction Monitor Optimization
The Transaction Monitor collects data and analyzes it in real-time. To maximize performance the TA has
to be configured properly.
Optimization Points:
TA
 Probe message handling
 Transaction stitching cache
 Statistics publishing
SQL Database
 Buffer Pools
 Tablespace utilization
 Other server-specific parameters
Probes
 Configure to send only required transaction tracking events – results in both decreased memory
and CPU utilization by TA.
© 1998-2016 Nastel Technologies, Inc.
18
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
4.2.1
Chapter 4: Configuration
Memory Optimization
The TA requires enough memory to hold the necessary transaction components for all active transactions,
in order to stitch them properly. It also requires enough memory to store the facts that it publishes. The
following properties affect the memory utilization of the TA:
 Analysis tab
o Transaction Cache Size Limit – The maximum number of active transactions that can be
stored. Reducing this will decrease amount of memory used, but if it is not sufficient to hold
all active transactions, some transactions may be not be stitched together properly.
o Transaction Cache Time Limit – If a transaction has not had activity for at least this amount
of time, it is removed from memory. Reducing this time causes “idle” transactions to be
removed from memory sooner, but setting it too low will cause transactions to possibly be
removed prematurely, thus causing them to not be stitched properly.
 Database – Payloads tab
o Pending Message Payloads Limit – Maximum number of transaction message payloads
queued up in memory for writing to the database. A smaller limit results in less memory used
for queuing payloads, causing additional ones to be written to disk-based overflow.
o Pending Message Payloads Overflow Size Limit – Maximum number of bytes worth of
message payloads queued up in memory for writing to database. A smaller limit results in
less memory used for queuing payloads, causing additional ones to be written to disk-based
overflow.
 HTTP Options tab
o Publish HTTP Connection List – Publish list of all active HTTP connections, showing
remove locations. If this is not required, can be disabled to reduce memory needed for this
information.
o Message Processing tab
o Pending Message Limit – Maximum number of probe tracking messages queued up in
memory for processing. A smaller limit results in less memory used for queuing probe
tracking messages, causing additional ones to be written to disk-based overflow.
o Pending Messages Overflow Size Limit – Maximum number of bytes worth of probe tracking
messages queued up in memory for processing. A smaller limit results in less memory used
for queuing probe tracking messages, causing additional ones to be written to disk-based
overflow.
 Statistics – General tab
o Publish Transaction Statistics Level – Indicates whether “Brief” transaction statistics
(aggregated by transaction status, transaction group, and milestone only) are published, of
“Full” transaction statistics are published, aggregated by all transaction components. Setting
this to “Brief” results in less memory required for publishing these statistics.
 Statistics – Hops tab
o If tracking component level statistics are not required, disabling Default Hop Statistics and
Custom Hop Statistics will eliminate memory required to hold these statistics.
 Statistics – Probe tab
o Publish Probe Runtime Statistics – If probe level statistics are not required, disabling the
publishing of them can eliminate the memory required to hold these statistics.
TWORKS/TA 655.001
19
© 1998-2016 Nastel Technologies, Inc.
Chapter 4: Configuration


4.2.2
AutoPilot TransactionWorks TA
TCP Options tab
o Publish TCP Connection List – Publish list of all active TCP connections, showing remove
locations. If this is not required, can be disabled to reduce memory needed for this
information.
Tracking tab
o Publish Transaction Violation Details – Enabling this option causes details for each
individual transaction that misses a defined SLA to be published, which could consume
considerable memory if there are many SLA violations.
CPU Optimization
The TA utilizes a configurable number of threads for it processing, with each processing category having
its own thread count parameter. In general, having TA use more threads for its processing results in
higher throughput, but over allocation of threads can cause a degradation in performance. A general rule
of thumb is to set the individual thread counts each equal to the number of CPU cores on the system. The
optimal value for each thread count depends on a number of factors, such as other system resources, other
system activity, and nature of transaction behavior. Experimenting with these setting with a
representative transaction load could be used to determine optimal settings. The following TA properties
affect its CPU utilization:
 Analysis tab
o Transaction Analysis Thread Count – Number of parallel threads used for transaction
stitching and analysis.
 Database – Payloads tab
o Message Payloads Pool Size – Number of threads used for writing transaction message
payloads into database.
o Pending Message Payloads Overflow Thread Count – Number of threads used for moving
messages from disk-based overflow back into in-memory queue for processing.
 HTTP Options
o Maximum HTTP Threads – Maximum number of threads to use to service all HTTP
connections.
 Message Processing tab
o Message Process Pool Size – Number of threads used for processing tracking event messages
from probes.
o Pending Messages Overflow Thread Count – Number of threads used for moving tracking
event messages from probes from disk-based overflow back into in-memory queue for
processing.
 TCP Options
o Maximum TCP Threads – Maximum number of threads to use to service all TCP
connections.
© 1998-2016 Nastel Technologies, Inc.
20
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
4.2.3
Chapter 4: Configuration
SQL Database Optimization
Optimal database performance is affected by a variety of factors. Tuning them requires adjusting the
defined settings based on the workload being run. TA is both write- and read-intensive, so the database
needs to be tuned to support both of them efficiently. TA also performs each of these operations
concurrently, so eliminating resource contention should be part of any tuning procedures.
While what parameters are available for tuning the performance of the database server vary by server
type, there are some general guidelines to help increase the performance of the database server, and
therefore the performance of the TA:
 Providing a dedicated server to host the database, with a minimum of 8 cores (64-bit) and 32 GB
of RAM
 Dedicate at least half of the available RAM to the database, depending on other activities on the
server (leaving sufficient memory of OS and other system activities).
 Store the database files, especially the redo and undo logs, on multiple direct-attached, high-speed
disk drives.
The TA installation includes sample configuration files for the various database servers it supports with
the recommended settings, based on an 8 core, 24GB system. These are generic configurations suitable
for generic environments. The optimal settings depend on both system resources and tracking event
contents and volume. You should consult with the database server documentation for a description of
these parameters, and the effects caused by changing them. Here are some general guidelines for each
database server:
 Oracle
o Use a minimum block size of 8K.

o
Use Oracle Automatic Memory Management, setting MEMORY_TARGET to at least onehalf of available system RAM.
o
The supplied Oracle scripts use the default tablespace for the defined user, with the exception
of the message payload table (tw_message_data), which is stored in a separate tablespace
(tw_message_data_tblsp). The scripts create this tablespace (if it does not already exist) with
the default block size, and in the default location. If a significant number of message
payloads will be larger than default block size, it’s recommended to use a block size of 16K
or 32K for this table space, setting corresponding DB_nK_CACHE_SIZE to a least 1GB.
o
Init.ora file contains recommended settings
MySQL
o Store InnoDB tables in separate files
o
my.cnf (my.ini) contain recommended settings (ini file for Windows)
TWORKS/TA 655.001
21
© 1998-2016 Nastel Technologies, Inc.
Chapter 4: Configuration
AutoPilot TransactionWorks TA
This page intentionally left blank.
© 1998-2016 Nastel Technologies, Inc.
22
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 5: Using TA
Chapter 5: Using AutoPilot TransactionWorks/
Transaction Analyzer
5.1 Deploying Transaction Analyzer Expert
An instance of TA is automatically installed and activated after installing the TA package. This instance
is displayed under the CEP server where the Transaction Monitor was installed as TransactionWorks >
Transaction_Analyzer.
To check that the instance is installed, expand the tree under your CEP Server. You should see CEP
Server > TransactionWorks > Transaction_Analyzer and Transaction_Manager.
Figure 5-1. Verify Installation
NOTE:
The database connection information must be set for this default instance. (See step 7 below).
If you want to create your own instance, you can use steps 1 - 3. Otherwise, to set the properties for
Transaction_Analyzer, right click on it, select Properties and continue at step 4.
1. Open the AutoPilot M6 Console.
2. Right-click on the CEP server where the Transaction Monitor was installed.
3. Click Deploy Expert > TransactionWorks > Transaction Analyzer.
displayed in the figure below is described in detail in Chapter 6.
The expert deployment
Figure 5-2. Deploy TA Expert
TWORKS/TA 655.001
23
© 1998-2016 Nastel Technologies, Inc.
Chapter 5: Using TA
NOTE:
AutoPilot TransactionWorks TA
It is recommended that as a minimum you configure the General, Database, HTTP Options, and TCP
Options tabs.
4. The General tab screen is displayed. It is recommended that you update the description, context, and
name to define each expert. At a minimum apply a definitive name to your agent.
Figure 5-3. TA Expert: General
Table 5-1. TA Expert: General
Property
Description
Brief description
Short, user-defined description of the service.
Context
User-defined category that will be registered with the domain server. The
default is TransactionWorks.
Name
Name of the service.
5. Click the About tab. These parameters are common to all experts and cannot be edited.
Figure 5-4. TA Expert: About
Table 5-2. TA Expert: About
Property
Description
Package Title
Implementation title of the source package.
Package vendor
Name of implementation vendor.
Package version
Package version as assigned by the vendor.
© 1998-2016 Nastel Technologies, Inc.
24
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 5: Using TA
6. Click the Analysis tab. Identify and format properties as described in the following table, as required.
Figure 5-5. TA Expert: Analysis
Table 5-3. TA Expert: Analysis
Property
Description
Analysis Delay Intervals
Number of intervals behind current time that the analysis will be
processed (0 – 10)
In-Progress Transaction Analysis
Interval (sec)
Interval, in seconds, that long-running in-progress transaction statuses
are evaluated (0 = disable)
Preload Transaction Cache
Load the memory transaction cache with currently active transactions
when analyzer starts. This is required in order to stitch newly-received
transaction operation with existing transactions across analyzer
restarts.
Transaction Analysis Interval (sec)
Interval, in seconds, that analyzer runs, stitching new activity to
existing transactions and creating new transactions, as appropriate.
Transaction Analysis Thread Count
Number of parallel threads to use in running analysis.
Transaction Cache Size Limit
Number of transactions to keep in Transaction Cache. When limit is
reached, transactions are removed from the cache in a least-recentlyupdated manner, with transaction last updated furthest in the past
removed. A value of 0 implies no cache limit based on size.
Transaction Cache Time Limit (min)
Maximum amount of time, in minutes, to keep a transaction in the
cache. If it has not been updated within this time, then it is removed
from the cache. A value of 0 implies no cache limit based on time.
Transaction Incomplete Interval
Limit (min)
Interval after which the transaction status will be marked from InProgress to Incomplete.
Transaction LUW Expiration (sec)
Length of time that an LUW is expected to be completed in. Single
LUW transactions that have not been updated within this interval are
considered for automatic purging.
TWORKS/TA 655.001
25
© 1998-2016 Nastel Technologies, Inc.
Chapter 5: Using TA
AutoPilot TransactionWorks TA
Table 5-3. TA Expert: Analysis
Property
Description
Transaction LUW Limit
Maximum number of LUWs allowed for a single transaction (0 = no
limit).
Transaction Message Level
Number of messages at which transactions are considered for
automatic purging during analysis. Transactions that contain only one
LUW have a message count at or below this level, and have not been
updated within LUW Expiration interval are purged.
Transaction Operation Level
Number of operations at which transactions are considered for
automatic purging during analysis. Transactions that contain only one
LUW have an operation count at or below this level, and have not been
updated within LUW Expiration interval are purged.
7. Click the Database tab. Identify and format properties as described in the following table, as
required.
Figure 5-6. TA Expert: Database
Table 5-4. TA Expert: Database
Property
Description
Data Source Name
(DSN)
Data source name or URL. (Reference JDBC and ODBC documentation and Chapter 4,
Configuration.)
DB logon ID
Logon ID to access database, if required. See your local DBA for logon information.
DB password
Password to access database. See your local DBA for password information.
Default Schema
Default database schema for accessing unqualified database items. If blank, then the
default schema for the database the user specified by DB logon ID, as determined by
the database server, is used.
JDBC Batch Size
Maximum number of records to include in a single batched database operation
JDBC Driver
Java Database Connectivity Driver name. (Refer to JDBC documentation and
Chapter 4, Configuration.)
© 1998-2016 Nastel Technologies, Inc.
26
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 5: Using TA
Table 5-4. TA Expert: Database
Property
Description
JDBC Fetch Size
Fetch size is a performance hint which tells the JDBC driver how many rows should be
fetched from the database when more rows are needed by the client. Increasing this
value can improve overall query performance, especially with large result sets.
Ping interval (min)
Interval, in minutes, to periodically ping database to ensure database connection stays
active. This value should be less than the server’s wait or inactivity timeout.
Retry attempts
Number of times to retry a failed database operation. 0 means retry indefinitely.
Retry failed save
Retry database save operations. If this is disabled, probe messages that cannot be saved
to the database are discarded.
Retry interval (sec)
Number of seconds to wait and retry DB connection or operation in case previous
attempt has failed.
Write Probe Data to
Database
Enables/disables writing of probe transaction data to the database. This must be
enabled for transaction analysis. Disabling this is useful only for collection of hop
statistics.
8. Click the Database - Payloads tab. Identify and format properties as described in the following table,
as required.
Figure 5-7. TA Expert: Database – Payloads
TWORKS/TA 655.001
27
© 1998-2016 Nastel Technologies, Inc.
Chapter 5: Using TA
AutoPilot TransactionWorks TA
Table 5-5. TA Expert: Database – Payloads
Property
Description
Compress Message Payloads
Indicates whether message payload data should be compressed before being
written to database.
Enable Pending Message
Payloads Overflow
When enabled, incoming messages will be routed to an overflow store when the
Pending Messages Limit is reached.
Message Payloads Pool Size
Number of probe message processing threads. For large volume of probe
messages, increase this to allow multiple messages to be processed in parallel.
This should generally be a number between 1 and 5.
Minimum Compress Size
(bytes)
Minimum message payload size, in bytes, that should be compressed. Set this to
0 to compress all message payload data.
Pending Message Payloads
Limit
Maximum number of probe messages that can be queued for processing. When
this limit is reached, the threads servicing probe messages will be blocked until
the number of queued messages is reduced.
Pending Message Payloads
Overflow Batch Size
Number of transaction message payloads to load from overflow store at one
time for re-queuing back onto in-memory queue for writing.
Pending Message Payloads
Overflow Directory
Location of overflow store. Use the Browse button to select a directory.
Pending Message Payloads
Overflow Limit
Maximum number of messages to maintain in the overflow store. When this
limit is reached, messages will be dropped. A value of 0 implies no limit.
Pending Message Payloads
Overflow Size Limit (MB)
Maximum amount of memory, in megabytes, to maintain in the overflow store.
When this limit is reached, messages will be dropped. A value of 0 implies no
limit.
Pending Message Payloads
Overflow Thread Count
Number of threads to use to move transaction message payloads in overflow
store back onto in-memory queue for writing.
9. Click the Dependencies tab. Edit properties described in the table below, as required.
parameters are common to all experts.
These
Figure 5-8. TA Expert:: Dependencies
Table 5-6. TA Expert: Dependencies
Property
Description
Platform dependencies
Dependencies on operating system platforms, which are expressed in a
comma separated list.
Service dependencies
Dependencies on other services, which are expressed in a comma separated
list.
© 1998-2016 Nastel Technologies, Inc.
28
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 5: Using TA
10. Click the Fact Options tab. Edit properties described in the table below, as required.
parameters are common to all experts.
These
Figure 5-9. TA Expert: Fact Options
Table 5-7. TA Expert: Fact Options
Property
Description
Exclude Expire Filter (regexp)
Facts that match the specified regular expression are not expired
Exclude Fact Filters
Comma separated list of fact paths to exclude during publishing.
For example: *SYSTEM*, *FactName*
Expire facts(ms)
User-defined time in which facts that have not been updated within a specific
time automatically expire (in milliseconds). 0 means never expire. Expire
facts must be less than Statistics reset rate value (in seconds), under the
Statistics tab, or the facts will continue to reset and never expire.
Fact History Size
Automatically maintain the specified number of samples for each published
fact in memory. 0 means there is no limit.
Fact History Time (ms)
Automatically maintain fact history not exceeding specified time in
milliseconds.
Fact service alias
Override fact service prefix for all published facts. Facts will be appearing
under specified service name.
Include Expire Filter (regexp)
Facts that match the specified regular expression are expired
Include Fact Filters
Comma separated list of fact paths to include during publishing.
For example: *SYSTEM*, *FactName*
Lock Fact History
Enables/disables history collection after accumulating the first history batch
up to Fact History Time or Fact History Size which ever limit is reached
first. If disabled newer history samples replace older on a rolling basis.
TWORKS/TA 655.001
29
© 1998-2016 Nastel Technologies, Inc.
Chapter 5: Using TA
AutoPilot TransactionWorks TA
11. Click the HTTP Options tab. Edit properties described in the table below, as required.
NOTE:
This option must be used when probes are configured to send TM facts using the HTTP protocol. The
port specified (6480 by default) MUST match the configuration specified when the probes are
installed.
Figure 5-10. TA Expert: HTTP Options
Table 5-8. TA Expert: HTTP Options
Property
Description
Accepted Access Tokens
List of accepted access tokens when using authenticated HTTP connections. An
empty list implies that authenticated connections are not being used. Use the
Add button to add a new entry to the list. Use the Remove button to remove
selected entries from the list.
Enable HTTP listener
Enable/disable to accept probe messages via HTTP transport published to
specified port. Default is disabled.
HTTP port
Port number that Transaction Analyzer will listen for HTTP messages. The
default is 6480.
Maximum HTTP Threads
Maximum number of threads to use for processing all HTTP probe connections.
Publish HTTP Connection List
Enable/disable publishing of information for active HTTP probe connections.
Secure Connection
Enable/disable use of secure (HTTPS) connection.
SSL Certificate Keystore
Password
Password for keystore containing SSL server certificate for use with secure
connection.
SSL Certificate Keystore
File name for keystore containing SSL server certificate for use with secure
connection. Use the Browse button to select the keystore file.
© 1998-2016 Nastel Technologies, Inc.
30
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 5: Using TA
12. Click the Logging tab. Edit properties as defined in the table below, as required. These parameters
are common to all experts.
Figure 5-11. TA Expert: Logging
Table 5-9. TA Expert: Logging
Property
Description
Audit
Enable/disable service audit trace.
Log name
Log name associated with the service. Default is Services.
Log service activity
Enable/disable service activity trace.
Log size (bytes)
Enter log file size if the activity is enabled. Default is 200000.
TWORKS/TA 655.001
31
© 1998-2016 Nastel Technologies, Inc.
Chapter 5: Using TA
AutoPilot TransactionWorks TA
13. Click the Message Processing tab. Edit properties described in the table below, as required.
Figure 5-12. TA Expert: Message Processing
Table 5-9A. TA Expert: Message Processing
Property
Description
Enable Pending Messages
Overflow
When enabled, incoming messages will be routed to an overflow store when
the Pending Messages Limit is reached.
Encrypt Pending Messages
Overflow
Indicates whether data in the overflow store should be stored encrypted.
NOTE: When changing from encrypted to unencrypted, the current contents
of the overflow store, if any, are discarded, so you should verify that the
overflow store is empty before changing this attribute.
Message Process Batch Size
Number of messages read from pending queue and processed in a single
database transaction.
Message Process Pool Size
Number of probe message processing threads. For large volume of probe
messages, increase this to allow multiple messages to be processed in parallel.
This should generally be a number between 1 and 8.
Pending Messages Limit
Maximum number of probe messages that can be queued for processing.
When this limit is reached, the threads servicing probe messages will be
blocked until the number of queued messages is reduced.
Pending Messages Overflow
Batch Size
Number of messages to load from overflow store at one time for requeuing
back onto in-memory queue for processing.
Pending Messages Overflow
Directory
Location of overflow store. Use the Browse button to select a directory.
Pending Messages Overflow
Limit
Maximum number of messages to maintain in the overflow store. When this
limit is reached, messages will be dropped. A value of 0 implies no limit.
Pending Messages Overflow
Size Limit (MB)
Maximum amount of memory, in megabytes, to maintain in the overflow
store. When this limit is reached, messages will be dropped. A value of 0
implies no limit.
Pending Messages Overflow
Thread Count
Number of threads to use to move messages in overflow store back onto inmemory queue for processing.
© 1998-2016 Nastel Technologies, Inc.
32
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
13A.
Chapter 5: Using TA
Click the Message Processing-Suppression tab. Edit properties described in the table below, as
required.
Figure 5-12A. TA Expert: Message Processing-Supression
Table 5-9B. TA Expert: Message Processing-Supression
Property
Description
Suppress List: Always
Included Resources
List of resources (regular expressions) which overrides exclusion lists and will
always be written to the database.
Suppress List: Automated
Excluded Resources
List of resources comparable to the manual list but provided for maintenance
via automatic methods (SuppressedObjectAdd/Remove). Can only be
removed via properties.
Suppress List: Manual
Excluded Resources
List of resources (regular expressions) whose operations will not be recorded
to TransactionWorks database.
Suppress Normal Start/End
Operations
Suppress normal start and end operations (typically commit control) from
being written to the database.
TWORKS/TA 655.001
33
© 1998-2016 Nastel Technologies, Inc.
Chapter 5: Using TA
AutoPilot TransactionWorks TA
14. Click the Recording tab. Edit properties as defined in the table below, as required. These parameters
are common to all experts.
Figure 5-13. TA Expert: Recording
Table 5-10. TA Expert: Recording
Property
Description
Anomaly Deviation Limit
Number of standard deviations above or below the mean.
Exclude Filter (regexp)
A regular expression filter to exclude certain facts from being written to the database.
Facts have the format expert\class\instance\leaf=value such as in the
example Servers\Linux\Serv7\processes=40.
Fact Anomaly Frequency
Frequency at which anomalies are checked and recorded.
Fact State Frequency
If Record Fact State is enabled, the value entered here specifies how often the Fact
State is updated.
Fact Summary
Frequency
If Record Fact Summary is enabled, used to write an intermediate summary record
every Xth update to the fact during the Summary Interval. In this example, every 50th
update to the fact an intermediate summary record is recorded. This is done to avoid
waiting 15 minutes for a summary record to appear in the summary table.
Include Filter (regexp)
A regular expression filter to include certain facts being written to the database.
Same format as described for the exclude filter.
Record Fact Anomalies
Enable/disable fact anomaly recording for this service.
Record Fact History
If enabled, records every fact change into the History database. The exclude/include
filters are respected. To define database tables and set AutoPilot options, refer to
AutoPilot M6 User’s Guide with Service Update 8, section 4.5.4.1.
© 1998-2016 Nastel Technologies, Inc.
34
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 5: Using TA
Table 5-10. TA Expert: Recording
Property
Description
Record Fact State
If enabled, records the last value published (current state) into the state database and
restores that value when the CEP Server is stopped and restarted. The
exclude/include filters are respected. To define database tables and set AutoPilot
options, refer to AutoPilot M6 User’s Guide with Service Update 8, section 4.5.4.1.
Record Fact Summary
If enabled, records summary record at the interval designated in the Summary
Interval (ms) field into the Summary database. The exclude/include filters are
respected. To define database tables and set AutoPilot options, refer to AutoPilot M6
User’s Guide with Service Update 8, section 4.5.4.1.
Storage for Anomalies
SQL table where anomalies are recorded.
Storage for History
Database table where the Fact History data is stored.
Storage for State
Database table where the Fact State data is stored.
Storage for Summary
Database table where the Fact Summary data is stored.
Summary Interval (ms)
If Record Fact Summary is enabled, designates the interval of time in ms for which
baseline numbers for each numeric fact are computed. Summary Interval is only in
affect when CEP instance is running in record mode (ATPNODE –record). Default
900000 is 15 minutes, which means maintain a baseline of statistics for each numeric
fact for a period of 15 minutes and write a record to the database. At the end of
interval fact statistics is reset and the baseline collection starts again.
14. Click the Restart-Recovery tab. Edit properties as defined in the table below, as required. These
parameters are common to all experts.
Figure 5-14. TA Expert: Restart-Recovery
Table 5-11. TA Expert: Restart-Recovery
Property
Description
Automatic start
Enable/disable automatic start of this service.
Save in registry
Enable/disable save persistent services in registry.xml file
Synchronous Control
Enable/disable synchronous service initiation.
TWORKS/TA 655.001
35
© 1998-2016 Nastel Technologies, Inc.
Chapter 5: Using TA
AutoPilot TransactionWorks TA
15. Click the Security tab. Enable or edit requirements as defined in the table below. These parameters
are common to all experts.
Figure 5-15. TA Expert: Security
Table 5-12. TA Expert: Security
Property
Description
Inherit permissions
from owner
Enable/disable inheriting of permissions from the owner’s permissions which are
applied to the service and displayed in the permission check boxes. If this option is not
selected the permissions can be set independently.
Owner
User that owns the object. Can be edited by clicking Change.
Permissions
Permissions for users of the same group as the owner and others. Enable/disable as
required.
Group
Other (Users)
Read
Group members may read/view attributes
of an object.
Others may read/view attributes of an
object.
Change
Group members may change the
attributes of an object.
Others may change the attributes of an
object.
Delete
Group members may delete the object.
Others may delete the object.
Control
Group members may execute control
actions such as start, stop, and disable.
Others may execute control actions such as
start, stop, and disable.
Execute
Group members may execute operational
commands on the object.
Others may execute operational commands
on the object.
© 1998-2016 Nastel Technologies, Inc.
36
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 5: Using TA
15. Click the Statistics-General tab. Enter or enable requirements as defined in the table below.
Figure 5-16. TA Expert: Statistics - General
Table 5-13. TA Expert: Statistics - General
Property
Description
Publish Transaction History
Interval (sec)
Interval that active transaction statistics are published, in seconds.
Publish Transaction Statistics
Level
Level of aggregate transaction statistics to publish:
Brief – Publish statistics for Transaction Status, Transaction Groups, and
Milestones
Full – Publish statistics for all transaction components
Publish Transaction Statistics
Rate
Designates how often transaction statistic facts are published, in terms of
statistics interval. For example, 1 means publish every statistics interval, 2
means publish every second statistics interval, etc.
Statistics Reset Interval (sec)
Rate at which statistics are reset in seconds (0 means never). Statistics reset
rate must be higher than time set for Expire facts, under the Fact Options tab
(Figure 5-9), or the facts will continue to reset and never expire.
TA Statistics Publishing
Interval (sec)
Rate of publishing analyzed data in seconds.
TWORKS/TA 655.001
37
© 1998-2016 Nastel Technologies, Inc.
Chapter 5: Using TA
AutoPilot TransactionWorks TA
17. Click the Statistics- Hops tab. Enter or enable requirements as defined in the table below.
Figure 5-17. TA Expert: Statistics – Hops
Table 5-14. TA Expert: Statistics - Hops
Property
Description
Comma-separated list of categories to use to aggregate transaction hop
statistics. Valid categories are:
Custom Hop Categories

Resource

ResourceType

ResourceMgr

ResourceMgrType

Application

Server

User

MsgTag

MsgFormat

TransportType

Operation

OperationType
Custom Hop Masks (regexp)
A comma-separated list of hop category masks (regular expressions) to define
which instances for specific categories to include in Custom Hop Statistics.
Enable Custom Hop Statistics
Enable/disable collection and publishing of hop statistics based on custom
categories defined above.
Enable Default Hop Statistics
Enable/disable collection and publishing of hop statistics using default
aggregation categories.
Hop Statistics Interval (sec)
Interval at which hop statistics facts are updated in seconds.
© 1998-2016 Nastel Technologies, Inc.
38
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 5: Using TA
18. Click the Statistics- Probe tab. Enter or enable requirements as defined in the table below.
Figure 5-18. TA Expert: Statistics – Probe
Table 5-15. TA Expert: Statistics - Probe
Property
Description
Probe Runtime Statistics
Grouping
Specifies how runtime statistics reported by the individual probes are
grouped. The supported groupings are:
 Host/Type – First group the statistics by the host on which the
probes are running, then within each host by the type of probe.
 Type/Host – First group the statistics by the type of probe, then
within each probe type by the host on which the probes are running.
Probe Runtime Statistics
interval (sec)
Interval at which probe runtime statistics facts are updated in seconds.
Publish Probe Runtime
Statistics
Enable/disable publishing of probe runtime statistics.
19. Click the TCP Options tab. Enter or enable requirements as defined in the table below.
NOTE:
This option must be used when probes are configured to send TM facts using the TCP protocol. The
port specified (6400 by default) MUST match the configuration specified when the probes are
installed.
Figure 5-19. TA Expert: TCP Options
TWORKS/TA 655.001
39
© 1998-2016 Nastel Technologies, Inc.
Chapter 5: Using TA
AutoPilot TransactionWorks TA
Table 5-16. TA Expert: TCP Options
Property
Description
Enable TCP listener
Enable/disable to accept probe messages via TCP transport published to
specified TCP port. Default is enabled.
Maximum TCP Threads
Maximum number of threads to use for processing all TCP probe connections.
Publish TCP Connection List
Enable/disable publishing of information for active TCP probe connections.
TCP port
TCP port number on which the TA will listen for incoming facts from
transaction probes. The default is 6400.
19A.
Click the TNT Logging tab. Enter or enable requirements as defined in the table below.
Figure 5-19A. TA Expert: TNT Logging
Table 5-16A. TA Expert: TNT Logging
Property
Description
Application name
Sets application name
Data center name
Sets data center name
Location
Sets server location
Log Facts
Enable/disable fact logging
TNT4j configuration name
TNT4j configuration block name
Write Probe Data to TNT4j
Write data reported by TransactionWorks probes to TNT
© 1998-2016 Nastel Technologies, Inc.
40
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 5: Using TA
20. Click the Trace Logging tab. Enter or enable requirements as defined in the table below.
Figure 5-20. TA Expert: Trace Logging
Table 5-17. TA Expert: Trace Logging
Property
Description
Enable Trace Logging to Console
Enable/disable logging of TA activity to console window.
Enable Trace Logging to File
Enable/disable logging of TA activity to specified file.
Log All Probe Messages
Enable/disable saving of all probe messages to a file
Log Failed Probe Messages
Enable/disable saving of probe messages that the analyzer failed to process
to a file.
Maximum Trace Log File
Backups
Maximum number of backup log files. When current log file is filled up, the
current file is moved to the backup and a new file is created, with the oldest
backup file being removed.
Maximum Trace Log File Size
(bytes)
Maximum log file size in bytes of any log file, including backups.
Probe Message Log Directory
Directory where the probe messages are logged. Messages are logged to a
subdirectory of this directory based on the data the message logged.
Trace Log File Name
Name of file where messages are logged.
Trace Logging Apply Component
Levels
Enable/disable custom logging levels per Transaction Analyzer component.
Trace Logging Base Level
Default level of messages to include in file, for those components not
overridden. Can be one of three:
 INFO – General messages about state of TA. This is the default.
 DEBUG – Includes information about actions TA is taking.
 TRACE – Includes detailed information about actions TA is taking,
displaying contents of all messages received.
TWORKS/TA 655.001
41
© 1998-2016 Nastel Technologies, Inc.
Chapter 5: Using TA
AutoPilot TransactionWorks TA
Table 5-17. TA Expert: Trace Logging
Property
Description
Level of messages to include in file for each analyzer component, overriding
the base level. Components are:

Analysis – logging messages related to transaction analysis,
including stitching and computing transaction metrics.

Message Reading – logging messages related to receiving messages
from probes.

Metrics Publishing – logging messages related to gathering and
publishing transaction metrics.
Trace Logging Component Levels

Message Processing – logging messages related to processing of
messages from probes, including parsing and persisting to database.
The levels are the same set as defined in Trace Logging Base Level
21. Click the Tracking tab. Enter or enable requirements as defined in the table below.
Figure 5-21. TA Expert: Tracking
Table 5-18. TA Expert: Tracking
Property
Description
Enable Message Tracking
Enable/disable transaction tracking and SLA measurement. This field must
be enabled to see tracking facts in AutoPilot.
Publish Transaction Violation
Details (memory intensive)
Enable/disable publishing violation facts for MISSED, FAILED, and
INDOUBT transactions. When disabled, will still keep count of the number
of transactions that had violations.
© 1998-2016 Nastel Technologies, Inc.
42
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 5: Using TA
22. If adding a new expert, click Deploy. The name of the expert/service being deployed is repeated
along with the node where it will be deployed.
Figure 5-22. TA Service Deployed
OR
To deploy on multiple nodes within the AutoPilot domain, click Deploy On and select the unique
name to be used and the nodes where the expert will be deployed.
Figure 5-23. Deploy Expert on Multiple Nodes
23. The deployed expert(s) will be displayed under the nodes where they were deployed, as in the figure
below. The facts produced by each expert are defined in Chapter 6, AutoPilot TransactionWorks/
Transaction Analyzer Metrics.
Figure 5-24. Deployed TA Expert
TWORKS/TA 655.001
43
© 1998-2016 Nastel Technologies, Inc.
Chapter 5: Using TA
AutoPilot TransactionWorks TA
This page intentionally left blank.
© 1998-2016 Nastel Technologies, Inc.
44
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 6: TA Metrics
Chapter 6: Transaction Analyzer Metrics
This chapter describes the Transaction Analyzer (TA) metrics collected by the TA expert. The TA
publishes facts in the following categories:
 AnalyzerStats – Statistics about the execution of the Transaction Analyzer.
 DBStats – Statistics about the database.
 HopStats – Statistics about the individual steps for transactions.
 ProbeStats – Statistics about messages the Transaction Analyzer has received from the probes.
 Tracking – Facts related to transaction analysis using a service-level specification.
 TransactionStats – Statistics about transactions flowing through the network.
6.1 AnalyzerStats
AnalyzerStats are statistics about the performance of the Transaction Analyzer itself, providing
information about the transaction metrics calculations the analyzer is performing.
Figure 6-1. Transaction Analyzer AnalyzerStats Metrics
TWORKS/TA 655.001
45
© 1998-2016 Nastel Technologies, Inc.
Chapter 6: TA Metrics
AutoPilot TransactionWorks TA
Table 6-1. Facts Published by TA: AnalyzerStats
Metric
Description
AnalyzerStats/ActiveInterval
active_tran_analysis_interval_active_transactions
Number of transactions active for the current active
analysis interval.
active_tran_analysis_interval_end_time_time
End of time period being processed by current
active analysis interval.
active_tran_analysis_interval_luw_msg_pairs
Number of distinct LUW/Message combinations
logged during last time period for current active
analysis interval (represents the number of items
that require stitching).
active_tran_analysis_interval_luws
Number of distinct LUWs for current active
analysis interval.
active_tran_analysis_interval_msgs
Number of distinct Messages for current active
analysis interval.
active_tran_analysis_interval_operations
Number of operations logged during time period for
current active analysis interval.
active_tran_analysis_interval_start_time_time
Start of time period processed during current active
analysis interval.
active_tran_analysis_start_time
Date and time the current active analysis started.
AnalyzerStats/Caches
active_correlator_map_size
Number of entries in correlator-to-transaction map.
active_luw_map_size
Number of entries in LUW-to-transaction map.
active_msg_map_size
Number of entries in message-to-transaction map.
active_tran_map_size
Number of entries in the transaction-to-components
map (maps transaction to list of LUWs, messages,
and correlators in transaction).
active_tran_members_map_size
Number of entries in transaction-to-luw_msg_pairs
map.
active_tran_update_times_map_size
Number of entries in the last_update_time-totransactions map.
AnalyzerStats/PreviousInteval/Phases
last_tran_analysis_calc_duration_msec
Amount of time to calculate transaction metrics
during the last analysis interval in milliseconds.
last_tran_analysis_db_write_duration_msec
Amount of time to transaction stitching results to
the database during the last analysis interval in
milliseconds.
last_tran_analysis_load_duration_msec
Amount of time to load data from database for last
analysis interval in milliseconds.
last_tran_analysis_purge_duration_msec
Amount of time to auto purge transactions for last
analysis interval in milliseconds.
last_tran_analysis_stitch_duration_msec
Amount of time to stitch LUWs/Messages for last
analysis interval in milliseconds.
AnalyzerStats/PreviousInterval
Date and time last (or current) transaction metrics
calculation started.
last_tran_analysis_end_time
© 1998-2016 Nastel Technologies, Inc.
46
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 6: TA Metrics
Table 6-1. Facts Published by TA: AnalyzerStats
Metric
Description
last_tran_analysis_interval_active_transactions
Duration of the last transaction auto purge in
milliseconds.
last_tran_ analysis_interval_auto_purge_count
The number of transactions that were automatically
purged during the last metrics calculation. Only
displayed if auto purge filters are enabled.
last_tran_analysis_interval_auto_purge_duration_msec
Duration of the last transaction auto purge in
milliseconds.
last_tran_analysis_interval_auto_purge_time
Last time that transactions were actually auto
purged. Not displayed if transactions were never
auto purged.
last_tran_analysis_interval_end_time_time
End of time period processed during last completed
analysis interval.
last_tran_analysis_interval_luw_msg_pairs
Number of distinct LUW/Message combination
logged during last time period for last completed
analysis interval (represents the number of items
that require stitching).
last_tran_analysis_interval_luws
Number of distinct LUWs for last completed
analysis interval.
last_tran_analysis_interval_msgs
Number of distinct Messages for last completed
analysis interval.
last_tran_analysis_interval_operations
Number of operations logged during time period for
last completed analysis interval.
last_tran_analysis_interval_start_time_time
Start of time period processed during last
completed analysis interval.
last_tran_analysis_interval_tran_members_added
Number of new LUW/Message pairs stitched to
transactions during last complete analysis interval.
last_tran_analysis_interval_tran_members_avg_dur_ms
Average time to insert an LUW/Message pairs for a
transaction during last complete analysis interval in
milliseconds.
last_tran_analysis_interval_tran_members_dur_ms
Total time to insert all LUW/Message pairs for all
transactions during last complete analysis interval
in milliseconds.
last_tran_analysis_interval_tran_merge_avg_dur_ms
Average time to merge two transactions into a
single transaction during last complete analysis
interval in milliseconds.
last_tran_analysis_interval_tran_merge_dur_ms
Total time to merge transactions during last
complete analysis interval in milliseconds.
last_tran_analysis_interval_tran_merges
Number of transaction merges done during last
complete analysis interval.
last_tran_analysis_interval_truncated_trans
Number of transactions that have been truncated
because they reached the defined LUW limit during
last complete analysis interval.
last_tran_analysis_interval_updated_trans
Number of transactions updated/created during last
complete analysis interval.
last_tran_analysis_start_time
Date and time that the last completed analysis
started.
TWORKS/TA 655.001
47
© 1998-2016 Nastel Technologies, Inc.
Chapter 6: TA Metrics
AutoPilot TransactionWorks TA
Table 6-1. Facts Published by TA: AnalyzerStats
Metric
Description
AnalyzerStats
active_tran_analysis_in_progress
Indicates whether there is an active transaction
analysis running.
failed_tran_analysis_attempts
The number of transaction metric calculations that
failed.
last_tran_analysis_duration_msec
Duration of last transaction metrics calculation in
milliseconds.
next_tran_analysis_start_time
Date and time when next analysis interval is
scheduled to start.
since_last_reset_sec
Number of seconds since the facts in AnalyzerStats
were reset.
total_tran_analysis_attempts
Total number of transaction metric calculation
attempts.
total_tran_auto_purge_count
Total number of transactions that have been auto
purged.
ran_analysis_interval_length_msec
Fixed length of a transaction analysis interval in
milliseconds.
tran_analysis_lag_msec
Total time that analyzer has fallen behind in
milliseconds. Represents the difference in time
between the interval currently being analyzed and
the expected interval that should currently be
analyzed.
© 1998-2016 Nastel Technologies, Inc.
48
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 6: TA Metrics
6.2 DBStats
Database statistics contains metrics about the database connection and the schema version.
Figure 6-2. Transaction Analyzer DBStats Metrics
Table 6-2. Facts Published by TA: DBStats
Metric
Description
database_connected
Indicates whether or not the Transaction Analyzer has a valid connection to
the database.
database_product
Description of database server that TransactionWorks Analyzer is connected
to.
db_schema_version
Schema version for the TransactionWorks database that the Transaction
Analyzer is connected to.
db_schema_version_match
Indicates whether the TransactionWorks database schema version matches
that required by the Transaction Analyzer.
logger_db_schema_version
Schema version for the TransactionWorks database that the Transaction
Analyzer requires.
TWORKS/TA 655.001
49
© 1998-2016 Nastel Technologies, Inc.
Chapter 6: TA Metrics
AutoPilot TransactionWorks TA
6.3 HopStats
Hop Statistics contain metrics for specific steps along the route of transactions. The statistics are
aggregated by various categories. The Custom category contains the user-defined aggregation specified
in the Custom Hop Categories property.
Figure 6-3. Transaction Analyzer HopStats Metrics
© 1998-2016 Nastel Technologies, Inc.
50
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 6: TA Metrics
Each Hop Statistics entry is broken down into three parts:
 msg_stats – statistics related to the messages observed at each step. (See Table 6-3.)
 opr_stats – statistics related to the individual operations at each step, aggregated by operation
type. (See Table 6-4.)
 opr_summary – summary level operation statistics for all operations observed. (See Table 6-5.)
Table 6-3. Facts Published by TA: HopStats/msg_stats
Metric
Description
average_msg_age_msec
Average time messages spent waiting to be read in milliseconds
average_msg_size_bytes
Average message size in bytes
maximum_msg_age_msec
Longest time a message spent waiting to be read in milliseconds
maximum_msg_size_bytes
Size of largest message in bytes
minimum_msg_age_msec
Shortest time a message spent waiting to be read in milliseconds
minimum_msg_size_bytes
Size of smallest message in bytes
recv_volume_bytes
Total amount of message data received in bytes
send_volume_bytes
Total amount of message data sent in bytes
total_msg_age_msec
Total time messages spent waiting to be read in milliseconds
total_msg_volume_bytes
Total amount of message data in bytes
total_msgs_recv_sent
Total number of messages processed
total_recv_msgs
Total number of messages sent
total_send_msgs
Total number of messages received
Table 6-4. Facts Published by TA: HopStats/opr_stats
Metric
Description
average_op_time_msec
Average operation execution time in milliseconds
last_op_comp_code
Last completion code returned by operation
last_op_reason
Last reason code returned by operation
total_op_count
Total number of operations observed
total_op_time_msec
Total operation execution time in milliseconds
TWORKS/TA 655.001
51
© 1998-2016 Nastel Technologies, Inc.
Chapter 6: TA Metrics
AutoPilot TransactionWorks TA
Table 6-5. Facts Published by TA: HopStats/opr_summary
Metric
Description
average_op_time_msec
Average operation execution time in milliseconds
average_wait_time_msec
Average time spent waiting for messages in milliseconds
fail_op_count
Total number of operations that failed
last_fail_op_reason
Reason for last failed operation
last_op_comp_code
Last completion code returned by operation
last_op_reason
Last reason code returned by operation
maximum_op_time_msec
Time of longest operation execution in milliseconds
maximum_wait_time_msec
Longest time spent waiting for message in milliseconds
minimum_op_time_msec
Time of longest operation execution in milliseconds
minimum_wait_time_msec
Shortest time spent waiting for message in milliseconds
total_op_count
Total number of operations observed
total_op_time_msec
Total time of operation execution in milliseconds
total_wait_time_msec
Total time spent waiting for message in milliseconds
Table 6-6. Facts Published by TA: HopStats Generic
Metric
Description
since_last_reset_sec
Number of seconds since the HopStats facts were reset
© 1998-2016 Nastel Technologies, Inc.
52
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 6: TA Metrics
6.4 ProbeStats
ProbeStats contain:
 Analyzed statistics about the performance of the Transaction Analyzer itself, providing
information about the volume of probe messages being received
 Generic statistics about the data received from the probes, aggregated by host and probe type.
 Performance statistics for processing transaction message payloads.
 Probe runtime statistics, providing information about the function and performance of the probe.
These statistics are computed and reported by the probes themselves.
Figure 6-4. Transaction Analyzer ProbeStats Metrics
TWORKS/TA 655.001
53
© 1998-2016 Nastel Technologies, Inc.
Chapter 6: TA Metrics
AutoPilot TransactionWorks TA
Table 6-7. Facts Published by TA: ProbeStats
Metric
Description
probe_http_connections
Number of current HTTP connections. Only displayed if
Enable HTTP Listener is set. (See Table 5-8.)
probe_message_bytes_pending
Total size of all probe messages queued up waiting for
processing in bytes
probe_messages_dropped
Total number of probe messages dropped due to in-memory
queue and disk-based overflow store being full
probe_messages_pending
Number of probe messages queued up waiting for processing
probe_messages_pending_limit
Configured limit on size of in-memory probe message queue
(value of Pending Messages Limit. (See Table 5-5.)
probe_messages_received
Total number of probe messages received
probe_messages_statistics_bytes
Total size of all probe statistics messages processed in bytes
probe_messages_statistics_failed
Total number of probe statistics messages that failed to be
processed
probe_messages_statistics_last_time
Last date/time that a probe statistics message was received
probe_messages_statistics_max_bytes
Size of largest proge statistics message processed in bytes
probe_messages_statistics_process_time_msec
Total time to process all probe statistics messages in
milliseconds
probe_messages_statistics_processed
Total number of probe statistics messages processed
probe_messages_statistics_skipped
Total number of probe statistics messages skipped
probe_messages_tracking_bytes
Total size of all probe tracking messages processed in bytes
probe_messages_tracking_db_error
Total number of database errors saving probe tracking
messages
probe_messages_tracking_db_insert_time_mse
c
Total time to write probe tracking message records to the
database in milliseconds
probe_messages_tracking_db_inserts
Total number of probe tracking message records written to
database
probe_messages_tracking_failed
Total number of probe tracking messages that failed to be
processed
probe_messages_tracking_failed_luws
Total number of failed LUWs reported in probe tracking
messages
probe_messages_tracking_failed_operations
Total number of failed operations reported in probe tracking
messages
probe_messages_tracking_last_time
Last date/time a probe tracking messages was processed
probe_messages_tracking_max_bytes
Size of largest probe tracking message in bytes
probe_messages_tracking_max_operations
Maximum number of operations reported in a single probe
tracking message
probe_messages_tracking_max_tran_msg_size
Maximum transaction message payload size reported in a
single probe tracking message in bytes
probe_messages_tracking_max_tran_msgs
Maximum number of transaction message payloads reported
in a single probe tracking message
probe_messages_tracking_min_tran_msg_size
Minimum transaction message payload size reported in a
single probe tracking message in bytes
© 1998-2016 Nastel Technologies, Inc.
54
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 6: TA Metrics
Table 6-7. Facts Published by TA: ProbeStats
Metric
Description
probe_messages_tracking_parse_time_msec
Total time to process all probe tracking messages
probe_messages_tracking_parsed
Total number of probe tracking messages parsed (but not yet
written to database)
probe_messages_tracking_processed
Total number of probe tracking messages processed (both
parsed and written to database)
probe_messages_tracking_skipped
Total number of probe tracking messages skipped
probe_messages_tracking_total_luws
Total number of LUWs reported in all probe tracking
messages
probe_messages_tracking_total_operations
Total number of operations reported in all probe tracking
messages
probe_messages_tracking_total_tran_msgs
Total number of transaction message payloads reported in all
probe tracking messages
probe_messages_tracking_total_tran_msgs_siz
e
Total size of all transaction message payloads reported in all
probe tracking messages in bytes
probe_msg_overflow_bytes
Total size of all probe messages in the overflow store. Only
displayed if Enable Pending Messages Overflow is set. (See
Table 5-5.)
probe_msg_overflow_bytes_limit
Configured limit on total size of all probe messages in the
overflow store in bytes (value of Pending Messages Overflow
Size Limit). A value of 0 implies no limit. Only displayed if
Enable Pending Messages Overflow is set. (See Table 5-5.)
probe_msg_overflow_count
Total number of probe messages that are in the overflow
store. Only displayed if Enable Pending Messages Overflow
is set. (See Table 5-5.)
probe_msg_overflow_ins_time_msec
Total time in milliseconds spent inserting messages into the
overflow store. Only displayed if Enable Pending Messages
Overflow is set. (See Table 5-5.)
probe_msg_overflow_inserts
Total number of messages inserted into the overflow store.
Only displayed if Enable Pending Messages Overflow is set.
(See Table 5-5.)
probe_msg_overflow_limit
Configured limit on total number of probe messages that are
in the overflow store (value of Pending Messages Overflow
Limit). A value of 0 implies no limit. Only displayed if
Enable Pending Messages Overflow is set. (See Table 5-5.)
probe_stats_publish_rate_sec
Configured rate at which probe statistics are published (value
of Probe Runtime Statistics Interval. (See Table 5-13.)
probe_tcp_connections
Number of current probe TCP connections. Only displayed if
Enable TCP Listener is set. (See Table 5-15.)
since_last_reset_sec
Number of seconds since the ProbeStats facts were reset
HTTP_Connections
Contains a list of active probe HTTP Connections. Only
displayed if Enable HTTP Listener and Publish HTTP
Connection List are set. (See Table 5-8.)
TCP_Connections
Contains a list of active probe TCP connections. Only
displayed if Enable TCP Listener and Publish TCP
Connection List are set. (See Table 5-16.)
TWORKS/TA 655.001
55
© 1998-2016 Nastel Technologies, Inc.
Chapter 6: TA Metrics
AutoPilot TransactionWorks TA
In addition to the above statistics about the performance of the analyzer in processing data sent by the
probes, there are also groups under ProbeStats representing the runtime statistics reported by each probe,
if Publish Probe Runtime Statistics is enabled. (See Table 5-15.) The hierarchy for these statistics is
either host name followed by probe type, or probe type followed by host name, based on the value of
Probe Runtime Statistics Grouping. (See Table 5-15.) The contents of these statistics are probespecific and differ by probe type. See the user guide for each specific probe for a description of the
reported runtime statistics. However, there are some generic statistics collected by the analyzer that it
aggregates based on host and probe type. These are the facts that start with “probe_message_statistics_”
and “probe_messages_tracking_” described in the above table.
The MessagePayloads fact group contains statistics about the Analyzer’s processing of transaction
message payloads.
Figure 6-5. Transaction Analyzer ProbeStats/Message Payloads
Table 6-8. Probe-specific Facts Published by TA: ProbeStats/MessagePayloads
Metric
Description
msg_payloads_bytes_pending
Total size of all transaction message payloads queued up
waiting for processing in bytes
tran_msg_payloads_db_error
Total number of transaction message payloads that encountered
errors saving to database.
tran_msg_payloads_dropped
Total number of transaction message payloads dropped due to
in-memory queue and disk-based overflow store being full
tran_msg_payloads_max_size_bytes
Maximum size of a transaction message payload in bytes
tran_msg_payloads_min_size_bytes
Minimum size of a transaction message payload in bytes
tran_msg_payloads_overflow_bytes
Total size of all transaction message payloads in the overflow
store. Only displayed if Enable Pending Message Payloads
Overflow is set. (See Table 5-5.)
© 1998-2016 Nastel Technologies, Inc.
56
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 6: TA Metrics
Table 6-8. Probe-specific Facts Published by TA: ProbeStats/MessagePayloads
Metric
Description
tran_msg_payloads_overflow_bytes_limit
Configured limit on total size of all transaction message
payloads in the overflow store (value of Pending Message
Payloads Overflow Size Limit). A value of 0 implies no limit.
Only displayed if Enable Pending Message Payloads
Overflow is set. (See Table 5-5.)
tran_msg_payloads_overflow_count
Total number of transaction message payloads that are in the
overflow store. Only displayed if Enable Pending Message
Payloads Overflow is set. (See Table 5-5.)
tran_msg_payloads_overflow_ins_time_msec
Total time in milliseconds spent inserting transaction message
payloads into the overflow store. Only displayed if Enable
Pending Message Payloads Overflow is set. (See Table 5-5.)
tran_msg_payloads_overflow_inserts
Total number of transaction message payloads inserted into the
overflow store. Only displayed if Enable Pending Message
Payloads Overflow is set. (See Table 5-5.)
tran_msg_payloads_overflow_limit
Configured limit on total number of transaction message
payloads that are in the overflow store (value of Pending
Message Payloads Overflow Limit). A value of 0 implies no
limit. Only displayed if Enable Pending Message Payloads
Overflow is set. (See Table 5-5.)
tran_msg_payloads_pending
Number of transaction message payloads queued up waiting for
processing
tran_msg_payloads_pending_limit
Configured limit on size of in-memory transaction message
payloads queue (value of Pending Message Payloads Limit.
(See Table 5-5.)
tran_msg_payloads_received
Total number of transaction message payloads received
tran_msg_payloads_total_inserts
Total number of transaction message payloads inserted into
database
tran_msg_payloads_total_insert_bytes
Total number of transaction message payload bytes inserted
into database
tran_msg_payloads_total_insert_time
Total time in milliseconds to insert transaction message
payloads
TWORKS/TA 655.001
57
© 1998-2016 Nastel Technologies, Inc.
Chapter 6: TA Metrics
AutoPilot TransactionWorks TA
6.5 Tracking
Transaction statistics are a measure of the transaction metrics for the entire network. It uses the same
facts as TransactionStats. (Refer to Table 6-12, Facts Published by TA: TransactionStats.)
Figure 6-6. Transaction Analyzer Tracking Metrics
© 1998-2016 Nastel Technologies, Inc.
58
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
6.5.1
Chapter 6: TA Metrics
Tracking Violation
It the Transaction Analyzer has been configured to publish transaction violation details (see Tracking tab,
Figure 5-21) data for individual transactions that do not appear to have completed successfully and are not
still in flight are also displayed. Entries are grouped by the transaction status. Individual transactions are
displayed as <TransactionPath>_<TransactionTag>. For each transaction, statistics are
published for:
 The transaction itself

For each Transaction Group the transaction is a member of
o Within each transaction group, statistics for each milestone in the transaction group
Figure 6-7. Transaction Analyzer Tracking Violation Metrics
TWORKS/TA 655.001
59
© 1998-2016 Nastel Technologies, Inc.
Chapter 6: TA Metrics
AutoPilot TransactionWorks TA
Table 6-9. Facts Published by TA: Tracking Violation
Metric
Description
applications
Comma-separated list of applications involved in this transaction
duration_msec
Total elapsed time of the transaction, in milliseconds
last_update
Time last transaction was updated
luw_count
Total number of logical units of work (LUW) involved in this transaction
message_count
Total number of distinct messages involved in this transaction
operation_count
Total number of operations involved in this transaction
resource_managers
Comma-separated list of all resource managers involved in this transaction
resource_mgr_types
Comma-separated list of all resource manager types involved in this
transaction
resource_types
Comma-separated list of all resource types involved in this transaction
resources
Comma-separated list of all resources involved in this transaction
servers
Comma-separated list of all servers involved in this transaction
total_luw_time_msec
Total elapsed time, including idle time, of all units of work in transaction in
milliseconds
total_msg_age_msec
Total time all messages involved in transaction spent waiting in a resource
to be processed in milliseconds
transaction_end_time
Date/time transaction ended
transaction_start_time
Date/time transaction started
transaction_status
Status of transaction
transaction_tag
Unique identifier assigned to transaction
users
Comma-separated list of all users involved in this transaction
workload_msec
Total execution time of all units of work involved in transaction in
milliseconds
Table 6-10. Facts Published by TA: Tracking Violation – Transaction Group
Metric
Description
defined_sla_msec
Specified SLA duration from transaction group definition in milliseconds.
Only displayed if SLA is not an absolute time.
defined_sla_time
Specified SLA time from transaction group definition, as a specific number
of days and time of day. Only displayed if SLA is an absolute time.
sla_status
SLA status of transaction, either “Missed SLA” if transaction missed its
defined SLA, or “Complete” if it did not miss SLA deadline.
transaction_group
Name of transaction group
transaction_sla_time
Date/time that transaction’s SLA expires (date/time by which is should
complete based on SLA definition)
transaction_tag
Unique identifier assigned to transaction
© 1998-2016 Nastel Technologies, Inc.
60
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 6: TA Metrics
Table 6-11. Facts Published by TA: Tracking Violation – Transaction Group – Milestone
Metric
Description
milestone
Name of milestone.
milestone_elapsed_start_usec
Elapsed time milestone occurred after the start of the transaction in
microseconds. Only displayed if milestone has been observed.
milestone_is_end
Indicates if milestone is an End milestone.
milestone_is_required
Indicates if milestone is required.
milestone_observed
Indicates if milestone has been observed.
milestone_prior
Name of prior milestone. Only displayed if milestone has a defined prior
milestone.
milestone_prior_time_usec
Elapsed time milestone occurred after the occurrence of the previous
milestone. Only displayed if milestone the milestone has occurred and
has a defined prior milestone.
milestone_sla_status
The milestone SLA status, based on the milestone’s SLA definition either
“Missed SLA” if milestone missed its defined SLA, or “Complete” if it
did not miss SLA deadline. Only displayed if the milestone has occurred
and has a defined prior milestone.
milestone_sla_usec
The defined SLA for the milestone. Only displayed if the milestone has
occurred and has a defined prior milestone.
milestone_time
The date/time the milestone was observed. Only displayed if milestone
has been observed.
transaction_group
Name of transaction group
transaction_tag
Unique identifier assigned to transaction
TWORKS/TA 655.001
61
© 1998-2016 Nastel Technologies, Inc.
Chapter 6: TA Metrics
AutoPilot TransactionWorks TA
6.6 TransactionStats
TransactionStats are analyzed statistics of transaction data as it flows through the network. The facts
published in this category are the statistics for individual transactions, which are considered to be groups
of message processing units (called logical units of work, or LUWs) that share a common message set.
Statistics are maintained in a number of categories and are summarized based on the publishing rate and
reset based on the reset rate. (See Statistics tab, Figure 5-16.)
The following TransactionStats facts are summarizations that are available.










Application – summarization by application name. Useful to understand the workload of a
specific application. Only displayed if Publish Transaction Statistics Level is set to “Full”.
(See Table 5-13.)
Milestone – summarization by milestone. Useful for determining the workload of key
transaction components.
Resource – summarization by resource across the entire network. Useful for determining the
total workload for a given resource. Only displayed if Publish Transaction Statistics Level is
set to “Full”. (See Table 5-13.)
ResourceManager – summarization by resource manager across the entire network. Useful for
determining the total workload for a given resource manager. Only displayed if Publish
Transaction Statistics Level is set to “Full”. (See Table 5-13.)
ResourceManagerType – summarization by type of resource manager across the entire network.
Useful for determining the total workload by type of resource manager. Only displayed if
Publish Transaction Statistics Level is set to “Full”. (See Table 5-13.)
ResourceType – summarization by resource type. Useful for determining the workload for a
type of resource. Only displayed if Publish Transaction Statistics Level is set to “Full”. (See
Table 5-13.)
Server – summarization by server. Useful when multiple resource managers are active on the
same server to see the total workload on that server. Only displayed if Publish Transaction
Statistics Level is set to “Full”. (See Table 5-13.)
TransactionGroup – summarization by transaction group definition. Useful for determining
workload of specific classes of transactions.
TranStatus – summarization by transaction status. Useful in determining the workload by status
of transaction.
User – summarization by users associated with each transaction. Useful to identify the workload
associated with a given user. Only displayed if Publish Transaction Statistics Level is set to
“Full”. (See Table 5-13.)
© 1998-2016 Nastel Technologies, Inc.
62
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 6: TA Metrics
Figure 6-8. TransactionStats Metrics
TWORKS/TA 655.001
63
© 1998-2016 Nastel Technologies, Inc.
Chapter 6: TA Metrics
AutoPilot TransactionWorks TA
Table 6-12. Facts Published by TA: TransactionStats
Metric
Description
average_duration_msec
Average time in milliseconds that a transaction took to execute
average_luw_time_msec
Average elapsed time, including idle time, in milliseconds, that a logical unit
of work took to execute
average_msg_age_msec
Average time in milliseconds that a message was waiting to be processed
maximum_duration_msec
Maximum time in milliseconds that a transaction took to execute
maximum_luw_time_msec
Maximum elapsed time, including idle time, in milliseconds that a logical
unit of work took to execute
maximum_msg_age_msec
Maximum time in milliseconds that a message was waiting to be processed
minimum_duration_msec
Minimum time in milliseconds that a transaction took to complete
minimum_luw_time_msec
Minimum elapsed time, including idle time, in milliseconds that a logical
unit of work took to execute
minimum_msg_age_msec
Minimum time in milliseconds that a message was waiting to be processed
total_failed
Total number of transactions that failed to execute due to a failed/rolledback unit of work
total_in_progress
Total number of transactions in flight
total_missed_sla
Total number of transactions that did not complete with their configured
SLA interval as defined by the transaction group(s) that the transactions
belong to
total_observed
Total number of transactions detected
total_success
Total number of transactions completed for which no errors were detected.
© 1998-2016 Nastel Technologies, Inc.
64
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 7: Database Configuration
Chapter 7: Database Configuration
7.1 Database Configuration Tables
Transaction Analyzer tables must be created manually by using the SQL scripts provided. There are three
classes of tables:



Reference – static tables that define the valid set of values for specific entry types
Data – stores the raw transaction and application data received from the probes
Analysis – stores the results of analyzing the raw transaction and application data.
NOTE:
7.1.1
Data definition SQL scripts can be found under [AUTOPILOT_HOME]/sql-scripts after
installation of TA Plug-in.
Reference Tables
Table 7-1. Data Definition of Reference Tables
Field
Description
Type
ref_id
Numeric value for reference item
INTEGER
ref_name
Text value for reference item
VARCHAR(64)
7.1.1.1 Message Formats
Table 7-2. ref_msg_formats
ID
Name
0
Unknown
1
WMQ Admin
2
WMQ CICS
3
WMQ Cmd1
4
WMQ Cmd2
5
WMQ Dead
6
WMQ DH
7
WMQ Embedded PCF
8
WMQ Event
9
WMQ IMS
10
WMQ IMS Vstring
11
WMQ MDE
12
WMQ PCF
13
WMQ RMH
14
WMQ RFH
15
WMQ RFH2
16
WMQ String
17
WMQ Trigger
TWORKS/TA 655.001
65
© 1998-2016 Nastel Technologies, Inc.
Chapter 7: Database Configuration
AutoPilot TransactionWorks TA
Table 7-2. ref_msg_formats
ID
Name
18
WMQ WIH
19
WMQ XQH
20
JMS Generic Message
21
JMS Test Message
22
JMS Bytes Message
23
JMS Object Message
24
JMS Map Message
25
JMS Stream Message
26
SQL Command
27
Text
28
Binary
29
XML
30
FIX
31
SWIFT
32
Object Instance
7.1.1.2 Message Types
Table 7-3. ref_msg_types
ID
Name
0
Unknown
1
Request
2
Reply
4
Report
8
Datagram
12
Acknowledgement
© 1998-2016 Nastel Technologies, Inc.
66
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 7: Database Configuration
7.1.1.3 Transport Types
Table 7-4. ref_transport_types
ID
Name
0
Unknown
1
JMS
2
TIBCO
3
TIBCO RV
4
WMQ
5
SQL
6
HTTP
7
HTTPS
8
SSL
9
TCP
10
UDP
11
SMTP
12
RMI
13
SOAP
14
FILE
15
DNET
7.1.1.4 Logical Unit of Work (LUW) Types
Table 7-5. ref_luw_types
ID
Name
0
Unknown
1
Producer
2
Processor
3
Consumer
7.1.1.5 Logical Unit of Work (LUW) Statuses
Table 7-6. ref_luw_statuses
ID
Name
0
Unknown
1
Begin
2
Commit
3
Rollback
TWORKS/TA 655.001
67
© 1998-2016 Nastel Technologies, Inc.
Chapter 7: Database Configuration
AutoPilot TransactionWorks TA
7.1.1.6 API Operation Types
Table 7-7. ref_api_types
ID
Name
0
Other
1
Start
2
Open
3
Send
4
Receive
5
Close
6
End
7
Inquire
8
Set
9
Call
10
URL
11
Browse
7.1.1.7 Resource Manager Types
Table 7-8. ref_res_mgr_types
ID
Name
0
Unknown
1
Application Server
2
Database Server
3
Standalone Server
4
Messaging Server
5
CICS Region
© 1998-2016 Nastel Technologies, Inc.
68
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 7: Database Configuration
7.1.1.8 Resource Types
Table 7-9. ref_res_types
ID
Name
0
Unknown
1
WMQ Queue Manager
2
WMQ Queue
3
WMQ Channel
4
Database
5
File
6
JMS Topic
7
JMS Queue
8
Java Runtime
9
C Runtime
10
DNET Runtime
11
OS Runtime
12
Network
13
Web Application
14
WMQ Topic
15
Journal
16
Program
17
Partition
18
CORBA Object
19
ENQ Model
20
Map
21
Portal Application
22
Web Service
23
MSMQ Queue
24
JMS Destination
TWORKS/TA 655.001
69
© 1998-2016 Nastel Technologies, Inc.
Chapter 7: Database Configuration
AutoPilot TransactionWorks TA
7.1.1.9 Property Types
Table 7-10. ref_property_types
ID
Name
1
Total Memory
2
Free Memory
3
Used Memory
4
CPU Percent Usage
5
Memory Percent Usage
6
CPU Usage Cycles
7
I/O Reads
8
I/O Writes
9
I/O Read Rate
10
I/O Write Rate
11
TrueSight Trace ID
7.1.1.10 Transaction Status Types
Table 7-11. ref_tran_status_types
ID
Name
0
Unknown
1
Complete
2
Failed
3
Missed SLA
4
In Progress
7.1.1.11 Completion Code Types
Table 7-12. ref_op_completion_codes
ID
Name
0
Succeeded
1
Warning
2
Failed
© 1998-2016 Nastel Technologies, Inc.
70
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 7: Database Configuration
7.1.1.12 Operation Severity Levels
Table 7-13. ref_operation_severities
ID
Name
0
Unspecified
1
Trace
2
Debug
3
Info
4
Success
5
Warning
6
Error
7
Failure
8
Critical
9
Fatal
10
Halt
TWORKS/TA 655.001
71
© 1998-2016 Nastel Technologies, Inc.
Chapter 7: Database Configuration
7.1.2
AutoPilot TransactionWorks TA
Data Tables
7.1.2.1 Servers
List of all servers taking part in transaction processing. A server represents a physical or virtual node
within a transaction processing network that hosts transaction processing activity.
Table 7-14. Data Definition of tw_servers
Field
Description
Type
server_signature
Unique identifier
VARBINARY(16)
server_name
Server name
VARCHAR(256)
server_ip
Server IP address
VARCHAR(64)
server_os
Name and version of operating system running on server
VARCHAR(256)
server_cpu_count
Maximum number of CPU cores, as reported by probes
INTERGER
server_mips_count
Maximum number of MIPS, as reported by probes
INTERGER
7.1.2.2 Client Users
List of all Web client users taking part in transaction processing.
Table 7-15. Data Definition of tw_client_users
Field
Description
Type
client_user_signature
Unique identifier
VARBINARY(16)
luw_signature
Identifer for unit of work user is associated with
VARBINARY(16)
client_user_name
Name of client user as reported by underlying transport
(e.g., HTTP request user name)
VARCHAR(64)
client_user_remote_addr
IP address from which client user initiated request
VARCHAR(256)
client_user_res_locator
Resource locator string (e.g., URL) user used to initiate
request
VACHAR(256)
client_user_request_time
Time request was received (including fractional seconds,
except for MySQL)
TIMESTAMP
client_user_request_time_usec
Fractional microsecond portion for time request was
received (MySQL only)
INTEGER
client_user_protocol
Protocol used to issue request
VACHAR(64)
client_user_res_params
Additional parameters supplied with request
VARCHAR(256)
client_user_referrer
Resource locator string from which this request was
initiated
VARCHAR(256)
client_user_remote_program
Name of program client user used to initiate request
VARCHAR(256)
client_user_remote_os
Name of the operation system client user is running
VARCHAR(64)
client_user_log_time
Time client user entry was recorded in the database
TIMESTAMP
© 1998-2016 Nastel Technologies, Inc.
72
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 7: Database Configuration
7.1.2.3 Applications
List of all applications taking part in transaction processing. An application represents a logical collection
of software components that perform a business function, running on a specific server.
Table 7-16. Data Definition of tw_applications
Field
Description
Type
appl_signature
Unique identifier
VARBINARY(16)
appl_name
Application name
VARCHAR(64)
server_signature
Identifier of the server the application is running on
VARBINARY(16)
appl_user
Name of the user under which application is running
VARCHAR(64)
appl_url
URL that application is processing requests for
VARCHAR(512)
7.1.2.4 Resource Managers
List of all resource managers taking part in transaction processing. A resource manager represents an
entity that is managing a collection of resources.
Table 7-17. Data Definition of tw_resource_mgrs
Field
Description
Type
res_mgr_id
Unique database identifier
INTEGER
res_mgr_name
Name of resource manager
VARCHAR(256)
res_mgr_type
Type of resource manager (from ref_res_mgr_types)
SMALLINT
server_signature
Identifier of server hosting resource manager
VARBINARY(16)
TWORKS/TA 655.001
73
© 1998-2016 Nastel Technologies, Inc.
Chapter 7: Database Configuration
AutoPilot TransactionWorks TA
7.1.2.5 Logical Units of Work (LUW)
List of all logical units of work taking part in transaction processing. A logical unit of work represents a
collection of operations and messages within a session that should be considered to be a single unit of
work (all or nothing property).
Table 7-18. Data Definition of tw_logical_unit_work
Field
Description
Type
luw_signature
Unique identifier assigned by Transaction Probe
VARBINARY(16)
appl_signature
Identifier of application that unit of work belongs to
VARBINARY(16)
res_mgr_signature
Identifier of resource manager unit of work is connected to
VARBINARY(16)
luw_type
Type of unit of work (from ref_luw_types)
SMALLINT
luw_status
Status of unit of work (from ref_luw_statuses)
SMALLINT
luw_appl_pid
Process ID of application executing unit of work
BIGINT
luw_appl_tid
Thread ID within application executing unit of work
BIGINT
luw_start_time
Time unit of work started
TIMESTAMP
luw_end_time
Time unit of work ended
TIMESTAMP
luw_log_time
Time database record was last updated
TIMESTAMP
luw_exception
Reason for LUW rollback
VARCHAR(512)
7.1.2.6 Messages
List of all messages involved in transaction processing. A message represents a physical message being
transported through the network.
Table 7-19. Data Definition of tw_messages
Field
Description
Type
msg_signature
Unique identifier for message
VARBINARY(16)
msg_transport_layer
Transport layer message was observed in (from
ref_transport_types)
SMALLINT
msg_tag
Label assigned to message by Transaction Probe
(distinct messages with the same label are
assumed to be part of the same transaction)
VARCHAR(256)
msg_size
Size of message, in bytes
INTEGER
msg_format
Message format (from ref_msg_formats)
SMALLINT
msg_type
Type of message (from ref_msg_types)
SMALLINT
msg_value
Value (generally a dollar amount or a resource
count) used to associate with a transaction.
VARCHAR(256)
msg_is_binary
Indication of whether message contents should
be considered as binary (otherwise, assumed to
be character)
TINYINT
msg_is_compressed
Indicates whether message contents have been
compressed
TINYINT
msg_data_size
Size of uncompressed message contents, in bytes
INTEGER
msg_data
Message contents
BLOB
© 1998-2016 Nastel Technologies, Inc.
74
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
7.1.2.7
Chapter 7: Database Configuration
Operations
List of all operations involved in transaction processing. An operation represents a specific operation or
transport API method call.
Table 7-20. Data Definition of tw_operations
Field
Description
Type
luw_signature
Identifier for unit of work executing operation
VARBINARY(16)
msg_signature
Identifier of message being operated on
VARBINARY(16)
msg_transport_layer
Transport layer operation was observed in (from
ref_transport_types). Only valid for operations that are acting on
a message
SMALLINT
op_api_func
Name of operation or API method
VARCHAR(256)
op_api_type
Type of operation (from ref_api_types)
SMALLINT
op_api_cc
Completion code indicating execution status of operation (from
ref_op_completion_codes)
SMALLINT
op_api_rc
Return or reason code returned by operation or API method
INTEGER
op_start_time
Time operation started (including fractional seconds, except for
MySQL)
TIMESTAMP
op_start_time_usec
Microsecond portion of start time (MySQL only)
INTEGER
op_end_time
Time operation ended (including fractional seconds, except for
MySQL)
TIMESTAMP
op_end_time_usec
Fractional microsecond portion of end time (MySQL only)
INTEGER
op_resource
Name of resource being accessed
VARCHAR(256)
op_resource_type
Type of resource being accessed (from ref_res_types)
SMALLINT
op_user_name
Name of user that operation is executing under
VARCHAR(50)
op_elapsed_time_usec
Total execution time of operation
BIGINT
op_msg_age_usec
Total time message for receive operation was waiting to be
processed, in microseconds
BIGINT
op_idle_time_usec
Total time receive operation was waiting for a message to be
available, in microseconds
BIGINT
op_step
Sequence number of operation
INTEGER
op_level
Position on call stack of operation
INTEGER
op_exception
Message associated with exception thrown by operation
VARCHAR(512)
op_log_time
Time operation was recorded in database
TIMESTAMP
op_severity
Severity level associated with operation (from
ref_operation_severities)
SMALLINT
op_location
Identifies location where operation occurred (e.g., GPS
coordinates)
VARCHAR(64)
op_correlator
Label used to relate independent operations to join their
corresponding transactions into a single transaction.
VARCHAR(256)
TWORKS/TA 655.001
75
© 1998-2016 Nastel Technologies, Inc.
Chapter 7: Database Configuration
AutoPilot TransactionWorks TA
7.1.2.8 Properties
Maintains a set of execution or state properties associated with units of work.
Table 7-21. Data Definition of tw_properties
Field
Description
Type
luw_signature
Identifier for unit of work property is associated with
VARBINARY(16)
property_type
Type of property (from ref_property_types)
SMALLINT
property_value
Property value, represented as a character string
VARCHAR(256)
property_sample_time
Time property was observed or recorded (including
fractional seconds, except for MySQL)
TIMESTAMP
property_sample_time_usec
Microsecond portion of property time (MySQL only)
INTEGER
7.1.2.9 Transaction Group Definitions
Maintains transaction group definitions, which are used to determine what SLA values to assign to
transactions by applying the specified mask(s) to each hop in the transaction.
Table 7-22. Data Definition of tw_tran_groups
Field
Description
Type
tg_id
Unique database ID
INTEGER
tg_name
Name of transaction group
VARCHAR(256)
tg_server_str
Regular expression that defines which servers are part of
this transaction group
VARCHAR(256)
tg_application_str
Regular expression that defines which applications are part
of this transaction group
VARCHAR(256))
tg_res_mgr_str
Regular expression that defines which resource managers
are part of this transaction group
VARCHAR(256)
tg_res_mgr_type
Regular expression that defines which resource manager
types are part of this transaction group
VARCHAR(256)
tg_msg_format_str
Regular expression that defines which message formats are
part of this transaction group
VARCHAR(256)
tg_sla
SLA for this transaction group, in microseconds
BIGINT
tg_resource
Regular expression that defines which resources are part of
this transaction group
VARCHAR(256)
tg_res_type_str
Regular expression that defines which resource types are
part of this transaction group
VARCHAR(256)
tg_sla_is_absolute
Indicates if SLA is an absolute time (<> 0) or a relative
SLA offset from start of transaction (= 0)
SMALLINT
tg_sla_apply_cal
For absolute SLA, indicates whether list of holidays should
be checked to skip these days when determining SLA time
for transaction (<> 0)
SMALLINT
© 1998-2016 Nastel Technologies, Inc.
76
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 7: Database Configuration
7.1.2.10 Transaction Milestones
This table contains the Transaction Milestone definitions.
Table 7-23. Data Definition of tw_milestones
Field
Description
Type
ms_id
Unique database identifier
INTEGER
ms_name
Name of milestone
VARCHAR(64)
ms_desc
Label to use when displaying milestone in transaction
flow diagrams
VARCHAR(256)
ms_api_type
Type of operation for milestone
SMALLINT
ms_res_mgr
Resource Manager for milestone
VARCHAR(256)
ms_res_mgr_type
Type of Resource Manager for milestone
SMALLINT
ms_resource
Resource for milestone
VARCHAR(256)
ms_res_type
Type of Resource for milestone
SMALLINT
ms_application
Application name for milestone
VARCHAR(256)
ms_server
Server name for milestone
VARCHAR(256)
7.1.2.11 Transaction Group Milestones
This table contains the association of milestones to transaction groups.
Table 7-24. Data Definition of tw_transaction_analysis_filter
Field
Description
Type
tg_id
ID of transaction group
INTEGER
ms_id
ID of milestone
INTEGER
ms_flags
Flags defining attributes of milestones:
0x01 = required milestone
0x02 = start milestone
0x04 = end milestone
INTEGER
ms_prior_id
ID of prior milestone in expected occurrence of
milestones
INTEGER
ms_sla
SLA for this milestone in this group, in microseconds
BIGINT
ms_seq
Position in list of milestones
INTEGER
7.1.2.12 Transaction Correlators
This table contains a list of all correlators involved in each transaction.
Table 7-25. Data Definition of tw_tran_correlators
Field
Description
Type
tran_tag
Transaction identifier
BIGINT
op_correlator
Correlator
VARCHAR(256)
TWORKS/TA 655.001
77
© 1998-2016 Nastel Technologies, Inc.
Chapter 7: Database Configuration
AutoPilot TransactionWorks TA
7.1.2.13 Transaction Search Tags
This table contains a list of all search tags identified in each transaction.
Table 7-26. Data Definition of tw_tran_search_tags
Field
Description
Type
tran_tag
Transaction identifier
BIGINT
tran_search_tag
Search tag
VARCHAR(256)
7.1.3
Analysis Tables
7.1.3.1 Analysis Info
Maintains information about the general state of data analysis.
Table 7-27. Data Definition of tw_analysis_info
Field
Description
Type
analysis_phase
Analysis phase number, in form “XY” where X = phase number
and Y = subphase numbe
last_update
Time that the previous execution of this phase last completed
TIMESTAMP
phase_start
Start time for time interval analyzed during previous execution of
this phase
TIMESTAMP
phase_end
End time for time interval analyzed during previous execution of
this phase
TIMESTAMP
current_update
Time when the current execution of this phase started
TIMESTAMP
current_start
Start time for time interval being analyzed by current execution of
this phase
TIMESTAMP
current_end
End time for time interval being analyzed by current execution of
this phase
TIMESTAMP
7.1.3.2 Transaction Members
Groups together LUWs that are part of the same transaction.
Table 7-28. Data Definition of tw_tran_members
Field
Description
Type
tran_tag
Transaction identifier
BIGINT
luw_signature
Identifier for LUW
VARBINARY(16)
msg_signature
Identifier for message the LUW operated on
VARBINARY(16)
© 1998-2016 Nastel Technologies, Inc.
78
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 7: Database Configuration
7.1.3.3 Tagged Transaction Groups
Maps transactions to transaction groups.
Table 7-29. Data Definition of tw_tagged_tran_groups
Field
Description
Type
tran_tag
Transaction identifier
BIGINT
tg_id
Transaction group identifier
INTEGER
sla_time
SLA date/time for this transaction, based on transaction group
definition (date/time by which the transaction should complete)
TIMESTAMP
tran_status
Status of transaction with respect to the SLA for this transaction
group (from ref_tran_status_types)
SMALLINT
7.1.3.4 Transaction Metrics
This table contains various transaction metrics for each transaction by LUW relationship method.
Table 7-30. Data Definition of tw_transactions
Field
Description
Type
tran_tag
Transaction identifier
BIGINT
tran_status
Current status of the transaction (from ref_tran_status_types)
SMALLINT
workload
Total computation time of all LUWs in transaction (time LUWs
spent actually doing work)
BIGINT
op_count
Total number of operations in the transaction
INTEGER
tran_start_time
Time transaction started
TIMESTAMP
luw_count
Total number of LUWs in the transaction
INTEGER
msg_count
Total number of distinct messages involved in transaction
INTEGER
duration
Total time, in microseconds, that transaction took to complete
BIGINT
luw_elapsed_time
Total execution time of all LUWs in transaction, including any idle
time waiting for messages
BIGINT
total_message_age
Total time messages spent waiting for processing
BIGINT
last_update
Time transaction metrics were last update
TIMESTAMP
min_luw_start
Timestamp for start of the earliest LUW
TIMESTAMP
min_send_op
Timestamp for first send operation
TIMESTAMP
tran_end
Timestamp for end time of transaction
TIMESTAMP
recv_msg_count
Total number of unique messages received
INTEGER
send_msg_count
Total number of unique messages sent
INTEGER
sla_time
SLA date/time for this transaction, based on transaction group
definition (date/time by which the transaction should complete)
TIMESTAMP
TWORKS/TA 655.001
79
© 1998-2016 Nastel Technologies, Inc.
Chapter 7: Database Configuration
AutoPilot TransactionWorks TA
7.1.3.5 Transaction Applications
This table contains a list of all applications involved in each transaction.
Table 7-31. Data Definition of tw_tran_applications
Field
Description
Type
tran_tag
Transaction identifier
BIGINT
appl_signature
Application identifier
VARBINARY(16)
server_signature
Server identifier
VARBINARY(16)
workload
Workload attributed to application
BIGINT
7.1.3.6 Transaction Users
This table contains a list of all users involved in each transaction.
Table 7-32. Data Definition of tw_tran_users
Field
Description
Type
tran_tag
Transaction identifier
BIGINT
tran_user
User Name
VARCHAR(64)
server_id
Server identifier
VARBINARY(16)
workload
Workload attributed to user
BIGINT
7.1.3.7 Transaction Resource Managers
This table contains a list of all resource managers involved in each transaction.
Table 7-33. Data Definition of tw_tran_resource_mgrs
Field
Description
Type
tran_tag
Transaction identifier
BIGINT
res_mgr_signature
Resource manager identifier
VARBINARY(16)
workload
Workload attributed to resource manager
BIGINT
7.1.3.8 Transaction Resources
This table contains a list of all resources involved in each transaction.
Table 7-34. Data Definition of tw_tran_resources
Field
Description
Type
tran_tag
Transaction identifier
BIGINT
op_resource
Resource name
VARCHAR(256)
op_resource_type
Type of resource (from ref_res_types)
SMALLINT
workload
Workload attributed to resource
BIGINT
© 1998-2016 Nastel Technologies, Inc.
80
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 7: Database Configuration
7.1.3.9 Transaction Logical Units of Work (LUW)
This table contains a list of all LUWs involved in each transaction.
Table 7-35. Data Definition of tw_tran_luws
Field
Description
Type
tran_tag
Transaction identifier
BIGINT
luw_signature
LUW identifier
VARBINARY(16)
7.1.3.10 Transaction Messages
This table contains a list of all messages involved in each transaction.
Table 7-36. Data Definition of tw_tran_msgs
Field
Description
Type
tran_tag
Transaction identifier
BIGINT
msg_signature
Message identifier
VARBINARY(16)
op_api_type
Type of operation (from ref_api_types)
SMALLINT
7.1.3.11 Tagged Transaction Milestones
Maps transaction operations to milestones for a transaction.
Table 7-37. Data Definition of tw_tagged_tran_milestones
Field
Description
Type
tran_tag
Transaction identifier
BIGINT
tg_id
Transaction group identifier
INTEGER
ms_id
Milestone identifier
INTEGER
ms_time
Date/time milestone was observed
DATETIME
ms_time_usec
Microsecond portion of time milestone was observed
INTEGER
ms_time_prior_usec
Elapsed time between this milestone and its prior milestone, in
microseconds
BIGINT
ms_sla
SLA for this milestone in this group, in microseconds
BIGINT
ms_status
Status of milestone (from ref_tran_status_types)
SMALLINT
ms_time_start_usec
Elapsed time between this milestone and the start of the transaction,
in microseconds
BIGINT
TWORKS/TA 655.001
81
© 1998-2016 Nastel Technologies, Inc.
Chapter 7: Database Configuration
7.1.4
AutoPilot TransactionWorks TA
Administration Tables
7.1.4.1 Database Schema Version
This table contains the TransactionWorks database schema version.
Table 7-38. Data Definition of twadm_version
Field
Description
Type
major_version
Major schema version number
INTEGER
minor_version
Minor schema version number
INTEGER
build_number
Schema build number
INTEGER
stored_procs_revision
Revision number of stored procedures file last loaded
VARCHAR(32)
7.1.4.2 Database Schema Update History
This table contains the history of all updates made to the TransactionWorks database schema.
Table 7-39. Data Definition of twadm_update_history
Field
Description
Type
major_version
Major schema version number that update applies to
INTEGER
minor_version
Minor schema version number that update applies to
INTEGER
build_number
Schema build number that update applies to
INTEGER
update_script
Name of the SQL update script file
VARCHAR(256)
update_reason
Description of the update
VARCHAR(256)
© 1998-2016 Nastel Technologies, Inc.
82
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 8: Maintaining Collected Data
Chapter 8: Maintaining Collected Data
8.1 How Much Data to Keep
One of the most important aspects of TransactionWorks is managing the data that you keep. The amount
of data you keep will be directly related to the number of transactions you run and the operations
(tracking events) that you collect, and the amount of payload data that you retain. The total data size
required will be the amount of data collected for any given day times the amount of days that you keep
online. For example, if you run 100,000 transactions a day each doing 10 operations and you keep a
month worth of data; that would represent 3,000,000 transactions, 30,000,000 operations and the
associated data. This can be many GigaBytes or even TerraBytes of data. In order to maintain a
reasonable amount of storage and associated performance for the end user, the older data must be
regularly purged.
8.2 Purging Data
Purging is a long-running operation. It should be done using a daily or weekly procedure. There are
online management screens to purge data, but these should only be used for small amounts of data or
using the “quick purge” option which only marks the transactions for deletion, but does not free up the
space used by them.
There are 3 purging concepts to consider:
 Purge – Purges old data by using delete operations. This method can be run with analyzer and
applications active although some contention is possible and it is not recommended. Purge
operations can take significant time to complete due to logging and file operations. However
purge is transactional, meaning it can be interrupted and restarted right where it left off. It will
require periodic table reorganization to clean up fragmented space. Purge can be run under a
non-privileged ID since it just performs Select/Delete commands.
 Copy – Purges old data by using SQL options to copy the retained data to a new table. Please be
aware of space requirements; e.g.; if you copy 90% of the data, you will need room for 180% of
the data. Because it manipulates the tables, it can only be done when the analyzer and
applications are down. The performance benefits are significant and can be completed in minutes
compared to hours for the purge method. The copy method can also be done using multiple
threads which can reduce the time further. It does not require deep clean since copy will only
copy good data so anything out of sync is not copied forward. Tables are rebuilt every time it
runs so the need to do table reorganization is reduced. Copy requires an Admin ID that can run
Table commands such as Drop and Create. Table functions are not transactional, which means
if you cancel it or it fails, you must fix it before re-running it. You cannot just restart TA since
the tables are not necessarily in a state where it can be run. TA will not start if copy purge
did not complete successfully. (Refer to section 8.3.1 if your purge did not complete.)
 Deep Cleaning – In some cases, orphaned data can be left on the database. Since it is no longer
related to the base transactions, normal purging will not find the data. Deep cleaning identifies
the orphaned data but requires more complex queries. It should not normally be needed (default
is No), but should be done if the reported data does not seem to match the data in the database.
Using the copy method also removes most orphaned data.
TWORKS/TA 655.001
83
© 1998-2016 Nastel Technologies, Inc.
Chapter 8: Maintaining Collected Data
AutoPilot TransactionWorks TA
The procedure TWSP_PURGE_TRANS_BACKGROUND is used for purging and can be included in a
daily script (preferred) or invoked using dbmaint.
Example: CALL TWSP_PURGE_TRANS_BACKGROUND(30,'No','Purge',0)
The following four options are applicable:
 Number of days beyond which data is consider for purge. (Default is 30.) For example 30
means keep 30 days of data and purge anything older. This can be a fractional amount (0.50) and
is calculated as of the time that the purge runs (current time). That is, a value of 1 when running
a purge at 9:00 PM would purge anything older than 9:00 PM on the previous day.
 Deep Clean – Yes, No, Only. Controls whether to follow the purge operation by a deep
cleaning. This can require significant time to complete. (Yes = purge first, then deep clean, No =
purge, no deep clean, Only – does not purge, only perform deep clean.)
 Purge Mode – Purge, Copy, Test, or CopyIgnore. Refer to the explanation above for Purge and
Copy. Test simulates a purge but does not delete any data and publishes results in the history
tables. CopyIgnore bypasses checks for applications using the database for Copy to proceed.
 Number of transactions (Purge) to commit in a single unit of work for Purge. When running a
purge mode copy, controls how often commits are done. Larger numbers increase the load on
database logging resources but require more SQL calls. The default of 0 indicates that the purge
procedure should determine the best value.
OR
Number of parallel threads (Copy). When doing copy, this option determines how many
threads to use with Oracle databases.
NOTE:
The fourth parameter has quite different meaning depending on type of purge. In normal purge, it is
the number of deletes to commit at a time. This can help when doing a lot of data because it keeps
the commit size down but also if you have to restart, it has committed most of the work in flight. For
copy and Oracle, it allows for parallel execution. Primary for large tables, it can help, but each thread
only cuts off about 10% of the time. Don’t confuse them, if you specify 4 for normal purge, it will do a
commit every 4 deletes which isn’t very efficient. Default is 20,000 or 1 thread when left to 0 (which is
probably the best to do unless you know what to expect).
The results of the purge operation are stored in two database tables:

tbl_purge_status – shows the most recent purge operation timings. Contains the tables being
purged, the number of rows purged, and the amount of time taken.

tbl_purge_history_status – keeps a 30-day history of any purges ran. It includes the time,
options used and the number of transactions on the database before and after the purge.
Refer to section 8.3, Troubleshooting for more information about these tables.
8.2.1
Sample Purge Usage
CALL TWSP_PURGE_TRANS_BACKGROUND(30,'No','Purge',0)
30-day purge using delete with no deep cleaning at default commit frequency
CALL TWSP_PURGE_TRANS_BACKGROUND(30,'No','Copy',4)
30-day purge using copy with no deep cleaning using 4 threads
CALL TWSP_PURGE_TRANS_BACKGROUND(7,'Yes','Test',0)
7-day test purge including deep cleaning
© 1998-2016 Nastel Technologies, Inc.
84
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Chapter 8: Maintaining Collected Data
8.3 Troubleshooting
If purge is cancelled or stops before completion at some points, manual intervention to clean up tables and
processing may be required.
8.3.1
Incomplete Purge
When using a purge option purge, you can restart the purge where it left off. It will continue from the last
committed operation and go forward.
When using a copy option purge, some cleanup will be required since the table operations such are
renaming may be partially done. If you try to restart it in this mode, you will get the message “Prior
incomplete purge requires manual intervention”. The first step is to look at the tbl_purge_status table
which will have one row with a value of -999. This is the point that the purge was processing. You then
need to look for the tables that exist. In most cases, you should find a _new and _old tables. For
example, if it was purging tw_messages, you might see tw_messages_new and tw_messages_old. In
order to continue, you would need to rename tw_messages_old back to tw_messages. You then need to
alter the value in tbl_purge_status to 0. For example:
update tbl_purge_status set action_flag = 0 where action_flag = -999
You can restart the purge at this point.
8.3.2
Out of Space
If you run out of space on the database server, it is possible that there will not be sufficient storage to run
a purge. You either need to add additional space to the database or manually free up some space from
existing tables. The table with the biggest data is tw_messages which contains the message content. You
might start by deleting all messages greater than a certain size. For example:
delete from tw_messages where msg_data_size > 5000
Note that deleting rows may help alleviate the issue, but you may need to issue a database specific
command to release the actual space being used.
TWORKS/TA 655.001
85
© 1998-2016 Nastel Technologies, Inc.
Chapter 8: Maintaining Collected Data
AutoPilot TransactionWorks TA
This page intentionally left blank.
© 1998-2016 Nastel Technologies, Inc.
86
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Appendix A: References
Appendix A: References
A.1 Nastel Documentation
The following table provides a list of reference information required for using the AutoPilot
TransactionWorks TA.
Table A-1. Nastel Documentation
Document Number
(or higher)
Title
APODW ADM 653.001
AutoPilot On-Demand Web Installation and Administration Guide
APODW USR 653.001
AutoPilot On-Demand Web User’s Guide
AP/TPz 600.001
AutoPilot M6/Transaction Monitor Probe for WebSphere MQ (z/OS)
Installation and User Guide
M6/INS 623.001
Nastel AutoPilot M6 Installation Guide
M6/USR 623.001
Nastel AutoPilot M6 User’s Guide
M6WMQ/ADM 656.001
Nastel AutoPilot M6 for WebSphere MQ Administrator’s Guide
M6WMQ/INS 656.001
Nastel AutoPilot M6 for WebSphere MQ Installation Guide
M6WMQ/SM 656.001
Nastel AutoPilot M6 for WebSphere MQ Security Manager User’s Guide
M6/WMQ 600.002
WebSphere MQ Plug-in for AutoPilot M6
TW/E ADM 653.001
AutoPilot TransactionWorks Explorer Administrator’s Guide
TW/E USR 653.001
AutoPilot TransactionWorks Explorer User’s Guide
TWORKS/NP 650.001
AutoPilot TransactionWorks .NET Probe Installation and User’s Guide
TWORKS/P 650.002
AutoPilot TransactionWorks Java Probes Installation and User’s Guide
TWORKS/TP 653.001
AutoPilot TransactionWorks Probe for WebSphere MQ (Distributed)
Installation, Configuration and User’s Guide
TWORKS/WSz 650.003
AutoPilot TransactionWorks Probes for z/OS Installation and User’s
Guide
TWORKS/DFP 653.001
AutoPilot TransactionWorks Direct Feed Probe Installation and User’s
Guide
A.2 Other Documentation
See the Sun Microsystems JDBC Driver Web page for more information, documentation and reference
materials available from Sun, and links to various vendors.
http://servlet.java.sun.com/products/jdbc/drivers
TWORKS/TA 655.001
87
© 1998-2016 Nastel Technologies, Inc.
Chapter 8: Maintaining Collected Data
AutoPilot TransactionWorks TA
This page intentionally left blank.
© 1998-2016 Nastel Technologies, Inc.
88
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Appendix B: Conventions
Appendix B: Conventions
B.1 Typographical Conventions
Table B-1. Typographical Conventions
Convention
Description
Blue/Underlined
Used to identify links to referenced material or websites.
Example: [email protected]
Bold Print
Used to identify topical headings, glossary entries, and toggles
or buttons used in procedural steps.
Example: Click EXIT.
Italic Print
Used to identify titles, menus, screen names, user inputs, or
other category.
Monospaced Bold
Used to identify keystrokes/data entries, file names, directory
names, etc.
Monospaced Italic
Used to identify variables in an address location.
Example: [AUTOPILOT_HOME]\documents, where the
portion of the address within the brackets [ ] are variable.
Monospaced Text
Used to identify addresses, commands, scripts, etc.
Normal Text
Typically used for general text throughout the document.
Table Text
Table text is generally a smaller size to conserve space.
TWORKS/TA 655.001
89
© 1998-2016 Nastel Technologies, Inc.
Appendix B: Conventions
AutoPilot TransactionWorks TA
This page intentionally left blank.
© 1998-2016 Nastel Technologies, Inc.
90
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Glossary
Glossary
Application: A logical collection of software components that perform a business function, running on a
specific server.
AutoPilot M6: Nastel Technologies’ Enterprise Application Management Platform. AutoPilot M6 is
designed to monitor and control distributed IT services such as application servers, middleware, user
applications, workflow engines, brokers, Service Oriented Architecture (SOA) and Enterprise Service Bus
(ESB) based applications and their impact on business services.
AutoPilot M6 for WMQ: Nastel Technologies’ WebSphere MQ management solution. Re-designated
as M6 for WMQ with release 6.0, prior releases retain the AP-WMQ or MQControl trademark.
AutoPilot M6 Web: AutoPilot M6 Web is a browser-based interface that provides monitoring and
operational control over managed resources and applications. It allows users to monitor health, recover
from a failure, view historical performance graphs and visualize impacts of a failure.
AutoPilot M6/WebSphere Message Queue Integrator (AP/WMQI): Formerly AP/MQSI
AutoPilot/Message Tracking (AP/MT): Nastel’s AutoPilot/Message Tracking plug-in that enables
AutoPilot/IT to intercept message exits and forward the statistical data to an AutoPilot expert.
AutoPilot TransactionWorks (AP/TW): Nastel Technologies’ transaction and application performance
monitoring product.
AutoPilot/WebSphere (AP/WS): AutoPilot/WebSphere plug-into enables AutoPilot to monitor and
manage eBusiness applications for continuous operations in addition to its standard features.
BCI: See Byte Code Instrumentation
Binary Large Object (BLOB): A collection of binary data stored as a single entity in a database
management system. Blobs are typically images, audio or other multimedia objects, though sometimes
binary executable code is stored as a blob. Database support for blobs is not universal.
BLOB: See Binary Large Object.
BSV: See Business View.
Business Transaction: A collection of related transactions that comprise a user-defined business function
(e.g. purchase a book, return merchandize, purchase stock). Each of the business activities may be
comprised of various workloads.
Business View (BSV): A collection of rules that define a desired state of an eBusiness environment.
Business Views can be tailored to present information in the form most suited to a given user, as defined
by the user.
Byte Code Instrumentation (BCI): The process of adding small portions of Java byte code around
methods of a Java class. The added code performs tasks such as time spent or CPU utilization within the
monitored class.
CEP (Complex Event Processing) Server: A container that can host any number of AutoPilot services
such as experts, managers, policies, etc. (Called managed node prior to AutoPilot M6 Service Update 6.)
Client: Any programming component that uses the AutoPilot infrastructure; for example, the AutoPilot
Console.
Common Object Request Broker Architecture (CORBA): A standard defined by the Object
Management Group that enables software components written in multiple computer languages and
running on multiple computers to work together. It can be invoked from a Web browser using CGI
scripts or applets.
Composite Application: A collection of applications that collaborate or communicate with each other
(have related sessions).
Console: The console acts as the graphical interface for AutoPilot.
Contacts: A subordinate to a given Manager or Expert.
CORBA: See Common Object Request Broker Architecture.
TWORKS/TA 655.001
91
© 1998-2016 Nastel Technologies, Inc.
Glossary
AutoPilot TransactionWorks TA
Data Source Name (DSN): The logical name that is used by Open Database Connectivity (ODBC) to
refer to the drive and other information that is required to access data. The name is use by Internet
Information Services (IIS) for a connection to an ODBC data source, (Example: Microsoft SQL Server
database). The ODBC tool in Control Panel is used to set the DSN. When ODBC DSN entries are used
to store the connection string values externally, you simplify the information that is needed in the
connection string. This makes changes to the data source completely transparent to the code itself.
Data Space: A range of up to two gigabytes of contiguous virtual storage addresses that a program can
directly manipulate. Unlike an address space, a data space can hold only data; it does not contain
common areas or system data or programs.
Decision Support System (DSS): An AutoPilot-based service designed to monitor, store, and display any
event information generated by AutoPilot enabled middleware and applications.
Deploy: To put to use, to position for use or action.
Domain Server: A specialized managed node that maintains the directory of managed nodes, experts etc.
The domain server is also capable of hosting experts, managers etc
DSN: See Data Source Name.
DSS: See Decision Support System.
Event: An Event is something that happens to an object. Events are logged by AutoPilot and are
available for use by AutoPilot Policies or the user.
EVT: Event Log file extension (for example: sample.evt).
Expert: Services that monitor specific applications such as an applications server, Web server or specific
components within the applications (example, channels in MQSeries). Experts generate facts.
Fact: Single pieces of data that has a unique name and value. One or more facts are used to determine the
health of the object, application or server.
Graphical User Interface (GUI): A type of environment that represents programs, files, and options by
means of icons, menus, and dialog boxes on the screen. The user can select and activate these options by
pointing and clicking with a mouse or, often, with the keyboard. Because the graphical user interface
provides standard software routines to handle these elements and report the user's actions (such as a
mouse click on a particular icon or at a particular location in text, or a key press); applications call these
routines with specific parameters rather than attempting to reproduce them from scratch.
GUI: See Graphical User Interface.
HAQS: See High Availability Queuing Service.
Heap: In Java programming, a block of memory that the Java virtual machine uses at run time to store
Java objects. Java heap memory is managed by a garbage collector, which automatically de-allocates Java
objects that are no longer in use
High Availability Queuing Service (HAQS): A component of AutoPilot consisting of two policies that
provide automatic queue fail-over for WebSphere MQ applications, provide high availability of
WebSphere MQ resources such as queues and channels, and ensure automatic recovery of WebSphere
MQ channels.
IIS: See Internet Information Services.
Independent Software Vendor (ISV): A business term for companies specializing in making or selling
software, usually for niche markets.
Initial Program Load (IPL): The process of loading system programs and preparing a system to run
applications.
Interactive System Productivity Facility (ISPF): An IBM licensed program that serves as a full-screen
editor and dialog manager. Used for writing application programs. It provides a means of generating
standard screen panels and interactive dialogues between the application programmer and terminal user.
Internet Information Services (IIS): Microsoft's brand of Web server software, utilizing HTTP to
deliver World Wide Web documents. It incorporates various functions for security, allows CGI
programs, and also provides for Gopher and FTP services.
© 1998-2016 Nastel Technologies, Inc.
92
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Glossary
IPL: See Initial Program Load.
ISPF: See Interactive System Productivity Facility.
ISV: See Independent Software Vendor.
Java: A platform-independent, object-oriented programming language developed and made available by
Sun Microsystems.
Java Database Connectivity (JDBC): Provides universal data access from the Java programming
language. Using the JDBC 2.0 API, you can access virtually any data source, from relational databases to
spreadsheets and flat files. JDBC technology also provides a common base on which tools and alternate
interfaces can be built. The JDBC Test Tool that was developed by Merant and Sun Microsystems may
be used to test drivers, to demonstrate executing queries and getting results, and to teach programmers
about the JDBC API.
Java Developer’s Kit (JDK): A set of software tools developed by Sun Microsystems, Inc., for writing
Java applets or applications. The kit, which is distributed free, includes a Java compiler, interpreter,
debugger, viewer for applets, and documentation.
Java Management Extensions (JMX): An open technology for management and monitoring that can be
deployed wherever management and monitoring are needed. By design, this standard is suitable for
adapting legacy systems, implementing new management and monitoring solutions and plugging into
those of the future.
Java Messaging Service (JMS): a Java Message Oriented Middleware API for sending messages
between two or more clients.
Java Platform, Enterprise Edition (Java EE): The industry standard for developing portable, robust,
scalable and secure server-side Java applications. Building on the solid foundation of Java SE, Java EE
provides Web services, component model, management, and communications APIs that make it the
industry standard for implementing enterprise class service-oriented architecture (SOA) and Web 2.0
applications.
Java Naming and Directory Interface (JNDI): Unified interface to multiple naming and directory
services for applications based on Java technology.
Java Run-time Environment (JRE): The minimum core Java required to run Java programs.
Java Server Pages (JSP): Technology that enables rapid development of Web-based applications that
are platform independent. Java Server Pages technology separates the user interface from content
generation enabling designers to change the overall page layout without altering the underlying dynamic
content. Java Server Pages technology is an extension of the Java Servlet technology.
Java Virtual Machine (JVM): The “virtual” operating system that Java-written programs run. The JVM
is a hardware- and operating system-independent abstract computing machine and execution environment.
Java programs execute in the JVM where they are protected from malicious programs and have a small
compiled footprint.
JCL: See Job Control Language.
JDBC: See Java Database Connectivity.
JDK: See Java Developer's Kit.
JMS: See Java Messaging Service.
JMX: See Java Management Extensions.
JNDI: See Java Naming and Directory Interface.
Job Control Language (JCL): A control language that is used to identify a job to an operating system
and to describe the job’s requirements.
JRE: See Java Run-time Environment.
JSP: See Java Server Pages.
JVM: See Java Virtual Machine.
TWORKS/TA 655.001
93
© 1998-2016 Nastel Technologies, Inc.
Glossary
AutoPilot TransactionWorks TA
Logical Unit of Work (LUW): A collection of operations and messages within a session that should be
considered to be a single unit of work (all or nothing property). These are generally delimited by
BEGIN/COMMIT calls.
LUW: See Logical Unit of Work.
Managed Node: Containers that are capable of hosting any number of AutoPilot services, such as
experts, managers, policies etc.
Manager: Managers are the home or container for policies. All business views must reside on managers,
and manager must be deployed prior to deploying a business view or policy.
Message: A physical message being transported through the TPN.
Message-Oriented Middleware (MOM): A category of inter-application communication software that
relies on asynchronous message passing as opposed to a request/response metaphor.
Message Queue Interface (MQI): Part of IBM’s Networking Blueprint. It is a method of program-toprogram communication suitable for connecting independent and potentially non-concurrent distributed
applications.
MOM: See Message-Oriented Middleware.
MQI: See Message Queue Interface.
MQSeries: IBM’s message queuing product. Renamed by IBM as WebSphere MQ.
Naming Service: A common server records “names” of objects and associates them with references,
locations and properties.
Object Request Broker (ORB): In object-oriented programming, software that serves as an intermediary
by transparently enabling objects to exchange requests and responses.
ORB: See Object Request Broker.
Orbix: CORBA product distributed by IONA Technologies.
Package Manager: The command line utility that allows users to list, install, uninstall, verify, and update
AutoPilot installation on any Managed Node.
PKGMAN: See Package Manager Utility included in AutoPilot products.
Policy/Business Views: A collection of one or more sensors. Business views are used to visually present
the health and status of the different systems as well as automatically issue remedial actions.
Resource: An entity on which transactions are executed or a medium of exchange. Examples include
queue, DB table, file, JMS topic.
Resource Manager: An entity that is managing a collection of resources. Examples include a WMQ
Queue Manager, Application Server, Database Server.
Sensor: A rule that is used to determine the health of an object or application based on one or more facts.
Actions can then be issued, based on the health.
Server: A physical or virtual node within a TPN that hosts all transaction processing activity.
Service Level Agreement (SLA): A formal written agreement made between two parties: the service
provider and the service recipient. The SLA itself defines the basis of understanding between the two
parties for delivery of the service itself. The document can be quite complex, and sometimes underpins a
formal contract. The contents will vary according to the nature of the service itself, but usually includes a
number of core elements, or clauses.
Service-Oriented Architecture (SOA): An evolution of distributed computing and modular
programming. SOAs build applications out of software services. Services are relatively large,
intrinsically unassociated units of functionality, which have no calls to each other embedded in them.
They typically implement functionalities most humans would recognize as a service, such as filling out an
online application for an account, viewing an online bank statement, or placing an online book or airline
ticket order. Instead of services embedding calls to each other in their source code, protocols are defined
which describe how one or more services can talk to each other. This architecture then relies on a
business process expert to link and sequence services, in a process known as orchestration, to meet a new
or existing business system requirement.
© 1998-2016 Nastel Technologies, Inc.
94
TWORKS/TA 655.001
AutoPilot TransactionWorks TA
Glossary
Simple Mail Transfer Protocol (SMTP): A TCP/IP protocol for sending messages from one computer
to another on a network. This protocol is used on the Internet to route e-mail. See also communications
protocol, TCP/IP.
SLA: See Service Level Agreement.
SMTP: See Simple Mail Transfer Protocol.
SOA: See Service-Oriented Architecture.
TCP/IP: See Transmission Control Protocol/Internet Protocol.
Time Sharing Option (TSO): An option of the MVS operating system that provides interactive time
sharing from remote terminals.
TPN: See Transaction Processing Network.
Transaction: A group of activities targeted at achieving a common goal or a task. Collection of related
LUWs.
Transmission Control Protocol/Internet Protocol (TCP/IP): A protocol developed by the Department
of Defense for communications between computers. It is built into the UNIX system and has become the
de facto standard for data transmission over networks, including the Internet.
Transaction Processing Network (TPN): A collection of servers engaged in transaction processing
activity
TSO: See Time Sharing Option.
Virtual Machine: Software that mimics the performance of a hardware device, such as a program that
allows applications written for an Intel processor to be run on a Motorola chip. Also see Java Virtual
Machine.
WebLogic: A Java EE compatible application server platform which enables support for multiple
programming models, which includes advanced administration tools and is the ideal foundation for
Service Oriented Architecture (SOA).
WebSphere MQ: IBM’s message queuing product, formally known as MQSeries.
Websphere_MQ_Manager: A specialized manager capable of hosting one or more WebSphere MQ
specific policies, apart from the regular policies.
Wireless Application Protocol (WAP): An open global specification that is used by most mobile
telephone manufacturers. WAP determines how wireless devices utilize Internet content and other
services. WAP enables devices to link diverse systems contents and controls.
Write to Operator (WTO): An optional user-coded service that allows a message to be written to the
system console operator informing the operator of errors and unusual system conditions that may need to
be corrected.
WTO: See Write to Operator.
TWORKS/TA 655.001
95
© 1998-2016 Nastel Technologies, Inc.
Glossary
AutoPilot TransactionWorks TA
This page intentionally left blank.
© 1998-2016 Nastel Technologies, Inc.
96
TWORKS/TA 655.001
Index
memory ....................................................................... 19
C
CPU optimization ..............................................................20
P
D
probes ................................................................................ 5
purge data ........................................................................ 83
database
administration ..............................................................14
creating ........................................................................15
updating .......................................................................15
database configuration table
admistrative .................................................................82
analysis .........................................................................78
data ..............................................................................72
reference ......................................................................65
definitions ...........................................................................7
deploy expert ....................................................................23
distribution .........................................................................9
document history ................................................................1
R
README files ...................................................................... 2
Resource Center ................................................................. 3
S
[email protected] .......................................................... 3
system requirements...................................................... 2, 3
T
technical support ................................................................ 3
Transaction Analyzer
conponents .................................................................... 5
database configuration ................................................ 65
features ......................................................................... 5
transport options ........................................................... 5
transaction analyzer tables .............................................. 65
Transaction Monitor
deploy on multiple nodes ............................................ 43
deploying ..................................................................... 23
expert properties - About ............................................ 24
expert properties - Analysis ......................................... 25
expert properties - Database ....................................... 26
expert properties - Dependencies ............................... 28
expert properties - General ......................................... 24
expert properties - HTTP Options ................................ 30
expert properties - Logging ......................................... 31
expert properties - Options ......................................... 29
expert properties - Recording...................................... 34
expert properties - Restart-Recovery .......................... 35
expert properties - Security ......................................... 36
expert properties – Statistics-General ......................... 37
expert properties – Statistics-Hops ............................. 38
expert properties – Statistics-Probe ............................ 39
expert properties - TCP Options .................................. 39
expert properties – TNT Logging ................................. 40
expert properties - Trace Logging ................................ 41
expert properties - Tracking ........................................ 42
JDBC drives .................................................................. 13
TransactionWorks
architecture ................................................................... 5
Explorer ......................................................................... 5
Transaction Analyzer ..................................................... 5
Transaction Probes ........................................................ 5
F
feedback, user.....................................................................2
I
installation
as AutoPilot expert.......................................................10
requirements .................................................................9
J
Java run time environment .................................................2
JDBC drives........................................................................13
M
memory optimization .......................................................19
metrics
AnalyzerStats ...............................................................45
DBStats .........................................................................49
HopStats .......................................................................50
ProbeStats ....................................................................53
Tracking ........................................................................58
TransactionStats...........................................................62
N
Network Time Protocol .......................................................9
O
optimization
CPU...............................................................................20
TWORKS/TA 655.001
97
© 1998-2016 Nastel Technologies, Inc.
Index
AutoPilot TransactionWorks TA
This page intentionally left blank.
© 1998-2016 Nastel Technologies, Inc.
98
TWORKS/TA 655.001