I am almost to the point where i want to deploy a solution i have built within Studio. Within studio i have generated a .OpenSpan and .Manifest file. The next step i am looking to do is to deploy my created solution to a number of client side machines.
I have several questions with my next step:
1. What is the best pega software to deploy my solution? Based on the knowledge base I am finding that the "Pega Robotic Runtime" is the best way to do this. I have also found the Pega platform as a potential solution. Which is best?
2. Depending on the solution used will the client side machine have editing options? i want to prevent the client from editing the solution.
1. Pega Robotics Run time is the best way to do the deployment.Here deployment of project should be done on each system if there are multiple systems where this run time is running else if it is running in any server then directly we can deploy in the server.
2. At a time only one solution should be in running mode which is equal to a BOT. User can have option for editing few of the setting related to run time. Eg : User can change the Logging setting from the context menu of the Robot icon. User cannot modify the solution or projects within it until there is some Pega robotics studio. The items that are displayed on the Robot icon of Run time can be controlled by editing RuntimeConfig.xml file.
Runtime loads and runs compiled solution (deployment) on user machine. First of all you must install Runtime there.
Additionally, you need to distribute deployment files somehow If you have very few users then it can be done by placing .openspan and .manifest files on accessible network share. Alternatively, you can leverage Robot Manager + Package Server capabilities to manage deployment packages.
Users can't modify solution files under Runtime. There are Runtime system settings in RuntimeConfig.xml that can be modified, these are generic options not tied to your solution code.
We are looking to run ~5 bots. Each bot will have its own machine as such i believe Runtime is a better way to run the RPA. Based on this 5 bot figure as well as not many patches/updates being deployed as the deployment should be a one off deliverable, do you agree Runtime is the correct course of action?
To understand clearly, Robotic Runtime is not the best solution. Robotic runtime (.exe) is software to run BOTs (.openspan) in users machine. So without this you can't run any BOTs.
1. If you don't have interaction with pega application then use normal approach like copy the .openspan, .manifest to user machine (1-3 users not exactly), if more users then copy those files in network shared path. Robot Manager (part of pega) will be used if any pega application interaction in the automation.
2. User can't edit solution at any cost but he can change log settings and this possible if user known it.
Can you explain your response "To understand clearly, Robotic Runtime is not the best solution. Robotic runtime (.exe) is software to run BOTs (.openspan) in users machine. So without this you can't run any BOTs." Why is Robotic Runtime NOTthe best solution to deploy? I want to run .openspan files that i have already developed on ~5 user machines. These machines are located on a client site (different than my own machine which is where the .openspan file was developed within studio)