IBM E02HRLL-G Administration Guide - Page 193

Appendix A - performance considerations This appendix contains information to assist you in achieving the best performance for your specific environment. Managing queue overflow WebSphere Partner Gateway components use a JMS queue to asynchronously invoke each other. However, if the arrival rate of messages in a queue is greater than the processing rate of those messages, the queue will reach its maximum number of messages. If depth of the queue becomes equal to the maximum depth configured for that queue, the queue overflows. WebSphere Partner Gateway provides a mechanism of persisting the incoming documents or messages to the file system in a queue overflow situation. Note: The maximum depth of queue might be reached during peak loads or while processing large documents. Monitor the queues during these times to ensure that the queue depth is large enough so that it does not overflow. See "Appendix C - component-specific system attributes" on page 223 for the list of attributes used to manage queue overflow. Generating summary data About this task WebSphere Partner Gateway periodically summarizes data about system activity. This Summary Service data is the information you see when you use the Document Analysis or Document Volume Report functions. You can view and edit how often the summary data is generated with the Summary Service Properties window. This window also displays the date and time that the summary data was last updated. To change the time interval that summary data is generated: 1. Click System Administration > Event Processing > Summary Service. The Console displays the Summary Service Properties window. 2. Click the Edit icon next to Processing Interval (in Minutes). 3. Type a value (from 1 through 60) indicating the number of minutes that should occur before data is summarized again. The default value is 15. 4. Click Save. © Copyright IBM Corp. 2007, 2008 187