Determines the method that Content Manager OnDemand uses
to compress the input data. See Data
Compression for details.
Resource Compression
For AFP and Metacode, determines the method that Content Manager OnDemand uses to compress resources.
See Resource compression for
details.
Large Object
The indexing program generates a large object by dividing very
large documents into smaller parts and defining the indexing information
that is used to retrieve the documents. When your users work with
large objects, they should be able to retrieve documents faster with
less impact on the network. For example, suppose that a document contains
10,000 pages; using large object support, you divide the documents
into parts that contain 100 pages each. When users retrieve one of
the documents, Content Manager OnDemand sends
only the first part of the document to the client. Other parts of
the document are automatically sent to the client when the user moves
to different pages of the document. Documents that require a large
amount of storage (even when compressed) can also benefit
from large object support. When you choose Large Object, Content Manager OnDemand displays the Number of Pages
field. Specify the number of pages to include in each segment of the
document when Content Manager OnDemand divides
the document up into smaller parts. 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.
The corresponding parameters are shown in the following
table:
Table 1. Corresponding parameters
Load information parameters
Indexer parameters
Large Object = Yes
INDEXOBJ=ALL
Large Object = No
INDEXOBJ=GROUP
Number of Pages
When you select Large Object, determines the number of pages that Content Manager OnDemand divides documents into.
This is the number of pages that Content Manager OnDemand retrieves
and decompresses at a time. You can specify a number from 1 to 1023.
Compressed Object Size (K)
Determines the number of bytes in a fixed-size block of data stored
on the system. By default, Content Manager OnDemand compresses
input data into 100 KB blocks. You can specify a number from 1 to
99999. However, IBM recommends that you accept the default value.
Specifying too small of a value can result in less optimal document
compression. Choosing too large of a value can result in less efficient
document storage and retrieval. The value of the compressed object
size must be less than or equal to the size of a storage object for
the application group to which the application belongs. The default
size of a storage object is 10 MB. The maximum size of a storage object
is approximately 100 MB. See the Storage Management page in application
groups for more information about defining the size of a storage object.
Resource Comparisons
Indicates how many resource group comparisons to make in order
to determine whether the data that is loaded has a different resource
group from a resource group that is already stored in Content Manager OnDemand. Enter a value in the range
of 0 - 9999. The default value is 50. This value applies to the data
type of AFP, PDF, and Metacode only.
Application Group Database Name
The list of application group database fields into which data
can be loaded (the list excludes the application ID field). Select
a field name from the list and specify its preprocessing parameters.
Load ID Name
For the selected database field, the name of the corresponding
index field in the index file. If the name of the database field is
not the same as the name of the index field, you must type the name
of the index field in the Load ID Name field. Content Manager OnDemand uses the name that you provide
to load the index values into the correct database field. The Load
ID Name can be a maximum of 100 bytes.
Default Value
There are two primary uses for the Default Value field:
Not every indexed item in the input data contains the field. If
an indexed item does not contain the field, then Content Manager OnDemand uses the default value.
For example, assume that awards is a string field. You type
NONE in the Default Value field. When the field does not exist in
an indexed item, Content Manager OnDemand stores
the characters NONE in the database field.
The input data does not contain a date. You must type a value
in the Default Value field, because every application group must contain
at least one date field. You can type a t (lowercase letter
t) to cause Content Manager OnDemand to
store the date that the input was loaded into the system into the
database field. You can also type a specific date. This might be useful
when you need to load an input file that is several years old; Content Manager OnDemand stores the date that you
specify into the database field.
If the index field does not exist in an indexed item and you
do not provide a default value, then the load fails. If the index
field exists in the indexed item, then Content Manager OnDemand always uses the value of
the indexed item.
Format
If the selected database field is a date or date/time field, verify
the format specifier that describes the appearance of the date or
date/time in the data.
Divide By
Determines the number of decimal places for Small Int, Integer,
Big Int, and Decimal fields. The default is 1 (no decimal places)
for Small Int, Integer, and Big Int fields and 100 (two decimal places)
for Decimal fields. The Divide By field is used with the Embedded
( Character removal) field to
correctly store decimal values in the database.
Character Removal
For the selected database field, specify up to 64 characters that Content Manager OnDemand removes from the index values
extracted from the report, before loading the index data into the
database. Content Manager OnDemand can remove
embedded, leading, and trailing characters from the index values.
For Small Int, Integer, Big Int, and Decimal fields, Content Manager OnDemand automatically places a comma
and a period in the Embedded field and a blank character in the Leading
and Trailing fields. For date fields, Content Manager OnDemand automatically places a blank
character in the Embedded, Leading, and Trailing fields. See Character removal for details.
Use Page Identifiers
For AFP data that contains page
identifiers, select the Use Page Identifiers checkbox so that
the Content Manager OnDemand client programs
list the page identifiers in addition to the sheet numbers. Users can move to pages
of a document by using the page identifiers or sheet numbers. Note:
If you select Large Object, then selecting Use Page Identifiers can
result in a significant amount of overhead when storing and retrieving
documents. Content Manager OnDemand must
extract the page identifiers when loading the data and keep track
of the page identifiers when a user retrieves a document for viewing.
Postprocessor Parameters
An operating system command or user-defined program that Content Manager OnDemand calls to process all of
the index records before loading them into the database. Type the
full path and name of the command or program in the space provided.