Helpful Answers
Hi aanchal mathur - In simple terms -(Development Environment Scenario) When you are inside the Process Studio (Debug Mode) - there is a separate instance which is automatically created as an instance of the runtime resource, the moment you play or run the process inside the process - which is named as MachineName_Debug and when you are running that process from Control room by dragging the process to the available resource - Runtime Resource is responsible to run it.
See below :- Debug resource in highlighted which is responsible for running the process inside the studio.
In Development Environment: This setting is triggered by a user/developer who logs in to Blue prism software: System > Setting > Local Device Setting:
Now for Production or Digital worker : - To wake the Runtime Resource or Resource PC - There is a separate batch file which is kept in the windows start up folder as these production machines are unattended and are usually logged in by Login agent and it doesnt open the Blueprism software as a normal just as any developer would do in development environment by logging in which triggers the runtime resource as above explained, you can see your startup folder in your prod environment by simply - Pressing the Windows logo key + R, type shell:startup
Sometimes when its not connected - it can be triggered manually by logging into the prod vm by simply running the CMD command (usually done by support team):
The Digital worker or the Resource PC is connected to Blueprism Application Server - which is where the application server checks the status of the ResourcePC and enables the automation run if available or not busy.
To summarise - Resource PC is responsible for overall run - when its in debug or process studio - it has a separate Instance created as _Debug which runs the process and when its from Production Environment this is done via application server connecting to Runtime Resource or Resource PC.
Hope it helps.
------------------------------
Kindly up vote this as "Best Answer" if it adds value or resolves your query in anyway possible, happy to help.
Regards,
Mukesh Kumar - Senior Automation Developer
NHS, England, United Kingdom, GB
------------------------------
Hi aanchal mathur - In simple terms -(Development Environment Scenario) When you are inside the Process Studio (Debug Mode) - there is a separate instance which is automatically created as an instance of the runtime resource, the moment you play or run the process inside the process - which is named as MachineName_Debug and when you are running that process from Control room by dragging the process to the available resource - Runtime Resource is responsible to run it.
See below :- Debug resource in highlighted which is responsible for running the process inside the studio.
In Development Environment: This setting is triggered by a user/developer who logs in to Blue prism software: System > Setting > Local Device Setting:
Now for Production or Digital worker : - To wake the Runtime Resource or Resource PC - There is a separate batch file which is kept in the windows start up folder as these production machines are unattended and are usually logged in by Login agent and it doesnt open the Blueprism software as a normal just as any developer would do in development environment by logging in which triggers the runtime resource as above explained, you can see your startup folder in your prod environment by simply - Pressing the Windows logo key + R, type shell:startup
Sometimes when its not connected - it can be triggered manually by logging into the prod vm by simply running the CMD command (usually done by support team):
The Digital worker or the Resource PC is connected to Blueprism Application Server - which is where the application server checks the status of the ResourcePC and enables the automation run if available or not busy.
To summarise - Resource PC is responsible for overall run - when its in debug or process studio - it has a separate Instance created as _Debug which runs the process and when its from Production Environment this is done via application server connecting to Runtime Resource or Resource PC.
Hope it helps.
------------------------------
Kindly up vote this as "Best Answer" if it adds value or resolves your query in anyway possible, happy to help.
Regards,
Mukesh Kumar - Senior Automation Developer
NHS, England, United Kingdom, GB
------------------------------
