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

doc1gen timeout

There is a document generation timeout setting defined in deploy.properties. This property specifies the amount of time (in seconds) the batch or composition bundle will wait until the doc1gen process responds. This property should be increased according to the size and content of the documents being composed.

doc.generation.timeout (default 120 seconds)

To modify these configurations on your composition or batch bundle install:

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 -b composition -p deploy.properties -t primary configure