Home
Batch processing
Process accumulated requests from EngageOne™ Interactive, or process your own multiple or individual files, in a scheduled, or ad hoc manner.
Batch error handling
Error handling for accumulated and non-accumulated batch have some differences.

Overview
Configure and manage operating modes and user roles.
Getting started
Information on creating and configuring communities, running the EngageOne™ Server Administration and common features available in the web application.
Template management
Template management allows you to create and organize folders that contain templates and Active Content, created in EngageOne™ Designer and imported into EngageOne™.
External File management
External resources not contained in the template, succh as images (key maps or keyed images), lookup tables, and RTF files.
Delivery management
Before you can use a template in EngageOne™ Administration you must define a device for viewing and define at least one delivery option.
Community Administration
Features for managing shared community document classes, retention policies, spelling dictionaries, data maps, and diagnostics.
System administration
As an EngageOne™ Server system administrator you will be responsible for configuration, diagnostics and account activities.
Event Monitor
Events related to the document cycle and administration, these are captured throughout the system and sent to the Event Monitor.
Batch processing
Process accumulated requests from EngageOne™ Interactive, or process your own multiple or individual files, in a scheduled, or ad hoc manner.
- Accumulated batch
  The process of submitting documents for batch delivery in EngageOne™ Interactive is referred to as accumulated batch.
- Non-accumulated batch
  In NA batch, which is a traditional batch process, the batch process accepts one or more input files containing document data sets, as well as optional processing instructions.
- NA batch setup and performance optimization
- Purging using batch
  Running purge is an important maintenance activity to prevent gradual performance degradation due to the build-up of data in the database tables. Make sure you implement a purge routine as part of your EngageOne™ Server maintenance plan.
- Log file location
- Logging information (accumulated and non-accumulated batch)
- Modifying log file count
- Batch error handling
  Error handling for accumulated and non-accumulated batch have some differences.
  - Batch exit codes
    Use this table to understand batch exit codes. Exit codes are the same for accumulated and non-accumulated batch.
- Batch threshold settings
  The threshold level is the limit where a running batch will terminate, if the number of processed documents that have errors has been reached.
- Setting up the batch programs on a separate machine
- Running batch with integrated security database connections
Managing your EngageOne™ environment
Best practices for managing your EngageOne™ and safeguarding your environment.
EngageOne™ Server system monitoring
This section describes how to monitor the EngageOne™ Server system.
Notices

Batch error handling

Error handling for accumulated and non-accumulated batch have some differences.

Error handling (accumulated and non-accumulated batch)

Any composition errors are reported to the log file and an incident archive, which are located at <active-drive>/incident-archive/dca.
If the errors are at the document level, the program will still continue until the threshold is reached. This is defined in the configuration framework file see Batch threshold settings.

Additionally, error occurrences for non-accumulated batch are handled as follows:

If the errors are at the document level, the program will still continue until the threshold that is defined in the configuration framework file is reached see Batch threshold settings.
If the error is non-document level, the batch process will fail.
If there are errors in the first step, a log file containing the error information and resource (answer file, etc.) will be copied to the error directory <Batch bundle installation folder>.
When there is an error in composition, DCA produces an incident archive.
The log file will contain all information including the errors.
An Event Monitor NaBatchJobFailedEvent is sent only when the batch job failed.
Standard logging (commons-logging) to a file will be used to track events and errors in the application.