Remedy - Email Engine - v.8.1.x The E-mail Engine operation is not assigned to the Secondary AR Server when the service is stopped manually on the Primary AR Server (Server Group) and the Notifications are not sent (Windows)

Version 5
    Share:|

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    Remedy AR System Server


    COMPONENT:

    AR System


    APPLIES TO:

    Remedy AR System E-mail Engine v.8.1.x



    PROBLEM:

    When the E-Mail Engine service on the primary AR Server (Server Group) is turned off manually, the Email operation doesn’t get failed-over to the Secondary E-Mail Engine on the Secondary AR Server.
     


    CAUSE:

    This is as designed in v.8.x


    SOLUTION:

    Email Engine "Failover" functionality 8.x :
    -To make the E-Mail Engine service to failover from AR-Server A to AR-Server B, it requires to stop the main AR System Server service to make the operation move on to Secondary server.
    Stopping the E-Mail Engine service only will not make the "Failover".


    - In the version 8.1.x the failover is driven by AR Server availability and this is working as designed. For service failover to happen the E-Mail Engine service needs to be running.

    -Hence to check if the E-mail Engine Service will work on the secondary server or not, we would need to stop the AR Server Service on the Primary Server and the entry present on the Ranking form will indicate which server should own this operation.

    -From version 9.x  there is the service failover operation for email engine but for 8.x version this feature is not available.
    Documentation available for this feature in version 9.x: Email engine service failover in a server group

    Is there a way to suspend the E-mail Engine's operation in 8.1.x which would be a similar behavior as it happens in 9.x ? 
    In 8.x version if you want to suspend and resume the email engine services, you will need to do it through EmailStop.bat file.


    Suspending email engine in 8.x :
    1- Go to the E-mail Engine's installation directory and locate the file called: EmailStop.bat 

    2- Make a backup of this file for safety purposes.

    3- Edit the EmailStop.bat file as follows:
         Original (example):
                        set JavaPath=C:\Program Files\Java\jre1.8.0_92\bin
                        "%JavaPath%\java" -jar EmailAdminAgent.jar
    stop
         Change it to:
                        set JavaPath=C:\Program Files\Java\jre1.8.0_92\bin
                        "%JavaPath%\java" -jar EmailAdminAgent.jar
    suspend

    4- Save the file.

    5- The Stdout.log will show:
                    Checking connection to server: test.bmc.com ...
                    Application has started Version: 8.1.02 201408260235
                    Using JRE: 1.8.0_92
                    Successfully connected at Aug 9, 2017 6:33:18 AM
                    Suspending Email Service on test.bmc.com ...
                    thread is still alive
                    Email Service has been successfully suspended.


    6- To resume the E-mail Engine, edit the EmailStop.bat as follows:
                        set JavaPath=C:\Program Files\Java\jre1.8.0_92\bin
                        "%JavaPath%\java" -jar EmailAdminAgent.jar
    resume

    7- The Stdout.log will show:
                    Checking connection to server: test.bmc.com ...
                    Application has started Version: 8.1.02 201408260235
                    Using JRE: 1.8.0_92
                    Successfully connected at Aug 9, 2017 6:33:18 AM
                    Suspending Email Service on test.bmc.com ...
                    thread is still alive
                    Email Service has been successfully suspended.

                    Email Service has been successfully resumed.
                    Checking connection to server: test.bmc.com ...
                    Successfully connected at Aug 9, 2017 6:36:05 AM

     


    Article Number:

    000140732


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles