EMG 5.4.7 - User's Guide
Software configuration is done by editing the configuration files. For server configuration the file EMGDIR/server.cfg is used and for client configuration the file EMGDIR/client.cfg is used. EMGDIR defaults to /etc/emg as described in the Installation chapter.
The configuration files contain a number of keywords used to control the behavior of EMG.
In order to use EMG at least two connectors need to be defined in the server.cfg file. However, it is most common that at least three connectors are defined:
For more information on connectors and how to configure them please consult the chapter Connectors.
5.2 Refreshing the server
After making changes to the server configuration file the changes will not be in effect until the server is either restarted, refreshed or reloaded. The routing table, user files and most options in the configuration file will be refreshed with the following exception:
If any of these options need to be changed you would need to stop and start the server.
During a refresh all open connections will be closed gracefully while during a reload connections will not be closed but only temporarily suspended.
5.3 Testing a configuration
After installing and configuring EMG consider the following:
5.4 The license file
EMG reads license information from a license file, normally /etc/emg/license or EMGDIR/license if environment variable EMGDIR has been set.
When multiple EMG nodes are reading configuration information from shared storage this approach does not work since each EMG node needs its own license key. Therefore emgd first looks for a license file called license.<hostid> and if that file exists it is used.
5.4.1 License expiration dates
Each EMG 5 license key generated has a license expiration date and a support expiration date specified.
In the sample license information below the first date (red color) is the license expiration date and the second date (blue color) is the support expiration date.
The license expiration date can be "0" which indicates a perpetual, non-expiring license. If the license expiration date is set in the license and has been passed then EMG will refuse to run.
The support expiration date is set to the date when support for the license ends. An EMG server with a later build date than the support expiration date in the license will refuse to run.
This way a perpetual license can continue to run forever but cannot be upgraded unless support is renewed (normally once per year) and the license key updated.
# Enterprise Messaging Gateway 5.0 - License file