IBM E02HRLL-G Administration Guide - Page 166
Document Manager workload, Document structure, Increasing the heap size, Collating data for multiple
View all IBM E02HRLL-G manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 166 highlights
2. Select the Websphere Partner Gateway component. 3. Select Java and Process Mgmt > Process Definition > Java Virtual Machine. 4. Update the values for Initial Heap Size and Maximum Heap Size 5. Restart Websphere Partner Gateway. Document Manager workload The number of processing threads used can be configured for several subcomponents by setting system properties. The default values for these properties are low but they might have been modified by the administrator. Look for properties involving thread configuration in the configuration tables in "Appendix C - component-specific system attributes" on page 223. Document structure Large documents can come either from the external partner or the internal partner (backend application). Determine if there are ways to reduce the document sizes, such as reduced batch sizes or using smaller documents. Increasing the heap size About this task Whenever sending a large number of documents (approximately 40) that have a size of 50MB with encryption, signing, and compression over AS3, it is necessary to increase the heap size. If the heap size is not increased, documents can fail with the error OutOfMemory. The OutOfMemory error is the result the working memory not being sufficient for the Websphere Partner Gateway to route the documents in bulk. Therefore, it is recommended that you increase the heap size. To increase the heap size parameters for the DocMgr server, perform the following steps: 1. Log into the WebSphere Application Server admin console. 2. From the WebSphere Application Server admin console, select java and process management > Process Definition > Java virtual machine for the bcgDocMgr server. 3. Set the initial heap size to 1024. 4. Set the max heap size to 1536. If the system has more than 2GB, then max heap size can be set to a value higher than 1536 value. Collating data for multiple languages WebSphere Partner Gateway depends on the underlying databases for collating data. If your installation supports multiple languages and your Unicode data is not sorted correctly, review this section. DB2 Since version 6.0, WebSphere Partner Gateway configures DB2 to use the UCA400_NO collating setting. DB2 version 8.2 does not support all special cases (as described in Unicode Standard version 4.00 Technical Standard #10) for all languages. In these instances contact DB2 directly. Oracle 160 IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide