1,126
edits
Difference between revisions of "Improving Content Manager OnDemand Performance"
Jump to navigation
Jump to search
m
Improving Content Manager OnDemand Performance (view source)
Revision as of 23:21, 24 September 2020
, 23:21, 24 September 2020Many small updates.
(IBM Content Manager OnDemand performance - draft 1) |
m (Many small updates.) |
||
| Line 10: | Line 10: | ||
The single best way to ensure performance stays high for the lifetime of an IBM Content Manager OnDemand server is to structure the Application Groups and Applications well. Doing this from the start will ensure that queries stay fast, as Content Manager OnDemand's database engine won't have to search dozens (or hundreds!) of database tables looking for the information users are requesting. | The single best way to ensure performance stays high for the lifetime of an IBM Content Manager OnDemand server is to structure the Application Groups and Applications well. Doing this from the start will ensure that queries stay fast, as Content Manager OnDemand's database engine won't have to search dozens (or hundreds!) of database tables looking for the information users are requesting. | ||
For example, if a telephone company was using Content Manager OnDemand inside a customer call centre, they might want to have all customer-centric communications combined into a single Application Group. Documents like statements in AFP format, copies of letters mailed to customers in AFP format, scanned handwritten letters or received facsimilie (fax) correspondance in TIF format, recordings of previous calls in MP3 format, etc. This would allow CMOD to complete a request for all the information a customer service agent might need to answer, by searching just a single Application Group. | |||
== Application Group Configuration == | == Application Group Configuration == | ||
* Increase Max | * Increase the "Max Number of Rows" Parameter in the CMOD Application Group configuration, to reduce [[Table Segmentation in Content Manager OnDemand|Table Segmentation]] in the database | ||
* Specify the CORRECT Expiration Type (Document, Load, Segment) | * Specify the CORRECT Expiration Type (Document, Load, Segment) to ensure the proper disposition of documents loaded into Content Manager OnDemand. | ||
* Use Indexes carefully | * Use Indexes carefully - consider using [[IBM CMOD Composite Indexes]] for enterprise Applications using the ODWEK Java API. | ||
== Application Configuration == | == Application Configuration == | ||
* Minimize floating triggers | * Minimize floating triggers - floating triggers make indexing documents very CPU intensive | ||
* use TLEs in AFP data | * use Tagged Logical Elements ("TLEs") in AFP data - the CMOD ACIF Indexer can locate metadata stored in TLEs quickly and efficiently. | ||
* Use PPDs in PDFs for super-fast indexing in CMOD v9.5 and higher | * Use PPDs in PDFs for super-fast indexing in CMOD v9.5 and higher | ||