Front cover -- Contents -- Notices -- Trademarks -- Preface -- The team that wrote this redbook -- Become a published author -- Comments welcome -- Part 1 Introduction -- Chapter 1. Introduction -- 1.1 What this book is about -- 1.2 Who this book is for -- 1.3 What about other problem determination books ? -- 1.4 How to use this book -- 1.5 Platform and products -- Chapter 2. Guidelines for problem determination -- 2.1 Things to check -- 2.1.1 Responsibilities and problem ownership -- 2.1.2 Availability of resources -- 2.1.3 Processes -- 2.2 Problem determination steps -- 2.2.1 Identifying the problem -- 2.2.2 Documenting the problem -- 2.2.3 Organizing problem resolution -- 2.2.4 Analyzing the problem -- 2.2.5 Implementing the problem resolution -- 2.2.6 Closing the problem -- 2.3 Guidelines for customers -- 2.3.1 Defining the problem -- 2.3.2 Gathering background information -- 2.3.3 Gathering relevant diagnostic information -- 2.3.4 Determining problem severity -- 2.3.5 Gathering additional information -- 2.3.6 Reporting a software problem -- 2.3.7 Accessing Software Support -- Chapter 3. The eMerge business scenario -- 3.1 The eMerge business scenario -- 3.2 Architecture -- 3.3 Application details -- 3.3.1 Get Customer Details use case -- 3.3.2 Request and Accept Quote use case -- 3.4 The Patterns for e-business approach -- 3.5 Products -- 3.5.1 Web server -- 3.5.2 WebSphere Application Server -- 3.5.3 Message Oriented Middleware -- 3.5.4 Integration middleware -- 3.5.5 Back-end applications -- Part 2 Problem determination details -- Chapter 4. Problem determination tools: runtime environment -- 4.1 Chapter organization -- 4.2 Operating system -- 4.3 WebSphere Application Server -- 4.3.1 JVM logs -- 4.3.2 Viewing the service log -- 4.3.3 Log Analyzer -- 4.3.4 Version information -- 4.3.5 Collector tool.

4.3.6 Debugging with the Application Server Toolkit -- 4.3.7 WebSphere Application Server tracing -- 4.3.8 First Failure Data Capture tool -- 4.3.9 Other WebSphere Application Server logs -- 4.3.10 BackupConfig and RestoreConfig -- 4.3.11 DumpNameSpace -- 4.3.12 Tivoli® Performance Viewer -- 4.4 WebSphere MQ -- 4.4.1 First-Failure Support Technology (FFST™) -- 4.4.2 Error logs -- 4.4.3 WebSphere MQ error logs -- 4.4.4 Tracing WebSphere MQ for AIX -- 4.4.5 WebSphere MQ Java tracing -- 4.4.6 Formatting the MQ trace file -- 4.4.7 WebSphere MQ Explorer -- 4.5 WebSphere Business Integration Message Broker -- 4.5.1 Tracing -- 4.5.2 Message Broker Debugger -- 4.6 IBM HTTP Server -- 4.7 IBM DB2 UDB -- 4.7.1 Java Database Connector tracing -- 4.7.2 Running a JDBC trace -- 4.8 IBM Tivoli Directory Server -- Chapter 5. Problem determination tools: development environment -- 5.1 WebSphere Studio -- 5.2 WebSphere Studio Application Developer Integration Edition V5.0.2 -- 5.2.1 Application assembly -- 5.2.2 Compile -- 5.2.3 Component test perspective -- 5.2.4 IBM Agent Controller -- 5.2.5 Test environment -- 5.2.6 Debugger -- 5.2.7 Process debugger -- 5.2.8 Profiling perspective -- 5.3 WebSphere Studio Application Developer V5.1 -- 5.3.1 Log and Trace Analyzer for Autonomic Computing -- 5.3.2 J9 JVM: Hot Method replace -- 5.3.3 Active Script debugging -- 5.3.4 SQLJ debugging -- 5.3.5 J2EE Code Validation technology preview tool -- 5.4 RFHUTIL -- Chapter 6. WebSphere Application Server : plug-in -- 6.1 Web server plug-in -- Chapter 7. WebSphere Application Server: base -- 7.1 WebSphere Application Server -- 7.1.1 General problem determination guidelines -- 7.1.2 Application servers -- 7.1.3 Administrative Console -- 7.1.4 wsadmin problems -- 7.1.5 Applications -- 7.1.6 Tracing -- 7.1.7 Clients -- 7.1.8 Resource providers -- 7.1.9 Resource providers: JDBC providers.

