Home
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.

EngageOne Server overview
EngageOne Administration is used to configure and manage operating modes and user roles.
Getting started
Information on creating and configuring communities, running the EngageOne Server Admin 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 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.
  - Running the accumulated batch job
    You can run the batch job from the command line or scheduler by running one of these scripts.
  - Running batch on a separate machine
    The batch programs can run on a separate machine other than the EngageOne Server provided that it has access to the database, the EngageOne Server JNDI, and the EngageOne Server repository.
  - ONH file recovery mechanism
- 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 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.
Copyright

Accumulated batch

The process of submitting documents for batch delivery in EngageOne Interactive is referred to as accumulated batch.

These documents are queued up or accumulated until you start, or schedule the batch job. Output variables are resolved during composition and saved with the intermediate file in the content repository.

Using this method you have one input file and one HIP file; one pre-defined set of output files is generated. The following diagram illustrates the batch accumulation pipeline.

In accumulated mode an EngageOne batch job is executed for a single delivery channel. Multiple batch jobs can be triggered by a single schedule through development of a batch script, which is typically a .bat or .sh file. Any standard scheduling product can be used, for example, Autosys, CA-7, Windows Scheduler, etc.