Introduction

Management Console is an application with a web-based user interface, which makes it easy to access from any computer on the network. The address to connect to a Management Console consists of a computer name and a port, such as http://computername:port.

Management Console can be deployed two ways.

Embedded mode: A way to quickly start Management Console after installation for demonstration and testing purposes. See Configure embedded Management Console below for information on the embedded mode.
Standalone mode: A standalone version of Management Console deployed on Tomcat in a production environment. For this mode, Kofax RPA also provides tools for Docker deployment. For information about a standalone Management Console, see "Tomcat Management Console" in the Kofax RPA Administrator's Guide.

All RoboServers must auto register to Management Console. The URL and shared secret for the Management Console with the cluster name must be specified when starting the RoboServer (either at the command line or on the General tab of the RoboServer Settings application). See Start RoboServer for more information.

Some features such as high availability may not be available, depending on your license key.

Configure embedded Management Console

In embedded mode, Management Console and RoboServer start simultaneously and by default, the web server interacts with port 50080. The web interface port and other parameters are configured on the Management Console tab in the RoboServer Settings application.

Protocols and ports

You can configure the web server to be accessible through HTTP and HTTPS on separate ports. If a protocol is enabled, a port number must be chosen; the default ports are 50080 (HTTP) and 50443 (HTTPS).

To enable HTTPS, a server certificate in JKS format must be stored in a file called webserver.keystore.

You can also restrict who is allowed to upload JDBC driver to the embedded Management Console. Possible choices are "Not Allowed", where no one can upload JDBC drivers, "Admin from localhost," which means that the administrator can upload drivers when accessing the Management Console from the local machine; and finally, "Admin from any host," which means the administrator can always upload JDBC drivers.

User management

One of the points of having a Management Console is to coordinate execution of robots, and thus it is typically accessed by many clients. To mitigate the potential security risk of having an unauthorized access to a Management Console from other machines, user management is enabled by default in embedded mode and the default admin superuser password is available (user name - admin, password - admin). See Users & groups for more information.

When you log in to a Management Console for the first time, use the default admin user password. Once you are logged in, you can change the password and create other users and groups on the "Users & groups" page under Admin in the Management Console. Use these credentials both when you publish a robot to the Management Console from Design Studio and when you access the web interface from a browser. To change the admin user password, do the following:

Expand the Admin item on the left pane and click Users & groups.
On the Users tab, select the admin user and click .
Type the new password, type it again to confirm, and click OK.

See Users & groups for more information.