Knowledge Base >> Ignite Email Overrides

Ignite Email Overrides - Confio Article 1613

Confio Article: 1613 Published: Sep 22 2011 1:38 PM
Version: 7.0+ Topic(s): Install and Setup Ignite Management
Product(s): Ignite
Database(s): All

Ignite Email Overrides

At times it may be necessary to override the email links that appear in the message content. This is necessary if:

  1. The internal name of the Ignite server machine is different than what it is publicly known as, or
  2. The name of the Ignite server machine contains double-byte characters.

  

For example, in the Confio demo environment, the machine name is CONFIODEMO but the publicly known name is DEMO.CONFIO.COM. By default, alert emails will contain a link similar to http://confiodemo:8123/... which will not work. In this case we need to override the machine with demo.confio.com.

 

To Override Email Settings

 

Edit the following file on the Ignite server machine, then uncomment and set the appropriate property:

<IgniteHome>/iwc/tomcat/ignite_config/idc/system.properties

 

com.confio.iwc.emailLinks.urlOverride=

Overrides the protocol, host and port used when building links back to the Ignite web client.

Format: http[s]://host:port
Examples: http:/demo.confio.com:8123, https://61.34.879.2:8090

com.confio.iwc.emailLinks.hostOverride=

Overrides the host used when building links back to the Ignite web client.  If the host name that Ignite is installed on has double-byte characters (e.g. Japanese, Korean, Simplified Chinese, etc.), set this to either the IP address of the Ignite host machine or to a mapped name (e.g. mapped locally on the host or in the DNS server) that does not contain double-byte characters.Ignored if urlOverride (option 1 above) is configured.

Format: name of host
Example: demo.confio.com, 61.34.879.2

com.confio.iwc.emailLinks.portOverride=

Overrides the port used when building links back to the Ignite web client. Ignored if the urlOverride (option 1 above) is configured.

Format: port number
Example: 8090


If you modify any of these settings, restart the Ignite server.