12-09-25 11:14 AM
Hello,
Any help to understand the blueprism logic on the following case will be very appreciated. I'm lost.
Best regards
I use bp 7.4.0. i'm testing a process that gived satisfaction in BP6.8 version. On a sand box, i have a pool with 2 ressources.
The process (called Master Process) uses the Business Object Utility - AutomateC to run other processes when needed (called business process).
Here are the first master process's steps when it try to run a business process :
1) Run a process on the ressource pool name to get the logged in status. Save the answering ressource name.
2) Past the step 1, the master process uses only the ressource name saved at first step and no more the pool name.
- If not logged in, run a process to log the ressource with the login
- if logged in, run a logout and so on.
When a process is launched using a specific ressource name (not using the pool name but a ressource name part of a pool), the process is sometimes launched on another non busy ressource.
This behaviour was not seen previously in BP6.8 version.
Is it impossible to choose a specific ressource to launch a process (using automateC) if the ressource is part of a pool?
12-09-25 06:22 PM
I'm surprised to hear that you were able to run on a specific resource when it was part of a resource pool in 6.8. I have assumed for a long time that it isn't possible to do that. But I also haven't used resource pools in a long time because we're using CTWO (RPA Supervisor) which doesn't use resource pools so I may just be ignore about it.
Frankly to me it sounds like you shouldn't be using resource pools if you're using AutomateC. What is the point of that? If you're using AutomateC, then you can just determine which resource to run something on dynamically and then just not use resource pools at all.
15-09-25 08:47 AM - edited 15-09-25 08:47 AM
Thank you for your answer Dadid. I'm currently working on a upgrade from 6.8 and 7.4. I'm tied to use previously (supposed) working code but i havn't seen myself a 6.8 process run on a specific resource when it was part of a resource pool. In any case, it is definitely not possible in 7.4.
I will think of a way to determine dynamically the ressource to use.
Best regards
15-09-25 01:35 PM - edited 15-09-25 01:35 PM
Is there a reason you need to pick a specific resource? If you are using resource pools, I would assume you've already figured out handling getting the resource to be logged in before running something on it while using it inside of a resource pool. I would assume that this incorporates the use of schedules, and you can start a schedule using AutomateC.
16-09-25 09:58 AM
This is the heart of the problem.
I have this BP process, it logs in the ressource (calling a pool and making note of the ressource name) then run a process on the ressource (calling directly the ressource name this time).
So with this design, the second execution must run on the same previously logged in ressource.
I think to create another process who :
- Read a list of ressource names from a config file
- Check their availability using http://resourceName:port busy
- Logout the ressource if needed
- Manage a queue where my existing process will have to pick an item corresponding to an available ressource
This way, i abandon the pool system