WebSphere Studio Application Monitor V3.2 advanced usage guide

WebSphere Studio Application Monitor V3.2 advanced usage guide

The addition of WebSphere Studio Application Monitor to the Tivoli product portfolio enhanced Tivoli offerings for application management. WebSphere Studio Application Monitor enables comprehensive monitoring and management of J2EE-based applications with their back-end platforms. This IBM Redbooks...

Descripción completa

Detalles Bibliográficos
Autor principal: Darmawan, Budi (-)
Formato: Libro electrónico
Idioma:Inglés
Publicado: Austin, TX : IBM, International Technical Support Organization 2005.
Edición:1st ed
Colección:IBM redbooks.
Materias:
WebSphere.
Web servers > Computer programs.
Ver en Biblioteca Universitat Ramon Llull:https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009626927806719
Tabla de Contenidos:
  • Front cover
  • Contents
  • Notices
  • Trademarks
  • Preface
  • The team that wrote this redbook
  • Become a published author
  • Comments welcome
  • Chapter 1. Introducing application management
  • 1.1 Application management challenges
  • 1.2 Tivoli application management solution
  • 1.3 Project overview
  • 1.4 Project environment
  • Chapter 2. WebSphere Studio Application Monitor V3.2 overview
  • 2.1 WebSphere Studio Application Monitor overview
  • 2.2 Architecture and interconnection
  • 2.2.1 The managing server
  • 2.2.2 Data collector
  • 2.3 Supported environment
  • 2.4 Monitoring features
  • 2.4.1 Administration
  • 2.4.2 Availability
  • 2.4.3 Problem determination
  • 2.4.4 Performance analysis
  • 2.5 New features in V3.2
  • 2.5.1 Memory Leak Analysis
  • 2.5.2 Lock analysis
  • 2.5.3 WebSphere Portal Server metrics
  • 2.5.4 z/OS data collector changes
  • 2.5.5 WebSphere Application Server 6 Support
  • 2.5.6 Trap and alert management
  • 2.5.7 Help system is now using Eclipse InfoCenter format
  • 2.5.8 Performance enhancement
  • Chapter 3. Managing WebSphere Studio Application Monitor
  • 3.1 Overview
  • 3.2 Security considerations
  • 3.2.1 Node authentication default properties
  • 3.2.2 Users and roles
  • 3.3 Server management
  • 3.3.1 Server groups
  • 3.3.2 Data collector configuration
  • 3.3.3 Monitoring level considerations
  • 3.3.4 Sampling rate considerations
  • 3.4 Database management
  • 3.4.1 Migration from V3.1
  • 3.4.2 Database backup
  • 3.4.3 Maintaining database performance
  • 3.4.4 Cleaning up the database
  • 3.5 Managing server parameters
  • 3.5.1 Component heap sizes
  • 3.5.2 JDBC driver properties
  • 3.5.3 Kernel host properties
  • 3.5.4 Port definitions
  • 3.5.5 Essential managing server tools
  • 3.5.6 Split server installation
  • 3.6 Data collector administration
  • 3.6.1 Configuration files for data collector.
  • 3.6.2 Log-level settings
  • 3.6.3 Data collector log files cleanup
  • Chapter 4. \Managing production environment
  • 4.1 Production environment definition
  • 4.2 An operator's typical day
  • 4.3 Reports
  • 4.3.1 Report types
  • 4.3.2 Performing capacity planning
  • 4.3.3 Report usage
  • 4.4 Performance tuning
  • 4.4.1 Development perspective
  • 4.4.2 Administration perspective
  • 4.4.3 Runtime perspective
  • 4.5 Notification
  • 4.6 Working with composite applications
  • 4.6.1 CICS composite application
  • 4.6.2 IMS composite application
  • Chapter 5. Analyzing WebSphere application problems
  • 5.1 Problem scenarios
  • 5.2 Memory leaks
  • 5.2.1 Symptoms
  • 5.2.2 Investigating a potential memory leak
  • 5.2.3 Narrowing the cause of a memory leak
  • 5.2.4 Determining the memory leak offender
  • 5.2.5 Resolution
  • 5.2.6 About this scenario
  • 5.3 Deadlock management
  • 5.3.1 Planning the problem resolution
  • 5.3.2 Performance analysis
  • 5.3.3 Lock Analysis preparation
  • 5.3.4 Lock analysis
  • 5.3.5 Historic lock information
  • 5.3.6 About this scenario
  • 5.4 Analyzing a slow-performing application
  • 5.4.1 Planning problem resolution for a slow application
  • 5.4.2 Performance analysis for a slow-performing application
  • 5.4.3 Identification of affected modules and servers
  • 5.4.4 Comparing system resources
  • 5.4.5 About the scenario
  • 5.5 Database performance
  • 5.5.1 Planning the problem resolution
  • 5.5.2 Analyzing the affected data source
  • 5.5.3 Re-creating the problem
  • 5.5.4 Application post-deployment activities
  • 5.5.5 About the scenario
  • Chapter 6. Analyzing composite application problems
  • 6.1 Problem scenarios
  • 6.2 CICS composite transaction
  • 6.2.1 About this scenario
  • 6.3 IMS composite transaction
  • 6.3.1 About this scenario
  • 6.4 CICS resource enqueue
  • 6.4.1 Symptoms of resource enqueuing.
  • 6.4.2 Investigating CICS resource enqueue
  • 6.4.3 About this scenario
  • 6.5 CICS transaction loops
  • 6.5.1 Symptoms of looping transaction
  • 6.5.2 About this scenario
  • 6.6 CICS DSA growth
  • 6.6.1 Monitoring storage growth
  • 6.6.2 About the scenario
  • Appendix A. Sample scenario setup
  • Environment overview
  • WebSphere applications used
  • Memory leak sample
  • Locking application sample
  • Distributed Application Sample
  • CICS application setup
  • Trader CICS application
  • Setting up CICS for TraderCICS
  • Connecting WebSphere for TraderCICS
  • IMS application setup
  • Trader IMS application
  • Setting up IMS for TraderIMS
  • Connecting WebSphere for TraderIMS
  • Putting in the load
  • WebSphere Studio Workload Simulator
  • Rational Robot
  • Sample Java program
  • Appendix B. Installation tips
  • Embedded installation problems
  • Composite transaction problems
  • Appendix C. Additional material
  • Locating the Web material
  • Using the Web material
  • System requirements for downloading the Web material
  • How to use the Web material
  • Abbreviations and acronyms
  • Related publications
  • IBM Redbooks
  • Other publications
  • Online resources
  • How to get IBM Redbooks
  • Help from IBM
  • Index
  • Back cover.

Ejemplares similares