管理员可以在“设置”页面调整 Orchestrator 租户设置。您可以使用租户级别的“设置”页面按租户进行更改，也可以使用 Orchestrator 主机门户中的“设置”页面同时对所有组织中的所有租户进行更改。
本页介绍租户级别的设置。此处进行的配置将覆盖在 Orchestrator 主机门户上进行的设置。
注意
独立 Orchestrator 安装与 Automation Suite 中的 Orchestrator 之间的某些设置不同。无论何时，我们都会在每个设置的说明下方记录这些差异。
常规选项卡
| Field | Description |
|---|---|
| Application Settings | Timezone - The time zone of the tenant. By default, this field is set to UTC. The time zone list depends on the machine. To ensure that all the instances under a multi-node Orchestrator installation have the same time zone list, they must use the same operating system version. Language - The language of the Orchestrator user interface for all tenants, including email notifications and alerts. This setting does not affect robot logs or event logs, which use the Windows language. Changing the organization language settings in Automation Suite. Custom logo - Upload your desired logo which appears in the Orchestrator window header. The accepted formats are .png and .svg, with a maximum file size of 1MB.Changing the company logo in Automation Suite. Custom header color - Select a color for the Orchestrator window header. This is useful for distinguishing between multiple Orchestrator tenants. The header color is selected by clicking the colored square to bring up your machine's color selector. In Automation Suite, you cannot customize the color of the header. |
| Personal Workspaces | Enable Personal Workspaces - Create personal workspaces for all users in a tenant that use a certain attended licensing profile, while also selecting the UI profile to be used for those users. Note: This action cannot be reversed, once the Personal Workspaces feature is enabled it cannot be disabled. |
| Standard Roles | Create standard roles for modern folders. These roles allow you to leverage the benefits of user groups. Click Create Role next to each of the roles you want create. |
| Client Binaries (Robot, Studio, Assistant) Auto-Update Settings | Ignore auto-update status for robot machines that were offline for more than ___ days - Allows you to exclude inactive machines from the update process and no longer take them into account when the update status is reported. |
| Modern Folders | Enable account-machine mappings - Enable the Account-Machine Mappings feature. |
| Classic Folders (deprecated) | Activate Classic Folders - Enable classic folders. Note: Classic folders are deprecated. Enabling them is only recommended if you migrate from an on-premises Orchestrator deployment to Orchestrator in Automation Cloud. |
| Email Setup | Enable alerts email - Enable Orchestrator to send email messages about Fatal and Error alerts. To receive email alerts, email settings must be properly set up. Configuring system email notification settings for all tenants in a standalone Orchestrator deployment. Configuring global email notification settings for all organizations (and the tenants in them) in Automation Suite. Overriding global email notification configuration for a certain organization (and the tenants in it) in Automation Suite. |
部署选项卡
Enables you to configure and secure feeds for packages and libraries. You can manage the feeds for all tenants from a centralized location using Automation Ops. For more information, see feeds management in the Automation Ops guide.
此处的设置仅影响租户订阅源；文件夹订阅源和个人工作区订阅源始终是内部的，并且仅在相应文件夹或个人工作区的上下文中可用。
包
使您能够设置内部或外部订阅源，用以维护自动化包。默认情况下，使用内部订阅源。可以通过定义基本身份验证凭据或使用 API 密钥来保护订阅源。
| Field | Description |
|---|---|
| Internal | Use an internal feed. The feed can be secured either with the Secure Deployment option or by using an API key: Secure Deployment - Ensures that your automation packages are downloaded through a secure NuGet feed. API Key - The key used to secure your feed against write operations such as delete or upload. |
| External | Use an external feed. The feed can be secured either by using an API key or basic authentication credentials: API Key - The key used to secure your feed against write operations such as delete or upload. Authentication - Enables you to specify the credentials for your basic authenticated feed. Please keep in mind that both the username and the password used with the API Key option should be used in this case as well. When External is selected, the Deployment URL field is displayed where you need to fill in the address where the NuGet feed is located. |
库
使您能够配置要用于库和活动包的订阅源。
| Field | Description |
|---|---|
| Only host feed | Libraries are stored in the host feed and are available to all tenants which use it. The Libraries page is the same for one Orchestrator instance, meaning libraries are not isolated at the tenant level: each tenant has access to the other tenants' activity. 🛈 You cannot upload libraries from Orchestrator if this option is selected. 🛈 This option gives robot access only to the host feed. |
| Only tenant feed | Libraries are isolated at the tenant level, meaning data is separated across tenants. You may set an internal or an external feed in which libraries are maintained. By default, an internal feed is used. 🛈 This option gives robot access only to the tenant feed. |
| Both host and tenant feeds | Libraries are isolated at the tenant level, meaning data is separated across tenants. You may set an internal or an external feed in which libraries are maintained. By default, an internal feed is used. 🛈 This option gives robot access to both the host and tenant feeds. |
| Internal | Must be selected in order to use an internal feed as the tenant feed. The feed can be secured either with the Secure Deployment option or by using an API key: Secure Deployment - Ensures that your automation packages are downloaded through a secure NuGet feed. API Key - The key used to secure your feed against write operations such as delete or upload. The user can use it to publish packages. This key is generated by the external provider and has the following format [username]:[password]. For example, admin:2652ACsQhy. |
| External | Must be selected in order to use an external feed as the tenant feed. The feed can be secured using an API key: API Key - The key used to secure your feed against write operations such as delete or upload. The user can use it to publish packages. This key is generated by the external provider and has the following format [username]:[password]. For example, admin:2652ACsQhy.When External is selected, the Deployment URL field is displayed where you need to fill in the address where the NuGet feed is located. |
通过代理使用外部订阅源的先决条件
如果要在 Windows 上已配置代理服务器的情况下使用外部订阅源，需要满足以下先决条件：
- Set the Load User Profile option for the Orchestrator application pool (Internet Information Services > Application Pools) to
True.
- 添加您在与应用程序池身份帐户 (
C:\Users\[YourAppPoolIdentityAccountName]\AppData\Roaming\NuGet\NuGet.Config) 关联的NuGet.config文件中使用的代理设置：
<config>
<add key="http_proxy" value="http://ipaddress:port" />
</config>
注意
Note that deployment settings are loaded only when the Robot Service connects to the server. Whenever they are modified you need to restart the UiRobotSvc service for the changes to take effect.
机器人安全选项卡
安全性
| Field | Description |
|---|---|
| Total hours a robot can run offline without license verification | Specify the number of hours a Robot can run offline, without Orchestrator checking its license. By default, it is set to 0. The maximum accepted value is 168 hours. This setting does not apply to Studio. |
机器人身份验证
| Field | Description |
|---|---|
Attended robot authentication | Interactive Sign-in SSO (Recommended) - This option only allows for robot connections with tokens that expire. Users can authenticate their robots only by signing-in with their credentials in the Assistant. Note: User sign in is required to run attended robots, make Orchestrator HTTP requests, or view processes in the Assistant. When using interactive sing-in, there is no need to create machine objects in Orchestrator. Hybrid - This option allows for both connections with tokens that don't expire (machine key) and connections with tokens that expire (interactive sign-in or client credentials). Users have the option to sign-in with their credentials to authenticate their robots, which in turn allows them to connect Studio and the Assistant to Orchestrator, however it is not mandatory. |
| Unattended robot authentication | Client credentials (Recommended) - This option only allows for connections with tokens that expire. It uses the OAuth 2.0 framework as the basis for the authentication protocol, meaning unattended robots can connect to Orchestrator with a client ID - client secret pair generated via machine template objects. The client ID - client secret pair generates a token that authorizes the connection between the robot and Orchestrator and provides the robot with access to Orchestrator resources. Hybrid - This option allows for both connections with tokens that don't expire (machine key) and connections with tokens that expire (client credentials). |
可扩展性选项卡
指定机器人服务是否应订阅 Orchestrator 的 SignalR 通道，并配置最适合您的传输协议。这些设置在升级后保留。
SignalR (机器人)
| Field | Description |
|---|---|
| Enabled | This toggle specifies if the Robot service subscribes to Orchestrator's SignalR channels or not. By default, this setting is enabled, and all available channels are selected: WebSocket Server-Sent Events (SSE) Long Polling When all transport channels are enabled, the best available transport is automatically selected, in the following priority order: WebSocket > Server-Sent Events > Long Polling. If the first protocol is not available for any reason, the next in line (if enabled) is used to facilitate the communication between Orchestrator and Robot. |
| WebSocket | When selected, enables the WebSocket transport protocol to be used to connect the Robot to Orchestrator's SignalR channels. This is the highest protocol used in the order of priority due to its performance and support for simultaneous communication in both directions - from the Robot service to Orchestrator and vice versa. If the SignalR (Robots) feature is not enabled, WebSocket becomes the only available transport protocol. |
| Server-Sent Events (SSE) | When selected, enables the Server-Sent Events (SSE) push technology to be used to connect the Robot to Orchestrator's SignalR channels. This is the first backup in case WebSockets is not available for any reason. This option cannot be used if the SignalR (Robots) feature is not enabled. |
| Long Polling | When selected, enables the long polling transport protocol to be used to connect the Robot to Orchestrator's SignalR channels. This protocol is used in case the WebSockets and SSE ones are not available. This option cannot be used if the SignalR (Robots) feature is not enabled. |
非工作日选项卡
定义每个租户的非工作日列表，用以限制触发器的运行。这意味着，您可以配置长期计划，使其不会在公共假日、周末或其他不进行正常业务活动的日子中触发。一旦定义的非工作日结束，触发器将照常启动。
为了将这些限制应用于触发器，您需要在配置触发器时选择非工作日日历。您在“非工作日”选项卡上所做的所有更改都会影响使用该日历的所有触发器。
备注：
如果触发器的时区与在租户级别设置的时区不同，则此触发器的“非工作日限制”将被禁用（“设置”>“常规”）。没有显式定义时区的租户将从主机继承时区。
For more details on how to manage non-working days, click here.
Updated 5 days ago