We are thinking about running 2 instances of Indicium to separate the load. We want to keep one for use with the Universal GUI and another one for possible external processes (which might put more pressure in the service). The thing is that Indicium is responsible for running the scheduled system flows.
Is this possible without both indiciums trying to run the scheduled system flows?
Best answer by Tim Waalewijn
View originalDear Mark,
To explicitly prevent an Indicium from taking on background work as specified by the IAM in connects to, such as system flows, you can set the Agent setting in the appsettings to false as described here:
{
"Agent": {
// Skip registering this Indicium instance as an agent on IAM.
// Also disables adding all agent related services such as the scheduled system flow runner.
"Enabled": false
}
}Do note that only one Indicium at a time will be receiving system flow schedules from IAM. So if you, for example, disabled the agent service on the Indicium that the Universal GUI connects to and then have two others that could both process system flows only one of them will be doing so. Of course if that Indicium were to go down somehow the other one would then take over.
I hope this answers your question.
It seems Anne Buit also attempted to reply and maybe I have clicked the “solved” too quickly, but just to add part of the response for other users. The quick answer is appreciated!
“Having multiple Indicium instances running on the same Intelligent Application Manager will not cause any issues. Both Indiciums will attempt to run system flows but a system flow instance from a schedule can only be started once - only one Indicium ‘win’ the right to run it. This also takes the Multiple running instances setting of a system flow into account. Indicium will not be able to start a system flow instance if the same system flow is still running on another Indicium.”
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.