Home
Managing your EngageOne™ environment
Best practices for managing your EngageOne™ and safeguarding your environment.
Tuning the system for performance
LDAP to database sync

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.
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

LDAP to database sync

EngageOne™ Compose maintains its own index of authorized users and groups for fast searching and type-ahead fields. Comparing this stored index to the latest LDAP data can be costly, so the ${ldap.syncIntervalSecounds} property in deploy.properties configures how often the two are synchronized. By default, this value is 2 hours (7200 seconds).

To modify this value:

Update the setting in your deploy.properties.
Stop the associated service bundle you are tuning.

Run the 'configure' target on the server.

groovy eos.groovy -p deploy.properties -t primary -b core configure

This value should be modified based on your business need and how frequently users are added to LDAP. A smaller value will create additional load on the core primary node, but make the LDAP data appear more quickly in EngageOne™. A smaller value will decrease load but may delay a new LDAP user's ability to use the system.

Note: Changing user and group entities in LDAP affects EngageOne™ role mapping functionality after two minutes.

For example, if the CommAdm group is defined in LDAP as Community Administrator of community1. When user1 is added to this group, after two minutes user1 will be able to use EngageOne™ as a Community Administrator of community1.