- Release Notes
- Requirements
- Installation
- Getting Started
- Projects
- Datasets
- ML Packages
- Pipelines
- ML Skills
- ML Logs
- Document Understanding in AI Fabric
- Basic Troubleshooting Guide
AI Center
3. Configure Orchestrator
Orchestrator configuration entails adding some fields in the Orchestrator UiPath.Orchestrator.dll.config (or Web.config for Orchestrator 20.4). Before you begin, backup your existing UiPath.Orchestrator.dll.config file (for example making a copy in a different path).
Below we provide two options to update this configuration:
- Automated Configuration . A PowerShell script.
- Manual Configuration - A step-by-step guideline
with explanations, this should be used in very unique cases (such as governance rules not
allowing for automated changes to Orchestrator Config). Manual configuration is error prone
and can lead to downstream installation issues.
Note: Please note that if you update DNS or certificates for Orchestrator or Identity Server, AI Fabric would stop working. You would need to reconfigure the Orchestrator certificates, then redeploy AI Fabric to fix it.
- Open PowerShell in Administrator mode. * Download the file
[here](https://raw.githubusercontent.com/UiPath/ai-customer-scripts/master/orchestrator/orchestratorAutomationAIF20-10.ps1).
This can be done with the following
command:
wget https://raw.githubusercontent.com/UiPath/ai-customer-scripts/master/orchestrator/orchestratorAutomationAIF20-10.ps1 -outfile "orchestratorAutomationAIF20-10.ps1"
wget https://raw.githubusercontent.com/UiPath/ai-customer-scripts/master/orchestrator/orchestratorAutomationAIF20-10.ps1 -outfile "orchestratorAutomationAIF20-10.ps1" - You can familiarize yourself with the script options by
running:
get-help .\)\)orchestratorAutomationAIF20-10.ps1 -full
get-help .\)\)orchestratorAutomationAIF20-10.ps1 -full
For most of the Orchestrator installations, the default values for the non-mandatory options will work. In these cases run:
.\)\)orchestratorAutomationAIF20-10.ps1 -aifip "<aif-linux-machine-domain-name-or-ip>" -orcname "<Orchestrator-Domain-Name Lower>"
.\)\)orchestratorAutomationAIF20-10.ps1 -aifip "<aif-linux-machine-domain-name-or-ip>" -orcname "<Orchestrator-Domain-Name Lower>"
<AIF Machine Domain Name or IP>
with the ip of
the linux machine where AI Fabric will be installed (or the fully qualified domain name
if AI Fabric will be installed with a certificate) and <Orchestrator Domain
Name Lower Case>
with the domain name of Orchestrator. The letter case
must exactly match the Orchestrator certificate used to install Orchestrator.
aifport "31390"
)
If you have a non-standard path to Orchestrator UiPath.Orchestrator.dll.config (Web.config), you can specify the path to the file explicitly:
.\)\)orchestratorAutomationAIF20-10.ps1 -aifip "<aif-linux-machine-domain-name-or-ip>" -orcname "<Orchestrator-Domain-Name Lower>" -config "<Path to UiPath.Orchestrator.dll.config file>"
.\)\)orchestratorAutomationAIF20-10.ps1 -aifip "<aif-linux-machine-domain-name-or-ip>" -orcname "<Orchestrator-Domain-Name Lower>" -config "<Path to UiPath.Orchestrator.dll.config file>"
After applying the script below, your config file will be modified. Applying a file diff on your previous config file and the modified config file looks like this:
Compare the certificate (which was used to install Orchestrator) thumbprint values, to the values in the modified config file. These values should be the same:
IDP.SigningCertificate
field in the modified config file. These
should be the same: