The term email daemon is frequently used when discussing the internal components of the Email Engine. For example, "email daemon" is used to describe background processes launched at start-time, email "handlers," the use of various threads to carry out different tasks like sending and mails, parsing instructions, and so on. In UNIX, these background processes are usually called "daemons," whereas for Windows they are called "services." Following the UNIX convention, the file you use to set parameters for the Email Engine is called EmailDaemon.properties. For the most part, the Email Engine as synonymous with the email daemon.
When the Email Engine is installed, the EmailDaemon.properties file is created in the Email Engine installation directory and is populated with the name of your organization's email server, user name, and password. The main purpose of the EmailDaemon.properties file is to identify the AR System server your Email Engine communicates with.
Sample contents of EmailDaemon.properties file
(Click the image to expand it.)
To use the EmailDaemon.properties file, see Settings in the EmailDaemon.properties file.
Updating the EmailDaemon.properties file
If your email environment changes — for example, if you need to change a server name or a TCP port — the EmailDaemon.properties file must be updated. The following procedure explains how to update the file.
- To update the value of one property at a time, open a command prompt, navigate to the Email Engine installation directory, and execute the following command:
JREInstallDiris the path of your JRE installation.
jarFileNamesSeparatedByColonsare the jar files listed in the command line of the command line from EmailStart.bat or emaild.sh file.
To use this command, you must properly set the library path for all UNIX platforms.
- To update the values of multiple properties simultaneously, add them to EmailStart.bat (Windows) or emaild.sh (UNIX) and running the executable.
Email Engine startup parameters
Server where the email forms (and the configuration information) are located.
AR System Application Service password. The Email Engine requires the same password that is supplied on the Connection Settings tab of the AR System Administration: Server Information form. To avoid authentication failures, the application password must not exceed 20 characters.
TCP port for the server to which the Email Engine should connect.
RPC number of the server to which the Email Engine should be connected. Use this parameter to connect to a private server. This can enhance performance if you expect a high volume of mail.
Language to be used. (The default is C.)
Directory where the EmailDaemon.properties file is located. If this parameter is not supplied, the system assumes that this file is stored in the same directory as the emaildaemon.jar file.
Time interval (in minutes) to use when checking the server for configuration updates (modifications to records in the Email Mailbox Configuration form). The default is 30 minutes.
Encrypts the given string and returns the value to the command line.
The temporary directory to be used for internal Email Engine files.
Monitor module interval (in minutes) to wait before trying to start the Email Engine again. The default is 30 minutes. When the AR System server is not available, it tries to restart the system for every 30 minutes by default.
(For 32-bit JVM only) MAPI sent folder where sent mail should be stored.
Displays the client version; does not take any parameter.
Changing property values does not affect the current instance of the email engine. To use the updated property values, you must restart the email engine service manually. When using EmailStart.bat or emaild.sh to restart the service, make sure to remove all the parameters you used to update the property values.