Home
System administration
As an EngageOne Server system administrator you will be responsible for configuration, diagnostics and account activities.
The configuration framework

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

The configuration framework

The configuration settings are stored in an XML file called config-settings.xml and the file location (typically <bundle-root>/conf/config-settings/config-settings.xml) is defined during the EngageOne installation process.

Its main features are:

the config-framework has a timed reload that will refresh configuration settings when changes are made to the config-settings.xml file.
the config-framework has the ability to separate multiple like settings by using setting groups. The setting groups are mainly used to maintain node specific settings within a multi-node environment. Config-framework will always try to retrieve a setting from a setting group according to its defined setting group level key. If a setting group is not present then the config-framework will search for settings defined at a higher, more global level that are not distinguished or associated specifically by a setting group.

It is recommended that you backup the file prior to making any changes. Although changes can be performed manually, use caution when any updates are applied to this configuration file as incorrect values, keys or namespaces may cause unpredictable behavior within the application.