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.
- Use case 1: Monitoring with Oracle's JConsole
- Use case 2: Monitoring with commercial monitoring tools - example: AppDynamics
Copyright

Enabling JMX (no security)

The following describes how to enable JMX instrumentation in a non-secure manner. Depending on your environment this may be sufficient and is relatively straightforward (in a production environment however, it is strongly recommended that you Enable JMX with the secure option).

Perform the following steps to enable JMX (non-secure):

Stop the bundle service you wish to instrument.
Update the ‘<bundle>.jvm.settings’ property in the deploy.properties file.
In the deploy.properties file each bundle has its own jvm.settings (such as core.jvm.settings, conversion.jvm.settings). You need to add the following settings from Oracle:
- -Dcom.sun.management.jmxremote
- -Dcom.sun.management.jmxremote.port=PORT_NUMBER
  where PORT_NUMBER is an open port of your choice.
- -Dcom.sun.management.jmxremote.authenticate=false
- -Dcom.sun.management.jmxremote.ssl=false
  For example:
```
core.jvm.settings=-Xms1024m -Xmx4g -XX:MaxPermSize=512M -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=9994 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false
```
Run the configureBundle.groovy script to apply configuration.
Restart the bundle service.

For more details on the deploy.properties and the configureBundle.groovy script, see the EngageOne Server Installation Guide.