EMG 5.2.19 - User's Guide

4. Configuration

4.1 General

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.

Comments can be added either on separate lines if line starts with "#" or inline by adding a "#" preceeded by a space.

# This is a comment
PROTOCOL=SMPP # This is also a comment

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:

· One incoming connector for MGP (used by the EMG client programs)

· One incoming connector where messages will be received

· One outgoing connector which connects to an SMSC or similar

For more information on connectors and how to configure them please consult the chapter Connectors.

4.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:

· The connector protocol cannot be changed

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.

4.3 Testing a configuration

After installing and configuring EMG consider the following:

· When starting emgd, does any messages that indicate a problem with the configuration file show up in the general log file (default EMGDIR/log/general)?

· If EMG is to be used as a converter with both incoming and outgoing connectors, first verify that the outgoing connector(s) work(s). Use the emgsend command-line utility to "inject" messages into EMG and use the server.cfg keyword ROUTE or the routing table to make sure incoming messages from emgsend (MGP protocol) will be routed to the correct outgoing connector.

· Check the connector logs (default EMGDIR/connector.*). For each message received and sent on a connector there will be a corresponding entry in the connector log file.

· Enable (LOGPDU keyword) and check the PDU logs (EMGDIR/pdu.*). For each message received and sent on a connector there will be a corresponding entry in the PDU log file.

· Use the "-debug" option with emgd to generate complete debug information. This information will be appreciated by EMG support engineers when helping out in troubleshooting an installation. The debug information will both be displayed on stdout and stored in the general log file.

· You should empty the log files from old information by simply removing the files before starting emgd. The files will be created if they does not exist when emgd is started.

4.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.

4.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
HOSTID=000c29b5d108
COMPANY=DEMO
TELNO=123456
SERIAL=emgDEMO
LICENSEDATA=30/Dec/2009-30/Dec/2009-0-0-1
ACTIVATION=D8055F1BC5119EFB79B51C378CF01E6292CCCA6D