Maximum performance with WebSphere application server V5.1 on iSeries

Maximum performance with WebSphere application server V5.1 on iSeries

There may be several different reasons why you want to read this book. Perhaps you are currently experiencing a performance issue with an application. Or, you may be designing and developing a new application that you want to deploy on the IBM WebSphere Application Server running on the IBM eServer...

Descripción completa

Detalles Bibliográficos
Autor Corporativo: International Business Machines Corporation. International Technical Support Organization (-)
Otros Autores: Aused, Luis (-)
Formato: Libro electrónico
Idioma:Inglés
Publicado: [S.l.] : IBM, International Technical Support Organization c2005.
Edición:1st ed
Colección:IBM redbooks.
Materias:
WebSphere.
Web servers > Computer programs.
Application software > Development.
Ver en Biblioteca Universitat Ramon Llull:https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009627239006719
Tabla de Contenidos:
  • Front cover
  • Contents
  • Notices
  • Trademarks
  • Preface
  • The team that wrote this redbook
  • Become a published author
  • Comments welcome
  • Chapter 1. Performance concepts and factors
  • 1.1 Topology
  • 1.2 Client considerations
  • 1.3 Network design
  • 1.4 Maximizing server performance
  • 1.5 Performance and emerging architectures
  • 1.5.1 Service-oriented architectures
  • 1.5.2 Virtualization
  • Chapter 2. Java and WebSphere execution environment on iSeries servers
  • 2.1 Java execution environment
  • 2.1.1 Java virtual machine implementation
  • 2.1.2 Java Runtime Environment
  • 2.2 Java compilation environment
  • 2.2.1 Direct execution using Java transformation
  • 2.2.2 JIT compiler
  • 2.2.3 Compiling and running Java code
  • 2.3 Garbage collection
  • 2.3.1 Basics in collecting garbage
  • 2.3.2 Garbage collection pitfalls
  • 2.4 Profiling (PFRDTA)
  • 2.4.1 Profiling on the iSeries
  • 2.4.2 Collecting profiling data
  • 2.5 IBM Toolbox for Java
  • 2.6 WebSphere execution environment
  • 2.6.1 Administration
  • 2.6.2 Application development
  • 2.6.3 Security
  • 2.6.4 Web services
  • Chapter 3. Performance tuning methodology
  • 3.1 Setting performance objectives
  • 3.2 General tuning process and performance strategy
  • 3.3 Performance problem determination process
  • 3.4 Summary of key performance measurement tools
  • Chapter 4. Tools for determining performance problems
  • 4.1 System-level tools
  • 4.2 System-level tools for real time use
  • 4.2.1 WRKSYSSTS command
  • 4.2.2 WRKDSKSTS command
  • 4.2.3 WRKACTJOB command
  • 4.2.4 WRKSYSACT command
  • 4.2.5 Management Central
  • 4.2.6 iDoctor
  • 4.2.7 HEAPANA command
  • 4.2.8 Database Monitor for iSeries
  • 4.2.9 Identifying and tuning problem areas
  • 4.2.10 SQL Visual Explain
  • 4.3 System-level tools for reactive use
  • 4.3.1 Collecting performance data
  • 4.3.2 Creating performance data.
  • 4.3.3 Performance Tools for iSeries
  • 4.3.4 Using the system performance tools
  • 4.3.5 Performance Management for iSeries, PM/400, and PM eServer iSeries
  • 4.4 Java and application-level tools
  • 4.4.1 DMPJVM command
  • 4.4.2 ANZJVM command
  • 4.4.3 JAVAGCTOOLS (STRSST)
  • 4.5 WebSphere performance tools
  • 4.5.1 Profiling applications running on the WebSphere Application Server
  • 4.5.2 Performance Monitoring Infrastructure
  • 4.5.3 Tivoli Performance Viewer
  • 4.5.4 Performance Advisors
  • 4.5.5 Log Analyzer
  • 4.6 HTTP performance tools
  • 4.6.1 Server logging
  • 4.6.2 HTTP server tracing
  • 4.6.3 Collection Services
  • 4.6.4 Communications trace
  • 4.7 Stress testing tools
  • 4.7.1 IBM Rational stress testing tools
  • 4.7.2 OpenSTA
  • Chapter 5. Tuning iSeries for a WebSphere or Java environment
  • 5.1 iSeries performance behavior
  • 5.2 Verifying the state of Licensed Program Products
  • 5.3 OS/400 system tuning
  • 5.3.1 Manual tuning versus automatic tuning
  • 5.3.2 Semi-automatic system tuning
  • 5.3.3 Verifying the settings of system values
  • 5.3.4 Creating a separate memory pool for a subsystem
  • 5.3.5 Setting the memory pool sizes and activity levels manually
  • 5.3.6 Working with the prestart jobs
  • 5.4 Java system environment
  • 5.4.1 Java thread run priority
  • 5.4.2 Java thread time slice setting
  • 5.5 AnyNet
  • 5.6 Example of an OS/400 tuning process
  • Chapter 6. Tuning the IBM HTTP Server (powered by Apache)
  • 6.1 Web server performance
  • 6.1.1 The server
  • 6.2 Caching
  • 6.2.1 Dynamic and local (static) caching
  • 6.2.2 Proxy caching
  • 6.2.3 Tuning cache
  • 6.2.4 Fast Response Cache Accelerator
  • 6.2.5 Network File Cache
  • 6.3 Persistent connections
  • 6.4 Secure Sockets Layer and Transport Layer Security
  • 6.5 HTTP server tuning options
  • 6.5.1 Threads and asynchronous I/O
  • 6.5.2 Triggered Cache Manager.
  • 6.5.3 mod_deflate
  • 6.5.4 Logging
  • 6.5.5 HostNameLookups
  • 6.5.6 KeepAliveTimeout
  • 6.5.7 TCP/IP buffer sizes
  • 6.5.8 Denial of service
  • 6.6 Static content location
  • 6.7 References
  • Chapter 7. Tuning the Java virtual machine
  • 7.1 Java virtual machine on iSeries
  • 7.1.1 High level view of JVM on the iSeries server
  • 7.1.2 Runtime modes of execution
  • 7.2 Garbage collection in iSeries JVM
  • 7.2.1 Understanding garbage collection
  • 7.2.2 Garbage collection performance tuning
  • 7.2.3 Problems with garbage collection
  • Chapter 8. Tuning WebSphere Application Server Base
  • 8.1 Adjusting WebSphere Application Server system queues
  • 8.1.1 Queue configuration tips
  • 8.1.2 Enterprise bean method invocation queuing
  • 8.2 WebSphere Application Server tuning parameters
  • 8.2.1 Web container
  • 8.2.2 Session management
  • 8.2.3 Dynamic cache service
  • 8.2.4 Data sources
  • 8.2.5 EJB container
  • 8.2.6 Object Request Broker
  • 8.2.7 Additional performance tips
  • 8.3 Java Messaging Service tuning parameters
  • 8.3.1 Listener service
  • 8.3.2 Listener port
  • 8.3.3 JMS resources
  • 8.4 Tuning your security configuration
  • Chapter 9. Java and WebSphere application design
  • 9.1 Java general design
  • 9.1.1 String manipulation
  • 9.1.2 Object instantiation
  • 9.1.3 Loops
  • 9.1.4 Exceptions
  • 9.1.5 Method resolution
  • 9.1.6 Logging
  • 9.1.7 Variables
  • 9.1.8 Collections
  • 9.1.9 Java Native Interface
  • 9.1.10 Thread creation
  • 9.2 Accessing system services: Database operations
  • 9.2.1 IBM Toolbox for Java driver versus iSeries Developer Kit for Java driver
  • 9.2.2 JDBC through a native driver
  • 9.2.3 Which one to use?
  • 9.2.4 Coding considerations with JDBC
  • 9.2.5 Caching your data source
  • 9.3 Coding considerations with DDM (record-level access)
  • 9.3.1 Minimizing open and close
  • 9.3.2 Blocking on READ_ONLY and WRITE_ONLY.
  • 9.3.3 Downloading a small file using the readAll() method
  • 9.4 Distributed Program Call
  • 9.5 Coding consideration for servlets and JSPs
  • 9.5.1 Do not store large objects in HttpSessions
  • 9.5.2 Releasing HttpSessions when finished
  • 9.5.3 Do not create HttpSessions in JSPs by default
  • 9.5.4 Do not use SingleThreadModel
  • 9.5.5 Using the HttpServlet init() method
  • 9.5.6 Using the HttpServlet destroy() method
  • 9.5.7 Minimizing or eliminating the use of System.out.println()
  • 9.5.8 Don't use Beans.instantiate() to create new bean instances
  • 9.5.9 Using and reusing data sources for JDBC connections
  • 9.5.10 Releasing JDBC resources when done
  • 9.5.11 Page generation using strings
  • 9.5.12 Consideration with static content
  • 9.5.13 JSP include directive versus Action
  • 9.5.14 Minimizing the useBean scope
  • 9.6 Coding considerations for EJBs
  • 9.6.1 Accessing entity beans from session beans
  • 9.6.2 JNDI names
  • 9.6.3 Reusing EJB home interfaces
  • 9.6.4 Using info beans to reduce remote calls
  • 9.6.5 Releasing resources in EJBs
  • 9.6.6 Using local interfaces when possible
  • 9.6.7 Removing stateful session beans when finished
  • 9.6.8 Transactions
  • 9.6.9 Using CMPs instead of BMPs
  • 9.6.10 Message-driven beans
  • 9.6.11 Using home methods
  • 9.6.12 Using the setEntityContext() method
  • 9.6.13 Don't use entity beans as simple data wrappers
  • 9.6.14 Minimizing the use of stateful session beans
  • 9.6.15 Using Data Class Access Beans
  • 9.7 Profiling your application
  • 9.7.1 Method speed
  • 9.7.2 Finding memory leaks
  • 9.8 Using a response time watcher
  • Chapter 10. Scaling and capacity planning for WebSphere applications
  • 10.1 Scalability objectives
  • 10.2 Scaling a solution
  • 10.2.1 Workload patterns
  • 10.2.2 Scalability in practice
  • 10.2.3 Six steps to scaling your solution.
  • 10.3 iSeries-specific scaling considerations
  • 10.3.1 iSeries advantages and configuration customization options
  • 10.3.2 WebSphere for iSeries scalability overview and key concepts
  • 10.3.3 JDBC driver choices on the iSeries
  • 10.4 Planning future capacity to maximize performance
  • 10.5 Generic performance process and methodology
  • 10.5.1 Process steps
  • 10.6 Capacity planning and workload estimation tools
  • 10.6.1 IBM Workload Estimator
  • 10.6.2 PM eServer iSeries
  • 10.7 Disk arm sizing
  • 10.8 Stress testing WebSphere applications
  • 10.9 Sizing an application under development
  • Appendix A. Additional material
  • Locating the Web material
  • Using the Web material
  • System requirements for downloading the Web material
  • How to use the Web material
  • Related publications
  • IBM Redbooks
  • Other publications
  • Online resources
  • How to get IBM Redbooks
  • Help from IBM
  • Index
  • Back cover.

Ejemplares similares