Hyland RPA Conductor Setup - Conductor - Foundation 23.2 - Foundation 23.2 - Ready - Hyland RPA - external

Hyland RPA Conductor

Hyland RPA
Foundation 23.2

Run, utilize, scale - Hyland RPA Conductor guides your musicians, the software robots, with efficient precision. Learn how you can set up the Hyland RPA Conductor in this article.

Note: The Hyland RPA Conductor requires Microsoft Visual C++ 2010 Redistributable Package (x86) to operate. Please download and install it from Microsoft before you start the RPA Conductor.

To initialize the RPA Conductor for its first startup you need to perform a couple of customizing steps inside the AM.Net.Core.Conductor.exe.config.

  1. Set-up a connection to your environment

    Open the AM.Net.Core.Conductor.exe.config using your Notepad. The config should be located inside the RPA Conductor base directory (for example, C:\AM\Conductor) . Search for the connection string <connectionStrings> entry. The entry to search for will look like this:

     <add name="AM.ConnectionString"
     connectionString="Data Source=myServerAddress;Initial Catalog=myDataBase;Persist Security Info=True;User Id=myUsername; Password=myPassword;" providerName="System.Data.SqlClient" />

    Maintain the required SQL credentials to your environment. If you require a different connection string variants you can view the linked website for further information.

    If you maintain your connection with windows authentication, your connection string looks like this:

  2. Maintain your license key

    Stay inside the AM.Net.Core.Conductor.exe.config and search for the licenseKey. The entry to search for will look like this:

     <add key="licenseKey" value="XXXXX-XXXXX-XXXXX-XXXXX"/>

    Maintain the provided license key and save the config file. The RPA Conductor will validate your license during startup. If you want to know more about how you can manage license activations for the Hyland RPA Conductor, see Licenses in the Hyland RPA Manager documentation.

  3. Manage your identification expression

    The Hyland RPA Conductor needs to be able to identify its current client in the database, so it is able to pull the right tasks (depending on the configured productions). To do so, it checks all existing clients in the database to find the first one with matching identification. If no client is matching, the Hyland RPA Conductor will automatically create a new one together with an asynchronous encryption key pair, so it is possible for the user to manage the credentials needed by this Client with the Hyland RPA Manager.

    By default the clients are identified by their computer name. If you want to modify this behavior, please adjust the clientIdentificationExpression within the AM.Net.Core.Conductor.exe.config file before you start the Hyland RPA Conductor for the first time on the client:

     <add key="clientIdentificationExpression" value="%COMPUTERNAME%"/>

    You can basically choose from any predefined or custom environment variable or a combination of them. So following configuration is also valid:

     <add key="clientIdentificationExpression" 

    This one will identify the client by the computer name and die username of the currently logged in user.

  4. Start the Hyland RPA Conductor.exe

    The RPA Conductor is a tray application you can find it on the right side of your windows start menu, by default the RPA Conductor remains hidden, due to the fact that its a quite technical application.

    To display the application right-click on the application inside your tray and press show. The RPA Conductor will show up and will go back to 'hide' after a couple of seconds. To make it stick you can disable the auto hide using the tray menu.

    The RPA Conductor console will open up afterwards.

    To gain access to the log you can use the show log function in the context menu.

Could not start RPA Conductor, please check your connection string?

Looks like you're using an invalid connection string or the RPA Conductor could not connect to your database. Please open the AM.Net.Core.Conductor.exe.config and change your connection string.

 <add name="Am.Net.Core.Data.Properties.Settings.AmConnectionString"
 connectionString="Server=myServerAddress;Database=myDataBase;User Id=myUsername; Password=myPassword;" providerName="System.Data.SqlClient" />

There is no license key configured

Your license key is missing in the AM.Net.Core.Conductor.exe.config. Please add your license key as displayed in the example below:

 <add key="licenseKey" value="XXXXX-XXXXX-XXXXX-XXXXX"/>