Since I was just testing everything in my local machine, I was able to easily stitch all the pieces in integrating the Microsoft Bot and UIPath Robot. I could just deploy with a console application and call it done. However, I wanted to move outside a local instance and would want to deploy in a production environment. In an actual production setting, you would want a dedicated machine to run all your RPA jobs. In order for you to be able to achieve that is by using UIPath's orchestartor.
UIPath has a free community edition for orchestrator with some limitations. However, you can still test their enterprise features in the community edition.
You can get UIPath Orcestrator by going to this link.
Platform Versions Used
- UiPath 2019 Orchestrator Community 2019.2.0-CE.2
- UIPath Studio 2019.2.0
Once you have created an account . Head over to the dashboard and start creating a machine.
Click the + button and select standard machine. Give it a name and click provision
Go to robots page and click the + button then select standard robot.
Fill out the form
Now the important part is to actually include the
domain of the user account. For example, in Azure VM you just created an account called
ServiceAccount1. Be sure to include the machine name as your domain name when adding the service account. I spent hours figuring out why UIPath robot will not fire any jobs even if I double checked everything is configured correctly.
Next you want to create an environment. The UI navigation was not friendly enough for me to determine where the environments are.
Click the + button and create your environment. This is crucial if you want to create processes that will be associated with a given environment.
I provisioned an Azure VM and installed UIPath. From there, I just created a simple workflow and publish it to the orchestrator. Once you have published, go back to the orchestrator web app and click processes.
Same process, just click the + and fill out the forms. You should be able to see all the packages you've published in the dialog.
Once you click create, you can test by going to jobs and start a job with your selected process.
And there you have it. You should be able to see if you remote desktop to the Azure VM that UIRobot is initializing the workflow in its local instance.