Home
Batch processing
Process accumulated requests from EngageOne Interactive, or process your own multiple or individual files, in a scheduled, or ad hoc manner.
Logging information (accumulated and non-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.
- 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

Logging information (accumulated and non-accumulated batch)

Non-accumulated batch is a multi-threaded application that processes large numbers of documents, defined by XML records. For this reason, the NA batch log output is formatted in a specific way to make information gathering easier.

All batch processes have a common logging configuration file located in <batch bundle installation folder>/conf/logging. All the configuration is present in file logback-global.xml, its structure and default content are the same as for all other bundles (security, core, composition, etc.).

Each log entry consists of several fields that hold values with different meanings. The number of fields and type of data in each field will be explicitly specified as follows:

For accumulated batch:

<TIMESTAMP>|<LOG_LEVEL>|<CLASS_NAME>|<THREAD_NAME>|<SPECIFIC_MESSAGE>

For NA batch:

<TIMESTAMP>|<LOG_LEVEL>|<CLASS_NAME>|<THREAD_NAME>|<INPUT_ANSWER_ID>|
                                                    <INPUT_FILE_NAME>|<SPECIFIC_MESSAGE>

As in the example above, the fields will be delimited with a "|" character. This allows you to programmatically parse log information from the log file.

Points to note:

The maxFileCount setting can be configured in the configuration framework. For detailed information, refer to Modifying log file count.

The maxLogFileSize and maxLogFileCount command line options override the defaults present in the logback-global.xml configuration file.

The logfile command line option overrides default log file name.

Logging can be configured such that the underlying log file is rolled over at a chosen frequency. See the below link on how to configure the rolling frequency:

https://logback.qos.ch/manual/appenders.html#SizeAndTimeBasedRollingPolicy

More about logging event components called appenders:

https://logback.qos.ch/manual/appenders.html