We have several jobs which publish events to drivers, and these events
are taking a long time to be processed, impacting online events (like
password synchronization).
Our idea for solving this problem is having separate servers for
processing online and job requests, but without having different drivers
or policies for each one, but just including veto policies in the
beggining of the processing, for vetoing trigger operations in online
driver and non-trigger operations in jobs driver. For allowing that, we
must know in what server a driver is running, for figuring which events
should be processed.
Jobs driver should allow only trigger operations in subscriber and input
operations in publisher.
This includes the AD driver, using two drivers pointing to the same
remote loader. Is this configuration possible? if yes, how can I get the
actual server in a policy?
Thanks for any help.

jluizberg's Profile: https://forums.netiq.com/member.php?userid=2003
View this thread: https://forums.netiq.com/showthread.php?t=49640