Skip to main content
Question

Recommended configurations for new Notifier, Escalation Scheduler and Auto Close Scheduler

  • April 2, 2025
  • 1 reply
  • 32 views
D
Do Gooder (Customer)
Forum|alt.badge.img+7

Hello, 

We are beginning the process of looking at upgrading our assyst version to 24R2SU2, and are investigating these three new programs: Notifier, Escalation Scheduler and Auto Close Scheduler. We have not been able to find much in the way of suggested configuration information on the wiki. 

The main question we have is when these programs are installed using the assyst installer, do they each need to be installed on all servers? “Notifier” if the only one of these that is checked off to be installed by default in the installer, so we must assume that for rule based notifications to work, it must be installed on all servers running the application? For Escalation Scheduler and Auto Close Scheduler to work, do they need to be installed on all servers or can they be installed only on our integration server(s) or on one server. 

Our setup is such that we have a number of web servers which are load balanced behind our URL, then a couple of servers which are primarily only used for back-end integrations. 

Any advise would be appreciated. 

 

Thanks, 

 

Duncan

A
Hero (Employee)
Forum|alt.badge.img+6

Hi

These do not need to be installed on every server, you can pick a specific server (or set of servers) to be the host for these processes. This can be a good idea when you are in the stage of creating your configuration for these, since logging will appear only on the one server.

In a production servers its maybe a better idea to provide multiple servers that have these capabilities so you do not need to plan down time for your auto closure server (for example) and you are protected against unexpected downtime which might exist if you have a single point of failure.

All of these capabilities are messaging system or scheduler backed, both of which has persistence guarantees, so should you have a single point of failure the worst outcome should just be a delay rather than missed auto closure, escalation or notification. Of course, where SLAs are present delays may not be desirable though.

If your concern is load/resources these capabilities should be very light weight. An auto closure processor doing nothing uses very few resources for example.

Hope that helps. 

   

P
1 person likes this
  • P
    Paul McCulloch

Reply


Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings