Home
System administration
As an EngageOne™ Server system administrator you will be responsible for configuration, diagnostics and account activities.
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.

Overview
Configure and manage operating modes and user roles.
Getting started
Information on creating and configuring communities, running the EngageOne™ Server Administration 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 EngageOne™ 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 EngageOne™ Designer repository or the EngageOne™ 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.
Notices

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.

Events relating to the document cycle and administration are captured throughout the system and sent to the Event Monitor database for analysis using the diagnostics feature. See Event Monitor for details of how the Event Monitor is configured for tracing activity on your system. If, for example, an e-mail failed because the SMTP server was down, you can set up filter criteria to extract these events and re-submit the e-mails concerned.

A process type defines the type of the event, for example, Create Document, Import Template, Login, etc. An event type is the priority of the event. There are four event type priorities defined in the system: Error, Warning, Informational, and Debug.

Click Diagnostics/ Diagnostics.
Select the event process type from the drop-down list.
Select the required event from the list.
If applicable, enter the unique application identifier from which the event originated.
To refine your search further you can enter a date/time range.
Click here and the returned events from the search criteria entered will be displayed below.
Highlight one of the events and all available details relating to it will be displayed below.
These buttons are activated for Document process types which have an Error type. See below for details.
You can use the Resubmit button if you have fixed any issues relating to the document, the issue is resolved and you want to resubmit the document/work item as if it was being submitted by the document creator.
Notes:
- Only those communities to which the current Community Administrator has rights will be available in the “Community” drop-down list.
- If a community is not specified for the Event search, all events for all the communities to which the Community Administrator has rights will appear.
You can use the Reactivate button if you want to send the document/work item back to the document creator. This option will be used if the front-office user needs to resolve the issue relating to the document.