Administrative Features in Orchestrator's Web Interface

The document summarizes administrative features in Orchestrator's web interface. It discusses users and roles, managing and deploying processes, alerts and notifications, audit logs, and general settings. Key points include creating custom roles, publishing processes from Studio, configuring email alerts, auditing user actions, and troubleshooting robot connections and job failures.

Uploaded by

Raghvendra Sharma

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PPTX, PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

39 views10 pages

Administrative Features in Orchestrator's Web Interface

Uploaded by

Raghvendra Sharma

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PPTX, PDF, TXT or read online on Scribd

You are on page 1/ 10

Infrastructure Training

Lesson 2 Recap
Administrative features in
Orchestrator's web interface

academy.uipath.com
Orchestrator user interface and components

Left hand menu offers access to daily tasks Upper right corner menu provides
(regular functionality) access to administrative functionalities
Users and Roles
Any number of roles can be Users can be local users or
created – example: Monitor AD users
Administrator role can’t be Permissions are cached –
deleted, but can be “not Redis cache is refreshed
used” on every change

A user can have one or

more roles

Default roles: Administrator

User import functionality is a
and Robot
one time only operation – no
synchronization with AD
Group is maintained
Managing and deploying processes

Publish from Studio directly to Go forward and backward between

Orchestrator versions

Disconnect Studio from

Orchestrator, publish locally and Reviewer’s role
upload package

Continuous integration – using

Delete unused versions Orchestrator API
Alerts and Notifications

Events that generate an alert

➢ Robot looses connection
➢ Get Transaction Item from a queue fails
➢ A schedule can not be fired
➢ A running job encounters an error
➢ A running process explicitly calls the “Raise Alert” activity (new in 2018.1)

Orchestrator can be configured to send emails for alerts

➢ Email is received by users with a valid email address and View permission on Alerts
Audit and Logs
Messages logged by the robots are centralized
by Orchestrator and can be redirected to one or
more targets. Default targets are the SQL
database and Elasticsearch

Audited actions: create, update, delete,

Filters can be applied
start/stop job, change password, import,
based on log level
upload, associate, change status

03
02 04
Actions performed by users NLog supports a set of standard

0
connected to Orchestrator’s web targets and there are extensions for
interface, or by API calls, are
audited 05 custom targets (Elasticsearch,
MongoDB, Kafka, Splunk)

1 l
Settings
General
➢ Timezone of the tenant; can be overridden by each schedule
➢ Connection String is used to automate deployment of robots

License
➢ License info and upload button

Deployment
➢ Deployment URL when a third party NuGet feed is used
➢ NuGet API Key

Mail
➢ Setting up email alerts

Security
➢ Password complexity, password expiration, account lockout options
Administration and configuration
Harden password complexity More about configuration in the lesson
(Security tab in Settings) “web.config explained”
Change admin password after
first login