Content Manager OnDemand large objects
Content Manager OnDemand large object support is designed to provide enhanced usability and better retrieval performance for reports that contain very large documents. For example, suppose a report contains statements that typically exceed 1000 pages. With large object support, the statements can be divided into parts of, say, 100 pages. When a user views a statement, Content Manager OnDemand retrieves and decompresses the first part of the statement. To view a specific page of a statement, the user can choose the Go To command in the viewer window and type the page number. Content Manager OnDemand automatically retrieves and decompresses the part of the statement that contains the requested page. When the user moves from page to page of a statement, Content Manager OnDemand automatically retrieves and decompresses parts of the statement as needed.
When you use large object support, users should experience consistent response time when moving from page to page of the document. There are several factors that you need to consider when using large object support:
- The report must be indexed with an indexing program that generates a large object by dividing very large documents into smaller parts and defining the indexing information that is used to retrieve the documents.
- The amount of data per page and the number of pages that you divide documents into has an impact on retrieval and viewing response time. The number of bytes per page typically dictates the number of pages that you can divide documents into. In general, the larger the page size in bytes, the smaller the number of pages that you can divide your documents into. For example, if the average page in the document contains 2.5 KB of data, then choose a range of 10 to 100 pages; if the average page in the document contains 50 KB of data, then choose a range of 1 to 5 pages.
- The capacity of your network and the traffic on the network might determine the number of pages that you should divide your documents into. Documents that require a large number of bytes to hold (even when compressed) require more network bandwidth to transfer from a Content Manager OnDemand server to a client. The number of users concurrently accessing Content Manager OnDemand and the types of documents being retrieved determine the overall load on the network.
- Response time requirements. The goal of Content Manager OnDemand large objects is to provide better performance and usability. Large object support clearly provides enhanced usability. However, you must implement large object support so that dividing your documents into parts provides better overall performance than other methods of segmenting the input data.
When you choose Large Object, Content Manager OnDemand displays the Number of Pages field. Specify the number of pages that you want Content Manager OnDemand to divide documents into in the Number of Pages field.
To generate large objects, the Indexer that is specified on the Indexer Information page must be ACIF, 390, or 400. When you select the Large Object checkbox, Content Manager OnDemand automatically adds the INDEXOBJ=ALL parameter to the indexing parameters (which causes the indexing program to generate the large object indexing information). When you remove the check from the Large Object checkbox, Content Manager OnDemand automatically changes INDEXOBJ=ALL to INDEXOBJ=GROUP. When you change or remove the INDEXOBJ parameter on the Indexer Information tab, the corresponding change is made to the Large Object setting. These two attributes must be kept in sync when using the ACIF or 400 indexer. For the 390 indexer, the Large Object setting is the only attribute used to determine if documents are stored as large objects.
Load information parameters | Indexer parameters |
---|---|
Large Object = Yes | INDEXOBJ=ALL |
Large Object = No | INDEXOBJ=GROUP |