Each eaDirect application requires certain batch jobs run on a recurring basis to make statement data available for online viewing.
The specific number and type of production (batch) jobs you need to create and configure depends on the type of input file your application uses, and the number and type of views the project team has developed in your application.
You may need to create and configure a combination of the following jobs for an application:
· An Indexer job, if your application uses live retrieval to index the data file in preparation for live statement viewing on the web. Applications using live retrieval must have an Indexer job. An Indexer job is also necessary to enable you to generate email output. See Why Do I Need an Indexer Job? and Creating and Configuring an Indexer Job.
· An EmailNotification job, if your application has an email notification view to send an email message to enrolled users informing them that a statement awaits them online. See Creating and Configuring an EmailNotification Job.
· A Purge App job to periodically delete old data from the index, email, report activity, detail, annotations, and dispute tables. See Database Administration and Creating and Configuring a Purge App Job.
· A Purge Logs job to periodically delete old data from the logs table in the database. See Database Administration and Creating and Configuring a Purge Logs Job.
· HTML Output or XML Output jobs are necessary only if you plan to provide users access to static output; not live retrieval.
· A Detail Extractor job is necessary only if you plan to upload recurring table data from the input file to a database table for merging using additional application functionality.
· A Report job creates report data from indexed statements for enrolled users (in the Master application). You must run an Indexer job against this data using the Report application before users can view reports.
· A JIT Report Collector job collects JIT reports into one file, to be indexed by the Report application's Indexer job. Also deletes JIT reports that have been indexed.
· Hierarchy Assignment and Hierarchy Registration jobs only if you use the hierarchy manager feature and need to import an existing hierarchy to your system.
· An XMLLoader job is necessary to index data only if you use xml input files.