7.1.10 Resource providers: data sources -- 7.1.11 Resource providers: WebSphere MQ JMS Provider resources -- 7.1.12 Embedded Messaging -- 7.1.13 Security -- 7.1.14 Security: SSL -- 7.1.15 Security: Java 2 security -- 7.1.16 Console users and groups -- 7.1.17 Naming -- 7.1.18 Java Virtual Machine: Memory -- 7.1.19 HTTP Sessions -- 7.1.20 Performance -- Chapter 8. WebSphere Application Server Enterprise -- 8.1 WebSphere Application Server Enterprise -- 8.1.1 Process Choreographer -- 8.1.2 Business rule beans -- 8.1.3 Extended messaging -- 8.1.4 Asynchronous beans -- 8.1.5 Dynamic query -- 8.1.6 Scheduler -- 8.1.7 Startup beans -- 8.1.8 Application profiling -- 8.1.9 Object pools -- 8.1.10 WorkArea service -- 8.1.11 Internationalization service -- 8.1.12 Last participant support -- 8.1.13 ActivitySession service -- 8.1.14 Back-up cluster support -- 8.1.15 Administrative Console (Enterprise) -- Chapter 9. WebSphere Application Server Network Deployment -- 9.1 WebSphere Application Server Network Deployment environment -- 9.1.1 Deployment Manager -- 9.1.2 Problems in the cell environment -- 9.1.3 Administrative Console -- 9.1.4 Workload management -- 9.1.5 HTTP session management -- 9.1.6 Resources -- 9.1.7 JMS Provider -- 9.1.8 Naming -- 9.1.9 ORB -- Chapter 10. WebSphere MQ -- 10.1 WebSphere MQ -- 10.1.1 WebSphere MQ Messaging issues with the WebSphere Application Server -- 10.1.2 Client -- 10.1.3 Cluster -- 10.1.4 Channels -- 10.1.5 Security -- Chapter 11. WebSphere Business Integration Message Broker -- 11.1 WebSphere Business Integration Message Broker -- Chapter 12. The back-end diagnostic overview -- 12.1 WebSphere TXSeries CICS -- 12.1.1 The SYMREC file -- 12.1.2 Encina trace messages -- 12.1.3 DCE diagnostic messages -- 12.1.4 WebSphere TXSeries tracing -- 12.2 Encina tracing for CICS Application Server processes.

12.2.1 Writing trace data to in-storage buffers -- 12.3 CICS Transaction Gateway and CICS Universal Client -- 12.4 CICS Universal Client tracing -- 12.4.1 Starting and stopping Client daemon tracing -- 12.4.2 Wrapping the Client daemon trace -- 12.5 Formatting the binary trace file (CICSFTRC) -- 12.6 Client daemon trace analysis -- 12.7 CICS Transaction Gateway tracing -- 12.8 CICS Transaction Gateway on z/OS -- 12.8.1 The Gateway daemon -- 12.8.2 Trace file allocation -- 12.8.3 Application trace -- 12.8.4 Gateway daemon trace -- 12.8.5 JNI tracing -- 12.8.6 EXCI trace -- 12.9 CICS problem diagnosis -- 12.9.1 CICS messages -- 12.9.2 CICS internal trace -- 12.9.3 CICS Trace Control Facility (CETR) -- Part 3 Appendixes -- Appendix A. Problem determination tools: other platforms -- Windows 2000 Server -- WebSphere MQ: Windows -- WebSphere Business Integration Message Broker: Windows -- z/OS -- System Management User Interface debug utilities -- Language Environment® (CEEDUMP) -- WebSphere MQ: z/OS -- WebSphere MQ channel trace -- IPCS and WebSphere MQ -- WebSphere Application Server: z/OS -- Diagnostic data -- Executing the CTRACE for WebSphere -- WebSphere Business Integrator: z/OS -- Components of WebSphere Business Integrator on z/OS -- Capturing a dump of the relevant address spaces -- Displaying the status of a trace -- Collecting a user execution group trace -- Collecting a service execution group trace -- Logs -- Useful HFS files -- Trace files -- LDAP: z/OS -- IBM HTTP Server -- General configuration -- SSL handshake and configuration issues -- CMS key database (.kdb) and certificate issues -- LDAP authentication related issues -- Server hang issues -- Request failure (500, 404, 400, etc.) issues -- Dynamic content, tracing IBM HTTP Server and WebSphere connection -- Appendix B. Methodology -- The methodology used in this book.

Why do we need a methodology? -- How does the methodology work? -- Work products -- Related publications -- IBM Redbooks -- Online resources -- How to get IBM Redbooks -- Help from IBM -- Index -- Back cover.