Home
System administration
As an EngageOne Server system administrator you will be responsible for configuration, diagnostics and account activities.
Resolving composition issues
The alwaysDumpIncidentArchive flag can be used to troubleshoot and resolve problems arising from unsuccessful composition of your communications by EngageOne Generate.

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.
- About system administration
- The configuration framework
- Diagnostics
  NA batch failed events logged and found in Diagnostics may or may not include all of the details about the failure. These events serve as an indicator that something went wrong. Review the NA batch logs for more details about the failure.
- Resolving composition issues
  The alwaysDumpIncidentArchive flag can be used to troubleshoot and resolve problems arising from unsuccessful composition of your communications by EngageOne Generate.
- Repository configuration
  The Repository configuration allows you to change the repository alias or repository name of the Designer repository or the Content Author repository.
- Active Drive configuration
- Account unlocking
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.
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

Resolving composition issues

The alwaysDumpIncidentArchive flag can be used to troubleshoot and resolve problems arising from unsuccessful composition of your communications by EngageOne Generate.

When the alwaysDumpIncidentArchive is set to true the following files are created in the incident-archive folder on the active-drive:

All template files.
All supporting resource files for each template. These are created during Publish for EngageOne processing in EngageOne Designer.

It is important to note that these files are created for both successful and unsuccessful composition; for this reason, setting this flag to true as a default is not recommended.

EngageOne Generate can compose communications either from batch processing requests or via SOAP/UI requests. The alwaysDumpIncidentArchive flag can be used for both types of requests to Generate.

Batch requests to Generate

Depending on the type of batch processing you are working with the alwaysDumpIncidentArchive property must be added to the batch jvm options. Update the appropriate run script, this can be found at:

<engageOneInstallPath>/batch/bin

SOAP/UI requests to Generate

Locate and run eos-compositionw this is found at: <engageOneInstallPath>/composition/bin.

The EngageOne Server composition Service Properties dialog is presented.

Enter -DalwaysDumpIncidentArchive=true in the Java Options entry area.