Configuring the Embedded Management Console

RoboServer contains an embedded web server which runs the Management Console. The web server is part of RoboServer, but is activated only when RoboServer is started with the -MC option enabled. By default, the web server will listen on port 50080, and thus the Management Console web interface is available on:


Protocols and Ports

The web server can be configured to be accessible through HTTP and HTTPS on separate ports. If a protocol is enabled, a port number for it must be chosen; the defaults are port 50080 (HTTP) and port 50443 (HTTPS).

In order to enable HTTPS a server certificate in JKS format must be stored in a file called tomcat.keystore in the Certificates/Web folder in the installation. If a certificate password other than the default one (‘changeit’) must be used, it can be entered in the Certificate Password field.

Enabling Administration Security

The Management Console can be accessed not only from the same computer (localhost), but also from others. One of the points of having a Management Console is that it coordinates execution of robots, and thus it typically must be accessible to many clients.

To mitigate the potential security risk of having access to the Management Console from other machines, you can enable an administrator password. Select the Use Admin Password option and enter the desired administrator user name and password. You must 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.

You can also restrict who is allowed to upload JDBC driver to the embedded Management Console (see more about uploading JDBC drivers here). Possible choices are 'Not Allowed' where no one can upload JDBC drivers, 'Admin from localhost' which means that the admin user can upload drivers if he is accessing the Management Console from the local machine, and finally, 'Admin from any host' which means that the admin user can always upload JDBC drivers.