Home
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.
Resources
Managing resources

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

Managing resources

Resource management requires coordination of the fonts and images used by templates, devices, Active Content, and Message Content. Templates, devices, and Active Content are defined in Designer. Message Content is defined in Content Author. This section explains how to manage these resources effectively. The following diagram shows the resource workflow among Designer, Content Author, and EngageOne.

When the template designer publishes a template, Active Content, or Message Content the device resources are automatically published with the templates using the device previously set up by the output device manager. Subsequent requests to publish a template only convert newly used resources that have not been converted from a prior publishing request. For more information about publishing resources from Designer, see Devices and the Designer User’s Guide.