Installing the Process Discovery Server
Process Discovery is composed of:
-
Process Discovery Server
-
Database Server
-
Seq Server
-
Discovery Robots
The following sections describe the steps to install the Process Discovery Server and databases on a single server. To perform a silent installation, see Silent Installation of Process Discovery Server.
This installation scenario prepares your system for using Nintex Process Discovery. Use the following steps to guide your installation of the Process Discovery Server. Once your servers are installed and configured, you can install the Discovery Robots and then set up your recordings, process the data, and analyze the output.

Ensure that the server meets the requirements. See System Requirements for Process Discovery Server.

-
The following default external ports are opened automatically in the Windows Firewall during the Process Discovery Server installation process.
-
(Optional) You can override the default port setting if you want. At this time, make sure the ports you choose to use are open in the hardware firewall. Be sure to write down the port numbers you use; later you will need to configure them in the installation settings.
-
(Optional) The following default back-end ports are used in the Process Discovery Server. We recommend NOT to open them in the firewall. They are customizable, if required:
These ports are intended for an installation that does not use SSL/TLS (see below for SSL/TLS ports). Open them in your hardware firewall prior to installing the server:
Default Port (Not using TLS) |
Port Used by |
Port Used for |
---|---|---|
80 |
NGINX |
Communication between the Discovery Robots and Console users with the Process Discovery Server |
3306 |
MariaDB / MySQL |
Database Management System |
5341 |
SEQ |
*Can be installed remotely |
27017 |
MongoDB |
Mongo Database |
If you will be using SSL/TLS , open the following ports in your hardware firewall prior to installing the server.
Default Port |
Port Used by |
Port Used for |
---|---|---|
443 |
NGINX |
Communication between the Discovery Robots and Console users with the Process Discovery Server |
Default Port |
Port Used for |
---|---|
5058 |
Communication between the Process Discovery Server and the User Management Tool |
50100-50130 |
Communication between the Process Discovery Server and the Console |
51000-51030 |
Communication between the Process Discovery Server and the Console |

Before proceeding with the installation, you must have a preexisting dedicated Windows version database server installed and ready. The supported database management systems are:
The database requires the same processor and RAM as the Process Discovery Server, with a minimum of 1TB of available hard disk space.
Databases are installed to collect, analyze, and work with the data received from the robots. Nintex Process Discovery uses four application databases.
Database |
Database engine |
Created users |
---|---|---|
Process Discovery application database #1 (data segregated by Team) |
MariaDB 10.3.7 (or higher) or MySQL 8.0.11 (or higher) |
The Process Discovery server installation package automatically installs MariaDB, which creates a database called Nintex-db, along with the following default users:
|
Process Discovery application database #2 (data aggregated for all Teams) |
||
Process Library database |
||
User Management platform database |
||
Raw data collections: Images + metadata recorded by Discovery Robots (segregated by team) Collection prefix: |
MongoDB 4.4.3 (or higher)
|
The Process Discovery server installation package automatically installs MongoDB, which creates a database called Nintex-db,along with the following default users:
|
Masked Images: Only if masking is enables (segregated by team) Collection prefix: |

The Process Discovery Server installation package automatically installs the RabbitMQ Server. You can opt to connect to a preexisting RabbitMQ instance later in the installation procedure. See Customize queue manager.
If you want to connect to a preexisting RabbitMQ instance, you may need to add permissions to the admin RabbitMQ user at this time. To do so, follow these steps: Rabbit MQ user management.

-
Download the Process Discovery Server installation file,
nintex-pd-23.5.0.395-full
, to a local folder on the server. -
If you have received your Process Discovery license key file from your contact at Nintex or the Nintex distribution partner, download it and save the license key file to
C:\Nintex\PDServer
.During the installation process, you will be prompted to provide the license key. Therefore, it is important to choose a folder location that is easily accessible and memorable for future reference.
If you don't have a license key now, you can install it after the Process Discovery Server installation is complete. See Set up the License After Installation.

Install the Process Discovery Server with the System Manager.

If you need to make changes like enabling TLS or configuring masking, you can do it by using the command-line instructions (CLI). There is no need to uninstall the previous version. Simply rerun the System Manager installation and adjust the config.json
and secrets.zip
files as required. You can use the original template and make changes there.

Follow these steps to activate your Process Discovery license (if you did not do so previously during installation):
-
Copy the license key file to the Install folder location that you created during the Process Discovery Server installation.
By default, the format of the installation folder location is
C:\Nintex\PDServer
. -
From the Windows Services app or the Windows Task Manager > Services tab:
-
Restart the Kryon Server - Process Discovery Service.
-
Check the Status column of the Kryon Server - Process Discovery Service to ensure that it shows
Running
.
-
If you have not yet received your license key file, check with your contact at Nintex or the Nintex distribution partner with whom your organization is working.

Verify the Process Discovery Server installation by checking that you can connect to the following components:
In the URL, use HTTP:// if you installed without TLS and HTTPS:// if you installed with SSL/TLS.
-
Connect to the RabbitMQ Management Plugin:
From a web browser on the Process Discovery Server, enter the following URL:
HTTP://{FQDN of Server}:15672
Log in with the following username and password:
Username: admin
Default temporary password: Nintex2023!
-
Connect to Process Discovery Components:
From a web browser on the Process Discovery Server, connect to the Process Discovery components:
-
PD Console:
HTTPS://${FQDN}/console
Log in with the following username and password:
Username: Pdconsole
Default temporary password: Pd123456! (If you changed the password, use the newly created password)
-
Seq logging server:
HTTPS://${FQDN}/seq
-
Aerobase management:
HTTPS://${FQDN}/authadmin
Log in with the following username and password:
Username: authadmin
Default temporary password: Nintex123! (You may be asked to change the password. If you do, be sure to write it down)
-
If you connected successfully to the above components, installation of the server is complete.
Once the Process Discovery Server installation is successful, you can install the Discovery Robots.