162 IBM Content Manager OnDemand Guide
7.1  Introduction
Before documents can be loaded into Content Manager OnDemand, they must be indexed. 
These indexes can be created during the load process (OS/390 indexer), directly before the 
load process (Advanced Function Presentation (AFP) Conversion and Indexing Facility 
(ACIF), OS/400, XML, and Portable Document Format (PDF) indexers), or before the load 
process (Generic indexer). When the indexes are not created as part of the load process, they 
are stored in an index file. The index file contains the index values that are associated with 
the document and “pointers” to the documents. Y ou cannot load documents into Content 
Manager OnDemand without index values.
The index values are text strings that occur in the documents, for example, “John Doe”, or 
“Account 1234”. One or more index values identify a unique document in Content Manager 
OnDemand.
An indexer extracts the index values and optionally stores them in the index file by examining 
the documents and copying the index values into the index file according to criteria that are 
specified by the user. Depending on the indexer that is used, the data and indexes are either 
directly loaded into Content Management OnDemand or are stored in a set of files that are 
then read by the load process to store the data to Content Manager OnDemand. The indexer 
creates the following files:
/SM590000Output file (.out file extension), which contains the documents to load
/SM590000Index file (.ind file extension), which contains the index values for the documents
The indexer might also create a resource file with a .res extension, which contains the 
resources that are extracted from the documents.
Operationally, the loading process arsload calls the indexer that is specified on the Indexer 
Information tab for the specified application. Depending on the indexer type, arsload 
performs one of the following tasks: 
/SM590000Creates a set of files that is then loaded by the arsload program into the Content Manager 
OnDemand System
/SM590000Directly passes the indexing and document information to the arsload program so that 
they can be loaded into the Content Manager OnDemand System
On Content Manager OnDemand for i, arsload is embedded within the (ADDPRPTOND) user 
interface. Therefore, run the Add Report to Content Manager OnDemand (ADDPRPTOND) 
command instead of ARSLOAD.
It is possible for the indexing to complete successfully but for the load to fail. The following 
reasons are the most common reasons for a loading failure:
/SM590000Using insufficient system resources
/SM590000Connecting to the wrong database
/SM590000Extracting the wrong index value from the document
For information about investigating and resolving common load failures, see 18.1.2, “Indexing 
and loading issues” on page 379.