Question
RBC
CA
Last activity: 13 Mar 2018 14:32 EDT
When/How does the OPENSPAN_APPLICATION_PATH environment variable get set?
I'm developing a powsershell script to start an OpenSpan RPA script on a machine. OpenSpan's runtime was installed on the machine by a system administrator.
I was expecting that I could use the environment variable OPENSPAN_APPLICATION_PATH to find where the openspan.runtime.exe was installed, but I did not find this. Is this because it did get set during the install or was it an error on the adminstrator's setup?
In either case, can I depend on OPENSPAN_APPLICATION_PATH variable being around or should I use another method for finding the .exe.
Any valued input is appreciated.
Accepted Solution
RBC
CA
Yes I had assumed the runtime would be in the same place, but no, that's not the case.. for dev machines it seems under openspan\devstuio...., using VS plugin it could be openspan\plugin... or our sysadmins installed as openspan\runtime enterprise...
There may also be a support case to have multiple runtimes against numerous RPA builds (ex: 1076, 1081, etc..) The environment var would have been helpful. Need to go back to the installers..
Thanks for the RPA schedule item. Will investigate how it could be implemented in our environments...
Pegasystems Inc.
US
The system environment variable, OPENSPAN_APPLICATION_PATH, is set on install. I really couldn't say what happened during your install but in most cases anyway, the application is installed in the same directory location.
I noticed you said you're doing an RPA project and a powershell script works but you should also consider the Scheduler functionality that was released with later builds. I wonder, for your case, if that would meet your needs better.
https://docs-previous.pega.com/pega-rpa/robotic-processing-automation-rpa-service
Accepted Solution
RBC
CA
Yes I had assumed the runtime would be in the same place, but no, that's not the case.. for dev machines it seems under openspan\devstuio...., using VS plugin it could be openspan\plugin... or our sysadmins installed as openspan\runtime enterprise...
There may also be a support case to have multiple runtimes against numerous RPA builds (ex: 1076, 1081, etc..) The environment var would have been helpful. Need to go back to the installers..
Thanks for the RPA schedule item. Will investigate how it could be implemented in our environments...