Improving Content Manager OnDemand Performance

From CMOD.wiki
Jump to: navigation, search

It's possible to improve IBM Content Manager OnDemand's performance by paying close attention to configuration of Application Groups, Applications, and being careful with the usage of the CMOD utilities.

Introduction

When you're first learning about Content Manager OnDemand, there seems to be a huge focus on making it work by any means possible, without considering the future implications of what you're doing. Given that IBM CMOD is an archive product that can store documents for several years before you begin expiring them, there are a lot of problems that are created in those early days when "get it done" is the priority. This article will explain some of the ways to ensure your IBM OnDemand server keeps its lightning-fast performance.

Architecture of Application Groups and Applications

In IBM Content Manager OnDemand, Applications are types of documents that are formatted, structured, and displayed the same way -- in the overwhelming majority of cases, this means a specific type of document or report, like a customer statement, a standardized document (late payment reminders), or summary 'greenbar' report (a list of accounts with outstanding balances, and how many days 'past due' they are). Content Manager OnDemand Application Groups are simply groups of those documents -- which all have the same indexes, retention, storage requirements, and expiration requirements.

Combine business documents into the same Application Group

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

  • Increase the "Max Number of Rows" Parameter in the CMOD Application Group configuration, to reduce Table Segmentation in the database
  • Specify the CORRECT Expiration Type (Document, Load, Segment) to ensure the proper disposition of documents loaded into Content Manager OnDemand.
  • Use Indexes carefully - consider using IBM CMOD Composite Indexes for enterprise Applications using the ODWEK Java API.

Application Configuration

  • Minimize floating triggers - floating triggers make indexing documents very CPU intensive
  • 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

Loading data into Content Manager OnDemand

  • Load in large batches (hundreds to thousands of documents at a time) with small date ranges
  • Load chronologically to prevent breaking table segmentation in CMOD.
  • Use separate Load Servers