Processing Reports Manually or Automatically

This topic covers these screens:

Scheduling/Indexing tab

The Scheduling/Indexing tab shows characteristics of the processing options for each report type (or blueprint). From this tab you can specify to run your reports manually, schedule them for automatic processing, and configure the options for automatic report processing. Access this tab by selecting Edit—Add/Edit Blueprint from the Blueprint Manager screen, then select the Scheduling/Indexing tab.

Edit Scheduling/Indexing Screen

The Edit Scheduling/Indexing screen lets you edit the characteristics of the processing options for each report type (or blueprint). From this screen you can elect to run your reports manually, schedule them for automatic processing, and configure the options for automatic report processing. Access this tab by selecting Edit—Add Blueprint from the Blueprint Manager screen, select the Scheduling/Indexing tab, then select Edit.

Options

Field

Description

Enabled for Scheduling

Whether to schedule the report for automatic processing. (Options: Yes or No)

Find Reports in:

The location where the generated report is placed when ready for processing through Report Parser. This might also be referred to as the watched directory.

Run

How often the watched directory will be scanned for reports to process. Options are:

  • On Demand: manual mode

  • At a Fixed Interval: automated processing every n minutes

  • On a Fixed Schedule: automated processing on scheduled day(s) and time(s)

Note: After an input report is processed, Report Parser moves it from the watched directory (for example, C:/<stellent_dir>/
custom/reportparser/data/Input), and moves it to the Save Input directory (for example, C:/<stellent_dir>/custom/reportparser/data/SaveInput).

Indexing

The indexing method to use for the published report. This relates to how the report is searched upon from users of the content server. Options are:

  • Content and field information: Search engine will index both the content of the report and its associated Field Info fields. (Provides optimum search capability on content server)

  • Field Info Only: Search engine will index only the report's associated Field Info. (Users on the content server will be limited to searching on Field Info fields only.)

Checkin Failures Before Aborting Run

An operational parameter that allows the check in process to run up to the specified number of failures. The default value is zero, which means to quit on the first checkin failure.

Number of Concurrent Checkins

A timing parameter that limits the number of output files that can be checked in to Content Server simultaneously, that is, by parallel threads within the Report Parser process. Setting this value to zero forces the output files to be checked in serially (i.e., document[N+1] can't be checked in until the checkin of document[N] has finished).

Level of Detail in Log Files

The amount of detail in the log reports. Options are:

  • Terse: lowest level of detail

  • Verbose: [in version 5.1, same level of detail as terse]

  • Debug: highest level of detail