This documentation supports the 9.1 version of Remedy Action Request System.

To view the latest version, select the version from the Product version menu.

Email engine service failover in a server group

In this topic:

Service failover scenario 1

Consider a scenario where you configure BMC Remedy Email Engine in a server group environment, behind a load balancer, and one of the AR System servers goes down. Since everything is routed via the load balancer, the associated email engine service continues to run.

To configure Email engine behind a load balancer, perform the following steps:

  1. Open the EmailDaemon.properties file located in the ARSystemInstallDir\BMCARSystem\AREmail folder and modify the following properties to point to the AR System server alias:
    Here, the value for server name is the server name in the ar.cfg file. Password is the encrypted value of Remedy Application Service user. For more information, see Understanding server group naming.

    • com.bmc.arsys.emaildaemon.serverName.TCP
    • com.bmc.arsys.emaildaemon.serverName.Password
    • com.bmc.arsys.emaildaemon.serverName.Language
    • com.bmc.arsys.emaildaemon.serverName.Interval
    • com.bmc.arsys.emaildaemon.Servers
    • com.bmc.arsys.emaildaemon.serverName.RPC
    • com.bmc.arsys.emaildaemon.serverName.Authentication
  2. Open the C:\WINDOWS\system32\drivers\etc\hosts file and add the following alias entry, and save the file:
    IPAddress serverName
    Where,
    IPAddress
    is the IP address of the load balancer
    serverName is the server name alias of the load balancer

Service failover scenario 2

Consider another scenario, where you configure Email Engine in a server group environment, behind a load balancer, and one of the Email engine services (inbound email) goes down. The second email engine service now handles both the inbound and outbound services.

Note

When you configure two Email engines (Email Engine1 and Email Engine2) in a server group environment, by default, Email Engine1 will be the Rank 1 server for both inbound and outbound services. 

To configure Email Engine1 as the primary server for inbound, and Email Engine2 as the primary for outbound, you must perform the following steps:

  1. Open the AR System Service Failover Ranking form.

    For the following entries, change the values in the Rank field to 2.

    • Entry for Email Engine1 outbound service.
    • Entry for Email Engine2 inbound service.

Service failover scenario 3

In this scenario if you have multiple email engines, where multiple mailboxes are configured. In such scenarios you can set ranking 1 for mail boxes from either of the email engines. For example, you can set ranking 1 for incoming mail boxes on one Email Engine and set the ranking 1 for outgoing mail boxes on another Email Engine. You can specify these rankings in the AR System Service Failover Ranking form.  Also, when you have multiple mailboxes (service names), all those entries are populated in the AR System Service Failover Ranking form. See, Changing the ranking of a service provider.

The following diagram illustrates the scenario.

Related topics

Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Vladimir Filimonov

    Hello, Could you please clarify what should be the value of Service Name in the AR System Service Failover Ranking form? In KA https://communities.bmc.com/docs/DOC-51548 the naming convention is not described very clearly as well. For example, is it required only to have the below two values for incoming and outgoing: com.bmc.arsys.emaildaemon://incoming/INCOMING_MAILBOX com.bmc.arsys.emaildaemon://outcoming/OUTGOING_MAILBOX

    Or we also need to specify the other two? And if yes, is "ARGOSOFT_INCOMING_POP3" the Mailbox Name?

    com.bmc.arsys.emaildaemon://incoming/ARGOSOFT_INCOMING_POP3 com.bmc.arsys.emaildaemon://outcoming/ARGOSOFT_OUTGOING_SMTP

    Thank you,

    Nov 02, 2017 05:16