安装

Identity Server and Orchestrator are installed together on the same IIS server. Please read here how to proceed with Orchestrator installation.

默认情况下，安装程序对 Orchestrator 和身份服务器使用相同的数据库，但您可以在安装过程中指定不同的数据库。已安装的身份服务器地址为 https://OrchestratorURL/identity。

重要提示：

• 对于大型部署，我们建议为身份服务器使用单独的数据库。
• 仔细检查选定的安装路径。不支持将安装从一个位置移动到另一个安装后位置。

执行全新安装

执行 Orchestrator 安装的结果如下：

• Orchestrator's UiPath.Orchestrator.dll.config file is updated with Identity Server specific keys.
• Identity Server's appsettings.json file is updated with Orchestrator specific settings (encryption keys, caching, Redis settings, etc.).

执行更新

The results of performing an Orchestrator update are the following:

• 预先存在的 Orchestrator 数据（如用户、租户、主机或默认设置）将传播到身份服务器。

• Orchestrator's UiPath.Orchestrator.dll.config file is updated with Identity Server specific keys.

• Identity Server's appsettings.json file is updated with Orchestrator specific settings (encryption keys, caching, Redis settings, etc.).

  重要提示：

  During Orchestrator update, the installer cannot read an encrypted SecureAppSettings section . In order to read the EncryptionKey from Orchestrator's config file and then migrate it into Identity Server's appsettings.Production.json file, the key must be plain text. You need to manually decrypt the section before updating Orchestrator. After the Orchestrator update process was finalized, remember to re-encrypt the SecureAppSettings section in UiPath.Orchestrator.dll.config.

  如果在 UiPath.Orchestrator.dll.config 中启用了任何外部提供程序，系统会提示您需要在外部提供程序的位置执行的手动更改。

  For security reasons, for the certificate used to sign the access tokens generated by the Identity Server, make sure to use a public key on 2048 bits. The certificate's location has to be set within appsettings.Production.json's Signing Credential section.

  After updating your Orchestrator to v2020.4+, the Profile page won't display login attempts previous to that update, but all the details are still accessible from Orchestrator's database.