10-06-20 07:58 PM
11-06-20 06:30 AM
11-06-20 09:40 AM
Hi,
Have done some testing with pools and the only way I was able to operate the resource properly was through command line. My thinking is that one resource is "acting" for the complete pool, and if you send a reboot request from a job in BP then the pool go offline for a while. ( Not ideal in my book..) But using AutomateC.exe I could adress a specific resource that is not "primary" in the pool currently.
Maybe I should highlight that we used separate ports for the RunTime and the Login agent. So we would have one resource not in the pool, pointing to the LoginAgent resource ; and the "RunTime" resource beeing a member in the pool.
So, basically I would setup a Login schema, pointing to the LA resource, and when executing it ; the resource would become a active member of the pool. I was planning to have a morning job that would add more resources to the pool during the day, and then in the evening fire a few "logout" schemas just to move those resources to another pool. Then something else go in the way…
But maybe these examples of functions could provide a embryo to something for you.
This functionality is something you want in a resilient and dynamic environment! Hope you get closer to the goal!
Br,
Håkan Engman
11-06-20 03:04 PM
11-06-20 03:07 PM
11-06-20 08:34 PM