- Getting started
- Best practices
- Tenant
- Actions
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Action Catalogs
- Profile
- System Administrator
- Identity Server
- Authentication
- Other Configurations
- Integrations
- Classic Robots
- Troubleshooting
Deployment Tab
Enables you to configure and secure a feed that can host automation packages.
Enables you to set an internal or an external feed in which automation packages can be maintained. By default, an internal feed is used. The feeds can be secured either by defining basic authentication credentials or by using an API key.
Field |
Description |
---|---|
Internal |
Must be selected in order to use an internal feed. The feed can be secured either with the Secure Deployment option or by using an API key. |
External |
Must be selected in order to use an external feed. The feed can be secured either by using an API key or basic authentication credentials. |
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. |
Deployment URL |
The address where the NuGet feed is located. |
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. |
Enables you to configure the feed to be used when working with libraries. Libraries either published from Studio or manually uploaded by the user are stored within the chosen feed. There are two options available:
- Host - the Libraries page is the same for the entire Orchestrator instance, meaning libraries are not isolated at tenant level: each tenant has access to the other tenants' activity;
-
Tenant - libraries are isolated at the tenant level, meaning data is separated across tenants. This option behaves similarly to the packages feed, meaning you may set an internal or an external feed in which libraries are maintained. By default, an internal feed is used.
Field
Description
Only host feed
Libraries are stored within 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 tenant level: each tenant has access to the other tenants' activity.
You cannot upload libraries if this option is selected.
Both host and tenant feeds
Additional to the host feed, libraries will also be stored within the tenant feed and are isolated at tenant level, meaning data is separated across tenants. This feed behaves similarly to the packages feed and, as such, the same options are displayed when selecting the option. When retrieving libraries, they are searched both in the tenant and host feeds.
Internal
Must be selected in order to use an internal feed. The feed can be secured either with the Secure Deployment option or by using an API key.
External
Must be selected in order to use an external feed. The feed can be secured using an API key.
Secure Deployment
Ensures that your automation packages are downloaded through a secure NuGet feed.
Deployment URL
The address where the NuGet feed is located.
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
.
If you want to use an external feed while you have a proxy server configured on Windows, the following are required beforehand:
-
Set the Load User Profile option for the Orchestrator application pool (Internet Information Services > Application Pools) to
True
. -
Add the proxy settings you used to the
NuGet.config
file associated with the application pool identity account (C:\Users\[YourAppPoolIdentityAccountName]\AppData\Roaming\NuGet\NuGet.Config
):<config> <add key="http_proxy" value="http://ipaddress:port" /> </config>
<config> <add key="http_proxy" value="http://ipaddress:port" /> </config>Note: Note that the following 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.