Home
Batch processing
Process accumulated requests from EngageOne Interactive, or process your own multiple or individual files, in a scheduled, or ad hoc manner.
NA batch setup and performance optimization
Areas affecting NA batch performance

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

Areas affecting NA batch performance

An NA batch run can be processed in several ways, based on how the delivery channel rules are configured. Within the delivery channel configuration for your batch run, you can configure rules around inclusion conditions, sorting and partitioning of the output record.

NA batch performance is affected by the following setup items:

The structure and the number of XML files in your input directory used to trigger batch processing.
The output variables used for any delivery channel.
Inclusion conditions - define if a document is included in a batch stream.
Sorting - defines how documents are ordered in a print file, and any associated report or index.
Partitioning - defines how the output record of an output document is separated.

The best batch performance is achieved when the following items are adhered to:

A single XML file in the input file in directory is used to trigger batch processing.
The XML file used to initiate batch processing contains one records element with associated template, deliveryOption, and data elements.
Inclusion conditions and/or sorting should not be applied to any delivery channel present for the chosen delivery option.
The only output variables that should be used in any delivery channel present for the chosen delivery option are:
- ${SYSTEM_TIME}
- ${COMPOSITION_DATE}
- ${INCREMENT}
The File Partition Number for any delivery channel present for the chosen delivery option should be set to the same value, either 0 or 1.
Note: Although improved performance can achieved when the File Partition Number is set to 1, a value of 0 will give the best performance with the set up scenario described above.