Creating the Orchestrator infrastructure

The steps needed for setting up the infrastructure are as follows:

1. Create a machine. You can choose from the following options:
   • Automation Cloud Robot - Serverless. This type of machine is hosted by UiPath® and allows you to run cross-platform automation projects. Find out more about Automation Cloud Robots - Serverless.
   • Automation Cloud Robot - VM. This type of machine is hosted by UiPath® and allows you to run automations on UiPath®-managed virtual machines. Find out more about Automation Cloud Robot - VM.
   • Machine template. You can connect unattended robots to a machine template to allow running executions without human involvement. Find out more about machine templates.
     Note: If you choose to create a machine template, you then need to connect its associated unattended robot to Orchestrator. Follow the link at step 4 to do that.
2. Create a robot account.

   A robot account is a non-user identity under which you can run unattended processes.

   Details:

   • Robot accounts defined
   • Creating robot accounts
3. Grant the robot account the Allow to be automation user role at the tenant level.
4. Add the previously created machine and robot account to the SAP Build folder, which is automatically created when you deploy a process from SAP Build.

   Once you've done that, grant the robot account the appropriate SAP-specific role at the folder level.

   To run processes in the various subfolders created under SAP Build, you need machines in each subfolder. To do that, you have two options:

   • Create and assign a separate machine for each subfolder.
   • Propagate the machine assigned to the SAP Build folder to all its subfolders. Find out how to propagate machines to subfolders.

   Details:

   • Creating the folder structure
   • Assigning objects to folders
   • Orchestrator folder structure for SAP organizations
5. Connect the robot to Orchestrator.
   In unattended automation, the host machine is connected and licensed in unattended mode, thus executing processes through Orchestrator. Find out how to connect an unatteded robot to Orchestrator.

   Note: This step only applies if you choose to use an unattended robot connected to a machine template.

The Orchestrator Unattended setup option walks you through these steps, ensuring that you have everything you need to get started. You can read more about it in Accessing the unattended robot setup.

Important: You cannot edit the name or change the version of any process included in the SAP Build folder. Doing so would lead to the automation breaking.

Orchestrator folder structure for SAP organizations

The Orchestrator folder structure for SAP organizations is dictated by actions performed on SAP Build Process Automation environments, as follows:

• When you deploy a project from your environment, the public SAP Build folder is automatically created in UiPath Orchestrator.
• When you create a shared environment under your environment, a subfolder with the same name as that of the shared environment is automatically created under the SAP Build folder in UiPath Orchestrator.
• When you deploy a project containing at least one UiPath task automation from a shared environment, a subfolder with the same name of that of the project is created under the shared environment subfolder.

Example

You deploy your first project from your SAP Build Process Automation environment, then you create the Invoices shared environment, and deploy the invoice_management project from it. The resulting folder structure in Orchestrator looks like this:

• SAP Build
  • Invoices
    • invoice_management

Addressing connectivity issues

Before running automations on any type of machine, you need to check whether the target system that the automation interacts with can be accessed from that machine. If the target system can only be accessed from a private network, you need to address connectivity issues by following these instructions:

Unattended robots

Deploy an unattended robot within the same private network as the target system. This ensures that the communication is direct and secure, without requiring additional network configuration.

Automation Cloud Robots - Serverless and Automation Cloud Robots - VM

1. Set up a VPN gateway.
   Important: The IP range can no longer be edited once the VPN gateway is configured.
2. Configure your cloud robots.