tjunicho,
OK, after digging deep into the help files, this is what I have gathered.
Essentially, Resource Pools, are redundant to Active Queues, in the way they are SUPPOSED to schedule workload.
If you create a Resource Pool, you can schedule a process to run against that pool. Per documentation, BP should check the number of resources in the pool, and distribute the queue cases across available resources.
I have not been able to make this work. Instead of distributing the load, all queue cases are assigned to a random available resource from the pool, even if more than one resource is available.
On the other hand, Active Queues, provide you the same parallel distribution capabilities, and some more.. They offer statistical / timing measures (ETA's, etc.). To configure an active queue, forget Resource Pools exist. Under Management, create a new Resource Group and add the resources. Configure the queue and map it to the target process and Resource Group. Do not include the same resources in a Resource Pool, and do not add any Resource Pools into the Resource Group. This is because, the active queue controller, sees the pool as one resource.
I have managed to run a process in parallel across two resources in available state and grouped in a Resource Group. That is, about half of the queue cases were processed by one resource - and another half by another, in parallel. Oddly, I haven't been able to run such a process from Session Management. The associated process runs, when you increase the 'Target Resources' field in the Active Queue -> ""your active queue name"" screen.
Cheers,
Naz
