Home
Managing your EngageOne™ environment
Best practices for managing your EngageOne™ and safeguarding your environment.
Tuning the system for performance
Java memory tuning

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

Java memory tuning

The Java Runtime memory settings are configured in the deploy.properties file. The default values are tuned to a scenario of 250 concurrent users per node.

security.jvm.settings
core.jvm.settings
composition.jvm.settings
conversion.jvm.settings
batch.jvm.settings

Perform the following steps to modify the JVM settings:

Update the setting in your deploy.properties.
Stop the associated service bundle you wish to tune.
Run the 'configure' target on the server.
For example, if you modify the ${security.jvm.settings} execute the eos.groovy on the security bundle servers:
```
groovy eos.groovy -b security -p deploy.properties -t primary configure
```