Home
Batch processing
Process accumulated requests from EngageOne Interactive, or process your own multiple or individual files, in a scheduled, or ad hoc manner.
Modifying log file count

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

Modifying log file count

This feature allows you to specify the maximum number of batch log files to maintain via the configuration framework or adding a parameter when starting up any batch process (A-Batch, NA-Batch, purge, etc.).

Use the appropriate namespace; com.pb.engageone.server.batch (for accumulated batch), or com.pb.engageone.server.batch.na (for NA-Batch) when making changes in config-settings.xmlconfiguration file. Refer to the NA-Batch example below:

<namespace name="com.pb.engageone.server.batch.na"> . . . .
<setting>
<setting>
<key>log.maxFileCount</key>
<value>10</value>
</setting>
. . . .
</namespace>

To enable this feature, you can either edit the config-settings.xml file entries, or override these settings by adding the maxLogFileCount parameter, note that this parameter accepts integer values, i.e. "1", "10", "25", etc.

Example

run-na-batch.bat -dir D:/temp/input1 -domain engageone -deliveryOption
"Batch Print" -maxLogFileCount 10

logback-global.xml

Below is the default configuration for RollingFileAppender, you can find this section in logback-global.xml file present in <batch bundle installation folder>/conf/logging:

<appender name="file-rolling" class="ch.qos.logback.core.rolling.RollingFileAppender">
 <file>../logs/${contextName}.log</file>
 <encoder>
 <pattern>[%date | %-5level | %1logger] %msg%n</pattern>
 </encoder>
 <rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy">
 <fileNamePattern>../logs/${contextName}.%d{yyyy-MM-dd}.%i.log</fileNamePattern>
 <maxHistory>300</maxHistory>
 <maxFileSize>10MB</maxFileSize>
 </rollingPolicy>
 <prudent>true</prudent>
</appender>

Log formatting

The following conversion pattern is used:

[%d{MMM dd HH:mm:ss}]|%-5p|%c|[%t]|%m%n

This pattern ensures that output is delimited by the "|" character if you wish to programmatically process log output files. It also ensures that the fields output by NA batch are as follows:

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

An example log message will look like the following:

[Dec 14 15:21:07]|INFO |BatchProgramImpl|[NA Batch Main Thread]|Input
Answer ID: N/A|Input File Name: input_1_record.xml|Done reading xml input file: 
D:\dev\EngageOne_1.1\e1DevEnv\e1_installs\202\input\input_1_record.xml