Use local machine as a runtime resource
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
12-04-21 10:09 AM
Hi,
I've installed blue prism on two machines - one app server on machine A and one interactive client on machine B - using the free trial license. In control room on the interactive client, only machine A is visible under Resources (offline, which is to be expected), but I'd like machine B to be showing as well so I can run a process locally from control room. I've checked the "Start a personal Runtime Resource on this machine when users sign in to Blue Prism" on the client.
Why can't I see machine B under resources?
Br
Sophie
I've installed blue prism on two machines - one app server on machine A and one interactive client on machine B - using the free trial license. In control room on the interactive client, only machine A is visible under Resources (offline, which is to be expected), but I'd like machine B to be showing as well so I can run a process locally from control room. I've checked the "Start a personal Runtime Resource on this machine when users sign in to Blue Prism" on the client.
Why can't I see machine B under resources?
Br
Sophie
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
12-04-21 12:39 PM
hello Sophie,
Yes it seems to be correct, any remote machine's personal runtime is not visible through the control room as its a private runtime connection. machine A's is showing up as for the App server its a local runtime.
try the below steps -
1. make sure machine B connection points to Machine A (app server).
2. the user logged in machine B needs to have corresponding access to start and run runtime resource.
3. Open command prompt and run the below command in machine B.
"C:\Program Files\Blue Prism Limited\Blue Prism Automate\Automate.exe" /resourcepc /public /user <bpusername> <BpPassword> /port 8183
or if using sso
"C:\Program Files\Blue Prism Limited\Blue Prism Automate\Automate.exe" /resourcepc /public /sso /port 8183
this should create a runtime resource window in machine B & start an RR
Yes it seems to be correct, any remote machine's personal runtime is not visible through the control room as its a private runtime connection. machine A's is showing up as for the App server its a local runtime.
try the below steps -
1. make sure machine B connection points to Machine A (app server).
2. the user logged in machine B needs to have corresponding access to start and run runtime resource.
3. Open command prompt and run the below command in machine B.
"C:\Program Files\Blue Prism Limited\Blue Prism Automate\Automate.exe" /resourcepc /public /user <bpusername> <BpPassword> /port 8183
or if using sso
"C:\Program Files\Blue Prism Limited\Blue Prism Automate\Automate.exe" /resourcepc /public /sso /port 8183
this should create a runtime resource window in machine B & start an RR
