Record:   Prev Next
Author Redbooks, IBM
Title Performance Tuning for Content Manager
Imprint Durham : I B M, 2003
©2003
Descript 1 online resource (462 pages)
text txt rdacontent
computer c rdamedia
online resource cr rdacarrier
Note Intro -- Part 1 Architecture and technology overview -- Chapter 1. Content Manager -- 1.1 Architecture overview -- 1.2 Content Manager components -- 1.2.1 Library Server -- 1.2.2 Resource Manager -- 1.2.3 System Administration Client -- 1.2.4 Client for Windows -- 1.2.5 eClient -- 1.2.6 Customized client -- 1.3 Content Manager system configuration -- 1.4 Performance features highlight -- Chapter 2. Complementing software -- 2.1 DB2 Universal Database overview -- 2.1.1 Basic relational database concepts -- 2.1.2 DB2 architecture overview -- 2.1.3 Memory usage -- 2.2 WebSphere Application Server overview -- 2.2.1 J2EE overview -- 2.2.2 Three-tier architecture -- 2.2.3 Architectural components -- 2.3 Tivoli Storage Manager overview -- 2.3.1 TSM capabilities overview -- 2.3.2 TSM architecture -- Part 2 Performance tuning overview -- Chapter 3. Performance tuning basics -- 3.1 Introduction -- 3.2 When to plan and tune your system? -- 3.3 Performance methodology -- 3.4 Performance improvement process -- 3.5 General performance tuning guideline -- Chapter 4. Performance monitoring and tracing -- 4.1 Measuring the baseline -- 4.2 Monitoring tools for AIX -- 4.2.1 topas -- 4.3 Monitoring tools for Windows -- 4.3.1 Task Manager -- 4.4 Monitoring tools for DB2 -- 4.4.1 Snapshot monitoring -- 4.4.2 Event monitoring -- 4.4.3 Health Center -- 4.5 Monitoring tools for WAS -- 4.5.1 Tivoli Performance Viewer -- 4.6 Performance tracing for Content Manager -- 4.6.1 ICM connector performance tracing -- 4.6.2 Library Server performance tracing -- 4.6.3 Resource Manager performance tracing -- Part 3 Performance tuning details -- Chapter 5. Planning for performance -- 5.1 Introduction -- 5.2 Understanding current processes and data -- 5.3 Translating current processes to the new data model -- 5.4 Analyzing impact of new workload -- 5.5 Estimating storage requirements
Chapter 6. Designing and configuring for performance -- 6.1 Introduction -- 6.2 General design considerations -- 6.3 Configuration choices and trade-off -- 6.4 Hardware -- 6.4.1 Scalability -- 6.5 Library Server -- 6.5.1 Library Server configuration -- 6.5.2 Authentication -- 6.5.3 Data model -- 6.5.4 Document routing -- 6.6 Resource Managers -- 6.6.1 Resource Manager properties -- 6.6.2 Configuration -- 6.6.3 System managed storage -- 6.6.4 Logging -- 6.6.5 Move Resource Manager storage area -- 6.7 Network -- 6.7.1 The triangle or the inverted "V" -- 6.7.2 Physical locations -- 6.7.3 Network and resource objects -- 6.7.4 Network and Web clients -- 6.7.5 Network and Library Server -- 6.8 Client applications -- 6.8.1 The OO API layer component of the client -- Chapter 7. Tuning Content Manager -- 7.1 Introduction -- 7.2 Common performance tuning recommendations -- 7.2.1 Effective use of memory -- 7.2.2 Effective use of disk I/O -- 7.2.3 Effective use of network bandwidth -- 7.3 Tuning the Windows operating system -- 7.3.1 Disable Indexing Service -- 7.3.2 Disable Computer Browser Service -- 7.3.3 Disable Internet Information Service -- 7.3.4 Disable 8.3 file name creation (NtfsDisable8dot3NameCreation) -- 7.3.5 Check memory -- 7.4 Tuning AIX operating system -- 7.4.1 Adjust maximum number of PROCESSES allowed per user -- 7.4.2 Use JFS2 and EJFS for logical volumes and file systems -- 7.4.3 Check the default values in ulimit -- 7.5 Tuning network -- 7.5.1 Set all machines to full duplex -- 7.5.2 Set MTU size to maximum supported by LAN -- 7.6 Tuning Library Server through DB2 -- 7.6.1 Design and configuration setup -- 7.6.2 Regular routine maintenance -- 7.6.3 Buffer pool tuning -- 7.6.4 Parameter tuning -- 7.7 Tuning Resource Manager -- 7.7.1 WebSphere tuning -- 7.7.2 Enabling LAN cache and managing staging directory -- 7.7.3 Tuning replicator
7.7.4 Tuning migration policy and migrator -- 7.8 Tuning for initial load and daily load operation -- 7.8.1 Loading legacy documents before going to production -- 7.8.2 Loading legacy documents during production -- 7.8.3 Load process -- 7.9 Maintenance monitoring and tuning -- 7.9.1 Routine DB2 tuning (runstat/rebind and reorg) -- 7.9.2 Performance monitoring and profile maintenance -- 7.9.3 Tuning system parameters and configurations -- 7.9.4 Re-defining and upgrading system architecture -- 7.9.5 Adding more system resources -- 7.10 Tuning applications -- Chapter 8. Tuning DB2 for Content Manager -- 8.1 Introduction -- 8.2 Design and configuration setup -- 8.2.1 Spread DB components over multiple disks -- 8.2.2 Customize CM databases deployment at install through DDL -- 8.2.3 Create separate instances during installation -- 8.2.4 Initial parameter tuning for Library Server database -- 8.2.5 Create attribute indexes -- 8.2.6 Create indexes for document routing -- 8.2.7 Additional configuration and tuning suggestions -- 8.3 Regular routine maintenance -- 8.3.1 Monitor system performance using DB2 snapshot -- 8.3.2 Keep db stat and execution plans up to date through runstats/rebind -- 8.3.3 Reorganize tables through reorg -- 8.3.4 Clean up event log -- 8.4 Buffer pool tuning -- 8.4.1 Buffer pool hit ratio and index pool hit ratio -- 8.5 Parameter tuning -- 8.5.1 Intra-partition parallelism (intra_parallel) -- 8.5.2 Maximum number of concurrently active databases (numdb) -- 8.5.3 Maximum number of active applications (maxappls) -- 8.5.4 Average number of active applications (avg_appls) -- 8.5.5 Maximum number of database manager agents (maxagents) -- 8.5.6 Maximum number of coordinating agents (max_coordagents) -- 8.5.7 Initial number of agents in agent pool (num_initagents) -- 8.5.8 Maximum number of idle agent pool (num_poolagents)
8.5.9 Maximum number of fenced processes (fenced_pool) -- 8.5.10 Maximum database files open per application (maxfilop) -- 8.5.11 Maximum total files open (maxtotfilop) -- 8.5.12 Database heap (dbheap) -- 8.5.13 Catalog cache size (catalogcache_sz) -- 8.5.14 Log buffer size (logbufsz) -- 8.5.15 Maximum storage for lock list (locklist) -- 8.5.16 Package cache size (pckcachesz) -- 8.5.17 Application control heap size (app_ctl_heap_sz) -- 8.5.18 Application heap size (applheapsz) -- 8.5.19 Sort heap size (sortheap) -- 8.5.20 Sort heap threshold (sheapthres) -- 8.5.21 Statement heap size (stmtheap) -- 8.5.22 Query heap size (query_heap_sz) -- 8.5.23 Java interpreter heap size (java_heap_sz) -- 8.5.24 Private memory threshold (priv_mem_thresh) -- 8.5.25 Client I/O block size (rqrioblk) -- 8.5.26 Application support layer heap size (aslheapsz) -- 8.5.27 Changed pages threshold (chngpgs_thresh) -- 8.5.28 Number of asynchronous page cleaners (num_iocleaners) -- 8.5.29 Number of I/O servers (num_ioservers) -- 8.5.30 Maximum percent of lock list before escalation (maxlocks) -- 8.5.31 Lock timeout (locktimeout) -- 8.5.32 Log file size (logfilsiz) -- 8.5.33 Number of primary log files (logprimary) -- 8.5.34 Number of secondary log files (logsecond) -- 8.5.35 Minimum commits before write logs to disk (mincommit) -- 8.5.36 Connection concentrator -- Chapter 9. Tuning WebSphere for Content Manager -- 9.1 Introduction -- 9.2 Hardware tuning -- 9.2.1 Processor speed -- 9.2.2 System memory -- 9.2.3 Networks -- 9.3 Operating system tuning -- 9.3.1 TCP timed wait delay (TcpTimedWaitDelay) -- 9.3.2 Maximum user ports (MaxUserPort) -- 9.3.3 Number of open files permitted (ulimit) -- 9.4 Web server tuning -- 9.4.1 Web server configuration refresh interval (RefreshInterval) -- 9.4.2 HTTP server maximum clients (MaxClients)
9.4.3 Minimum spare server processes (MinSpareServers) -- 9.4.4 Maximum spare server processes (MaxSpareServers) -- 9.4.5 Startup server processes (StartServers) -- 9.4.6 Maximum requests per child (MaxRequestPerChild) -- 9.4.7 Threads per child (ThreadsPerChild) -- 9.4.8 Pending connections queue length (ListenBackLog) -- 9.5 WebSphere Application Server tuning -- 9.5.1 Application server process priority -- 9.5.2 Web container maximum thread size -- 9.5.3 Thread allocation beyond maximum -- 9.5.4 Max keep-alive connections (MaxKeepAliveConnections) -- 9.5.5 Maximum requests for a connection (MaxKeepAliveRequests) -- 9.5.6 URL invocation cache -- 9.5.7 Security -- 9.6 Java Virtual Machines tuning -- 9.6.1 Initial and maximum heap size for the JVM -- Chapter 10. Tuning TSM for Content Manager -- 10.1 Introduction -- 10.2 Server performance option tuning -- 10.2.1 Asynchronous I/O (AIXASYNCIO) -- 10.2.2 Direct I/O (AIXDIRECTIO) -- 10.3 Automatic tuning of server options -- 10.3.1 Self-tune MOVEBATCHSIZE/MOVESIZETHRESH -- 10.3.2 Self tune buffer pool size (BUFPOOLSIZE) -- Chapter 12. Case study -- 12.1 Generic Content Manager systems -- 12.1.1 Forms processing system -- 12.1.2 Archiving system -- 12.1.3 Document management system -- 12.1.4 Web content management system -- 12.1.5 Rich media system -- 12.1.6 Characteristics of Content Manager systems summarized -- 12.1.7 Our near "worst case scenario" -- 12.2 The business problem: XYZ Insurance revisited -- 12.2.1 Familiar XYZ example -- 12.2.2 New business requirements -- 12.3 The design of our solution -- 12.3.1 Data model -- 12.4 Sizing of our solution -- 12.4.1 AIX -- 12.4.2 Windows 2000 -- 12.5 Process -- 12.6 Developed programs -- 12.7 Testing procedure -- Part 4 Appendixes -- Appendix A. CMV8 Sizer output -- A.1 AIX system results -- A.2 Windows system results
Appendix B. Case study system setup
Description based on publisher supplied metadata and other sources
Electronic reproduction. Ann Arbor, Michigan : ProQuest Ebook Central, 2020. Available via World Wide Web. Access may be limited to ProQuest Ebook Central affiliated libraries
Link Print version: Redbooks, IBM Performance Tuning for Content Manager Durham : I B M,c2003 9780738453194
Subject Content manager.;IBM Database 2.;Database management
Electronic books
Record:   Prev Next