Commerce performance monitoring

 

  1. High Availability
  2. Failover and mutual failover
  3. Switchover
  4. Fail back of fallback
  5. Nodes, cells, and clusters
  6. Terminology
    1. Workload
    2. Transaction
    3. Scenario
    4. Throughput
    5. Response time
    6. Capacity
    7. Failover
  7. WebSphere Commerce environments
    1. Runtime environment
    2. Development environment
  8. Considerations for implementing High Availability solution
    1. Continuous business capacity and performance
    2. Failover support and disaster recovery
    3. System monitoring and performance tuning
    4. Performance testing
  9. Types of system outages
    1. Different scopes of system outage
    2. Different causes of system outage
  10. High Availability solution for WebSphere Commerce
  11. Identify your scenario
  12. Identify your resources and skills requirements
    1. Inventory of site assets
    2. Inventory skilled resources required
  13. Plan your activities
    1. Education and training
    2. Getting skilled help
    3. Site development life cycle
    4. Scaling hardware versus performance tuning
    5. Performance testing is critical
    6. Failover support for launch
  14. Topology
  15. Chapters overview
    1. High Availability
    2. Application development
    3. Performance monitoring and tuning
    4. Performance test
    5. Maintenance
  16. Reliability Scalable Cluster Technology
  17. Tivoli System Automation
    1. Introduction
    2. Terms in Tivoli System Automation
    3. Start with Tivoli System Automation
    4. Relationship with RSCT
  18. HACMP
  19. High Availability Disaster Recovery
    1. Introduction
    2. Architecture of HADR
    3. How HADR works
    4. Synchronization modes for HADR
    5. Automatic Client Reroute
  20. HACMP
  21. SQL replication
    1. Introduction
    2. How SQL replication works
  22. Introduction to availability
    1. Hardware-based High Availability
    2. Workload management
    3. Failover
    4. HAManager
    5. Session management
  23. WebSphere workload management defined
    1. Distributing workloads
    2. Benefits
  24. Session management and failover inside the plug-in
  25. Web container failures
  26. Web server plug-in failover tuning
  27. Web container clustering and failover (Web server plugin)
  28. WebSphere Application Server clustering
  29. WebSphere Commerce cell and cluster setup
  30. Introduction to Web server High Availability
    1. Available solutions
    2. IBM WebSphere Edge Components Load Balancer
  31. Load Balancer High Availability
  32. Database nodes
    1. DB2 installation prerequisites
    2. Base product installation
    3. Manually create DB2 64-bit instance
    4. Installation of DB2 fix pack
  33. WebSphere Commerce node 1
  34. Additional WebSphere Commerce nodes
  35. Configure a WebSphere Network Deployment Manager
    1. Install IBM WebSphere Application Server Network Deployment
    2. Create the WebSphere Network Deployment Manager Profile
  36. Install IBM HTTP Server
    1. Base installation
    2. Install fixes
  37. Install IBM WebSphere Edge Components Load Balancer V6.0.2
    1. Install the license
    2. Install Load Balancer refresh pack
  38. HADR
    1. Configuring HADR on a primary/standby database
    2. Enabling client reroute in a HADR environment
    3. Installing Tivoli System Automation
    4. Defining and administering a TSA cluster
    5. Enabling instance and HADR with TSA
  39. Scenario setup as described in the clustering whitepaper
  40. Details on configuring Web server node 1
    1. Pre-instance creation tasks
    2. Post instance creation tasks
    3. Post federation tasks
  41. Add additional Web servers
    1. Preparation
    2. Copy files from Web server node 1
    3. Modify the Web server configuration
    4. Add the new Web server to the cell configuration
  42. Configure Load Balancer
    1. MAC forwarding
    2. NAT forwarding
    3. Configure the Web servers for WebSphere Commerce
    4. Configure the IBM HTTP Server Plug-in
  43. Configure Load Balancer High Availability
    1. Configure basic High Availability
    2. Adding reach targets
    3. Command-line configuration
    4. Configuring the High Availability scripts
    5. Test Load Balancer High Availability
    6. Starting Dispatcher automatically after a reboot
  44. Development best practices for performance
    1. Access Bean usage
    2. Java classes and keywords
    3. JSPs
    4. Registry objects
    5. Database operations
    6. Command execution
    7. Webconsiderations
  45. Performance best practices for database customizations
    1. Table design
    2. Index design
    3. Avoiding deadlocks
  46. Performance best practices for SQL queries
    1. Reduce the result set as early as possible
    2. Avoid using sub-selects and redundant expressions
    3. IN versus Exists
    4. Other important SQL tuning hints
  47. Register source in SQL replication
  48. Subscribe sets in SQL replication
  49. Capture data from DB2 sources
  50. Types of caching
    1. Dynamic caching
    2. Edge Side Includes (ESI) caching
  51. Set up ESI caching
    1. Prerequisites for ESI caching
    2. Configure ESI caching
  52. Caching enhancements in WebSphere Commerce.1 and later
  53. Cache replication
    1. Cache replication
    2. In-memory cache
    3. Offload to disk
    4. FlushToDiskOnStop
    5. Limitation on invalidation when server is stopped
    6. Performance tuning
    7. Tune disk cache
    8. Instructions to set up cache replication
    9. Other options to ensure cache content consistency across cluster
    10. 13.4.10 Monitor runtime cache
    11. Monitor ESI caching
    12. Cache Replication Summary
  54. Cookie-based session management
  55. Database persistence using WebSphere Application Server session management
  56. Memory-to-memory session replication using WebSphere Application Server session management
  57. Conclusion
  58. URL rewriting
  59. Clustering for scalability and failover
  60. SQL profiling
  61. Java code profiling
  62. Mapping an SQL statement to Java code
  63. IBM Page Detailer
    1. Page Detailer Overview
    2. Page Detailer considerations
    3. Page Detailer Key factors
    4. Tips for using Page Detailer
    5. Page Detailer Reference
  64. Operating system introduction
  65. General utilities related with operating system monitoring
    1. nmon
    2. Top
    3. vmstat
    4. iostat
    5. ps
    6. svmon
  66. Best practices for AIX monitoring
  67. Operating System Monitoring Summary
  68. DB2 performance considerations
    1. Physical environment considerations
    2. DB2 objects management
    3. DB2 prerequisites checking
    4. Installation prerequisites
  69. DB2 monitoring
    1. DB2 Monitoring
    2. Snapshot monitor
    3. DB2 Event monitor
  70. DB2 tuning in WebSphere Commerce
    1. DB2 Parameters related to memory
    2. DB2 Parameters related to transaction logs
    3. DB2 Parameters related to disk I/O
    4. DB2 Parameters related to locking
    5. DB2 Parameters related to agents management
    6. DB2 Best practices
  71. Utilities in database tier for WebSphere Commerce
    1. Massload
    2. Staging server
    3. DBClean
  72. DB2 Performance Conclusions
  73. Web container thread connection pool
  74. Database connection pool
  75. Prepared statement cache
  76. Dynamic caching
  77. Java Virtual Machine heap management
    1. Heap expansion
    2. Heap shrinkage
    3. Tune the JVM heap size
    4. Monitoring JVM memory and garbage collection
    5. Heap fragmentation due to pinned and dosed objects
    6. Heap fragmentation due to large objects
  78. Monitoring
    1. Performance Monitoring Infrastructure (PMI)
    2. WAS Trace and logging
  79. WAS Tools and reference
  80. Performance fixes
  81. Monitor IBM HTTP Server
    1. IBM HTTP Server status page
    2. Access log
    3. Monitoring performed by Load Balancer
    4. IBM HTTP Server Plug-in
    5. Configure directories, non-root_user, and permissions
    6. Enable remote configuration
    7. Check the configuration directory
    8. Verify the Web server configuration file
    9. Activate remote Web server management (optional)
    10. Update the Web server configuration
    11. Activate remote Web server management
    12. Propagate IBM HTTP Server Plug-in configuration
    13. Restart the Web server
  82. Web Server Tuning parameters
    1. AIX web server settings
    2. httpd.conf settings
    3. IBM HTTP Server Plug-in
  83. Configure the Load Balancer cluster using the GUI
  84. Load Balancer Monitor
    1. Load Balancer Reports
    2. Load Balancer Graphical server monitor
    3. Load Balancer Binary logging
  85. Tuning Load Balancer parameters
    1. Load Balancer Host
    2. Load Balancer Executor
    3. Load Balancer Cluster
    4. Load Balancer Port
    5. Load Balancer Server
    6. Load Balancer Manager
    7. Load Balancer Advisor
  86. Load Balancer Server affinity
    1. Load Balancer: Types of server affinity
    2. Load Balancer: Configure source IP affinity for MAC and NAT forwarding
    3. Load Balancer: Configure CBR and SSL session ID affinity
    4. Load Balancer: Testing server affinity
  87. Configure Web servers for MAC forwarding
  88. Configure the Load Balancer cluster using the GUI
  89. Variables
  90. goInOp
  91. serverDown
  92. serverUp
  93. highavailChange
  94. Performance testing: Why is it complex
  95. Load Balancer: Why it is important
  96. Overall site development life cycle
  97. Typical performance characteristics of a WebSphere Commerce site
  98. Types of performance tests for WebSphere Commerce
    1. Stress testing
    2. Scalability testing
    3. Soak, endurance, or reliability testing
    4. Stress-endurance test
    5. 100% + 1 testing
    6. Capacity testing
    7. Performance regression testing
    8. High Availability testing
  99. Define scope and requirements of new design
  100. Well formed constructor
  101. Lazy instantiation
  102. Tracing
  103. Synchronization
  104. Avoid instanceof
  105. Initial capacity and load factor
  106. Throwing and catching exceptions
  107. Reduce unnecessary memory usage
  108. Use local variables, avoid inappropriate use of non-final getter methods
  109. Session-aware JSP
  110. DataBean activation
  111. StoreRegistry
  112. RefreshRegistry and UpdateRegistry controller commands
  113. Define target environment
  114. Retrieve only the information that is needed
  115. Practices to be avoided
  116. Define scenario and workload distribution
  117. Define test cases
  118. Maintaining a well-defined test plan
  119. Test tools introduction
    1. How to select test tool
    2. Performance test tools classification
  120. WebSphere Application Server dynamic cache
  121. ESI Processor
  122. ESI Best practices
  123. Install the DynaCacheEsi application
  124. Start the DynaCacheEsi application
  125. External cache group settings
  126. Reconfigure the Web servers
  127. Modify the DynaCache configuration file
  128. IBM Rational Performance Tester
    1. Architecture of Rational Performance Tester
    2. Features of RPT
    3. Procedure to use RPT to run performance test
  129. Seague SilkPerformer
  130. Page Detailer
    1. Page Detailer: Overview
    2. Page Detailer: Important considerations
    3. Page Detailer: Key factors
  131. Other performance test tools
  132. Trend of performance test tools
  133. Control DRS message size
  134. Tune in-memory cache size
  135. Filter out expiration and LRU-based invalidation events
  136. Control disk cache size
  137. Configure offload location
  138. Additional disk cache tuning parameters
  139. What SilkPerformer can do
  140. Procedure to use SilkPerformer to run performance test
  141. Create a replication domain
  142. Associate a server to replication domain
  143. Configure sharing policy in cachespec.xml
  144. Invalidate cache entry per JVM using database
  145. Invalidate cache entry per JVM using file system
  146. Key attributes of a performance test
  147. Common test execution steps
  148. Executing stress tests
    1. Testing for throughput
    2. Testing for concurrency
    3. Analyzing stress test results
  149. Scalability testing
  150. Soak, endurance, or reliability testing
  151. High Availability testing
  152. Test results to be collected and verified
  153. Common troubleshooting steps
  154. Solving memory problems in WebSphere applications
    1. Gather verbose Garbage Collection logs
    2. Analyzing verbose GC logs
    3. Option 1: Tune max heap size to optimize GC frequency
    4. Tactic 2: Tune -Xk and -Xp to minimize fragmentation
    5. Tactic 4: identifying by swprofiler
    6. Tactic 4: Tuning the cache size
    7. Tactic 5: Performing the heap dump
  155. Solving throughput and response time problems
    1. Identifying throughput problems in performance testing
    2. Analyzing and solving throughput problems
  156. Benefit of nmon
  157. Installing and using the nmon tool
  158. Get AIX statistics data using nmon
  159. How to analyze the statistics data
  160. The best practice for AIX performance analysis
  161. DB2 database maintenance in WebSphere Commerce
    1. DB2 database maintenance utilities
    2. WebSphere Commerce Database Cleanup utility
    3. Commerce DB2 database maintenance solution
  162. WAS Maintenance not requiring planned outages
    1. WebSphere Application Server log maintenance
    2. Deployment of cachespec.xml
    3. Rollout update
  163. DB2 Efficient I/O management
  164. DB2 Memory usage
  165. DB2 Table management
  166. Index management
  167. Tablespace management
  168. DB2 Agent management
  169. Planned outages
    1. WebSphere Application Server fix pack/APAR upgrade
    2. WebSphere Commerce fix pack/APAR upgrade
  170. Reorganizing data in tablespaces
  171. DB2: Collecting statistics
  172. How massload works
  173. Step1: Configure the loading utilities
  174. Step 2: Generate a DTD and schema for using loading utilities
  175. Step 3: Resolve identifiers for records that share identifiers with existing data
  176. Step 4: Execute the massload utility
  177. Preformation consideration and practice
  178. Staging server introduction
  179. How staging server works
  180. Staging Server: Performance consideration and practice
  181. Maintenance not requiring planned outages
    1. Maintain IBM HTTP Server logs
    2. Deploy new static content
  182. Enable verbose garbage collection
  183. Identify Java stack that creates large objects
  184. Tune heap to accommodate more large objects
  185. PMI predefined statistic sets
  186. IBM Support Assistant
  187. Maintenance involving planned outages
    1. Quiescing a Web server
    2. Compatible upgrades
    3. Incompatible upgrades
    4. Maintenance Web page for site downtimes
  188. Load Balancer: Maintenance not requiring planned outages
  189. Keepalive
  190. IBM HTTP Server Threads
  191. SSL
  192. Compression
  193. Web Server Access logs
  194. Expiration of static content
  195. Workload management policies
  196. Retry interval
  197. Plug-in Connection timeout
  198. Primary and backup servers
  199. Load Balancer: Maintenance involving planned outages
    1. Load Balancer: Compatible upgrades
    2. Load Balancer: Incompatible upgrades
  200. Maximum number of connections
  201. Refresh interval
  202. Rule-based load balancing
  203. Load Balancer Stickyness to source IP address
  204. Load Balancer Cross-port affinity
  205. Load Balancer: Passive cookie affinity
  206. Load Balancer: Active-cookie affinity
  207. Load Balancer: URI affinity
  208. Load Balancer: SSL session ID
  209. Load Balancer: Server affinity conclusion
  210. Source IP affinity - GUI configuration
  211. Command-line configuration
  212. Configure CBR using the GUI
  213. Configure CBR by modifying the NAT configuration files
  214. Performance test life cycle
  215. Building your site capacity to account for High Availability
  216. Data scalability
  217. Workload scalability
  218. Store complexity scalability
  219. Saturation point testing
  220. Verify pass criterion
  221. Identify memory leaks
  222. Identifying memory fragmentation
  223. kCluster, pCluster, and fragmentation
  224. How fragmentation occurs
  225. How to avoid fragmentation
  226. Configuring the kCluster
  227. Configuring the pCluster
  228. Set Xk and Xp values in WebSphere Administration Console
  229. Throughput analysis methodology
  230. Throughput degradation analysis and solution
  231. Example of throughput degradation analysis
  232. Runstats
  233. Reorgchk and Reorg
  234. Rebind (db2rbind)
  235. Syntax for DBClean configuration and execution
  236. Performance consideration for DBClean
  237. FFDC
  238. Garbage collection log (native_stderr.log)
  239. SystemOut.log and SystemErr.log
  240. Trace.log
  241. Threaddump and heapdump
  242. Deployment of Commerce instance configuration file
  243. IBM HTTP Server logs (Apache logs)
  244. IBM HTTP Server Plug-in
  245. Maintain Load Balancer logs
  246. Instructions for all compatible upgrade types
  247. Instructions for specific types of compatible upgrades
  248. IBM Redbooks
  249. Other publications
  250. Online resources
  251. How to get Redbooks
  252. Help from IBM
  253. WebSphere Application Server and WebSphere Commerce federation and clustering
  254. Web server clustering
  255. Development performance considerations
  256. Caching
  257. Profiling
  258. Operating system monitoring tools
  259. IBM DB2 Universal Database
  260. Monitor and tune WebSphere Application Server for WebSphere Commerce
  261. Monitor and tune Web servers
  262. Monitor and tune Load Balancer
  263. Introduction
  264. Introduction to performance testing
  265. Designing a test plan
  266. Performance test tools
  267. Applying performance testing to WebSphere Commerce
  268. Analyzing test results and solving performance problems
  269. Database maintenance
  270. Maintain and update WebSphere Application Server tier
  271. Maintain and update Web servers
  272. Maintain and update Load Balancer

  273. Node
  274. Getting started
  275. High Availability solutions for unplanned and planned outages
  276. Install and configure a High Availability WebSphere Commerce system
  277. Design with performance in mind
  278. Monitoring and performance tuning
  279. Performance test
  280. Maintenance
  281. Cell
  282. Profile
  283. Federated or managed environment
  284. Clustering
  285. Development environment
  286. Runtime environment
  287. Active-manual failover support
  288. Active-active failover support
  289. Complete outage
  290. Partial outage
  291. Planned outage
  292. Unplanned outage
  293. Related publications

 

Home