Configuring the Configuration Manager

You must launch the Configuration Manager after adding a user account to your virtual machine. To launch, you can start the Configuration Manager immediately after installation the RPA application or navigate to the installation folder. The Configuration Manager establishes a connection of the RPA Agent with the RPA Mastermind.

Perform these steps after launching the Configuration Manager:

  1. Click Add to add a profile on the Manage Profile tab.
  2. Select the downloaded RPA Agent.ionapi credential file from the default Download folder of your device.

    See, Downloading the credential filesection for details.

    Note: You can add multiple profiles from different tenants. However, you can connect to only one profile at a given point. To switch tenants, you must sign out from the current tenant and sign on to a different tenant.
  3. Click Default corresponding to the tenant profile you want to use for connecting to Mastermind.
  4. Navigate to the Generate Keys tab and click Generate Keys. Private and public keys are generated.
  5. Copy the public key.
    Note: This step is required only if a device is created directly in RPA Management.
  6. Navigate to Device Settings tab.
  7. Specify the number of concurrent RDP sessions that RPA must use at any given time.
    Note: The number of concurrent RDP sessions specified must be less than the maximum RDP sessions allowed by the device.
  8. Select the Enable Auto Update check box to automatically update the RPA application on your device. This option is applicable only for the unattended installations.
  9. Specify the time interval in the Auto Update Interval field. The RPA unattended application checks for updates in the specified time interval.
  10. Click Create Device tab on the Configuration Manager window to create a new device.
  11. Specify this information:
    Display Name
    The name of the device.
    Domain
    The domain of the device.
    Scope
    The scope of the device. Possible values:
    • Public
    • Private
    Note: Value specified in the FQDN field is pre-defined and cannot be modified.
  12. Click Create Device. The device is created automatically in RPA Management within Infor OS.
    Note: Alternately, you can also create a device directly in RPA Management. See, Creating device in RPA Management for details.
  13. Click Mastermind Connection tab.
  14. Click Connect. The status is displayed as Connected, if the connection is successful.

    Alternately, you can also navigate to RPA Management > Manage > Devices page to check the device and the connection status.

  15. Navigate to Infor OS.
  16. Click RPA Management > Manage > Robots on the RPA Management application to create a robot.
  17. Click Add Bot.
  18. Specify this information:
    Domain or FQDN
    The domain name that was registered with the device where the robot must run.
    Name
    The name of the robot. This name is used as a display name.
    User
    The user account for which the robot must run the processes.
    Note: The user account specified must be same as mentioned when adding a user to your virtual machine. See, Adding a user account section for details.
    Password
    The password to access the new user account.
    Note: The password specified must be the same as mentioned when adding a user to your virtual machine. See, Adding a user account section for details.
    Devices

    The devices to which the robot must be added. Select the newly created device in the process.

    You can select multiple devices.

    Description
    The description for the robot.
  19. Click Add.
    Note: The application validates the specified information and displays an error message for any discrepancy. The windows user session in RPA Management refers to robots in which the automation runs.
  20. Navigate to the Configuration Manager application and select the Manage Users tab. The users from the RPA Management assigned to the device are displayed with sync status set to True.
    Note: Click the Sync Users option if users are not displayed or the sync status is set to False.

    You can now create jobs to run on the new device for the new robot.