License and subscription

Administrator A user who can use all functionality in both Nintex RPA Central and Nintex Bot. role required.

Before you start 
Install Nintex RPA Central, activate the license, and configure the Nintex RPA Central URL. For more information, go to Install Nintex RPA Central and activate license key.

A subscription to Nintex RPA LE allows your organization to efficiently and effectively automate repetitive, manual tasks with RPA software tools that are easy to use. The following license options are available:

  • Standard: Automate repetitive tasks and mundane work by leveraging the speed and ease of your own RPA bot. Pricing encompasses attended bots as well as support and training.
  • Enterprise: Experience the full capabilities of RPA with the control and governance you expect from an enterprise offering. Pricing includes both attended and unattended bots, access to workflows, cloud-to-ground connectivity, SAP interactions, and emulator actions.

For more information about license and pricing, go to Nintex RPA LE pricing.

On the License and subscription page you can:

View the license and subscription details

On the top navigation bar, click Settings. The License and subscription page displays the following details:

Section Field Description
License information License key Enter a license key or lists an existing license key.
  Edition

Type of license. Values can be:

  • Enterprise
  • Standard

For more information, go to Nintex RPA LE pricing.
  Botflow entitlement Number of botflows available for an existing license key.
  Expiry Expiry date for the currently assigned license key.
About Nintex RPA Central URL The Nintex RPA Central URL, which must be used to request access for a Nintex Bot. Click Copy URL to quickly and easily copy the URL. For more information about the URL, see Set your Nintex RPA Central URL and security certificate.
  Version Version of the Nintex RPA Central installation.
  SQL Server

SQL Server database. Values can be:

  • Microsoft SQL Express

  • Microsoft SQL Server

Edit the license key

You can edit the license key if you want to update the license details.

  1. On the top navigation bar, click Settings.

  2. Click License and subscription in the side navigation menu.
  3. In the License information section, to the right of the License key, click and select Edit.
  4. Edit the License key and click Update.

    The license key is updated.

Deactivate the license key

If you want to temporarily disable all botflows from running, you can deactivate the license.

  1. On the top navigation bar, click Settings.

  2. Click License and subscription in the side navigation menu.
  3. In the License information section, to the right of the License key, click and select Deactivate.
  4. Click Deactivate to confirm.

    The license is deactivated and the license activation page displays.

If you have any botflows running, they will be disabled and you must activate the license again to continue using Nintex RPA Central and Nintex Bot.

Edit the Nintex RPA Central URL

Hosting Nintex RPA Central on a server will allow you and other users on your domain to create botflows and assign them to one Nintex Bot (Standard edition) or an unlimited number of Nintex Bots (Enterprise edition). To host Nintex RPA Central, you will need to assign it to a URL.

Important: Nintex RPA Central can use a security certificate specifically generated for this server that is trusted by your domain. Check with your IT administrator to ensure selecting this solution is appropriate for your implementation in a production environment. If not, you can specify your own certificate provided by your IT administrator.

  1. On the top navigation bar, click Settings.

  2. Click License and subscription in the side navigation menu.
  3. In the About section, to the right of the Nintex RPA Central, click and select Edit.

    The Host Nintex RPA Central panel is displayed on the right.

  4. Select a security certificate from the Security certificate drop-down list. Your IT administrator must provide a security certificate that specifies the URL to use for Nintex RPA Central. The first entry in the Subject Alternative Names (SAN) of the certificate is automatically selected as the URL; contact Support if you need to select another SAN entry. The certificate must be on the local machine and meet the Nintex RPA Central certificate requirements described below:

    5. Note: If you need help verifying your certificate requirements, contact your IT department.

    On the machine where you want to install Nintex RPA Central, open the Control Panel > System and Security > Administrative Tools > Manage computer certificates window, and complete the following steps:

    1. Verify that the machine is configured appropriately to host an intranet site.
    2. Confirm that a user with local administrative rights has installed a valid web server certificate with:
      • A valid date range that is not expired.
      • A valid signing algorithm matching current cryptography standards.
      • An "Intended Purpose" including "Server Authentication."
      • Auto renewal (if available).
      • Issuance by the internal CA.
      • A private key.

      • A signature hash algorithm with a minimum size of 256 bits (SHA-256).

      • An installation location in the machine's Personal Certificates location at Certificates > Local Computer > Personal > Certificates.
      • A common name (Issued To) on the certificate matching the fully qualified domain name (FQDN) of the machine where Nintex RPA Central is installed.

      3. Example: MYCOMPANYRPAC.acme.com

      Note: If Nintex RPA Central is not on the same machine as your Nintex Bot, install the certificate in the Trusted Root section.

    3. Verify that a Subject Alternative Name (SAN) for the FQDN name of the machine exists.
      Note: 

      When binding the Nintex RPA Central URL, be sure to list the DNS Name value for the SAN in the certificate with MachineName.DomainName.com. The first DNS Name entry for the SAN will determine the Nintex RPA Central URL.

      For example, if the first entry for DNS Name=MyMachine1, then the Nintex RPA Central URL will be https://MyMachine1. If the first entry for DNS Name=MyMachine1.DomainName.com, then the Nintex RPA Central URL will be https://MyMachine1.DomainName.com.

  5. Type the Port number.
  6. Click Set URL.

    The Nintex RPA Central URL is configured and displayed.

Tip: If Nintex Bot is installed on a different computer and cannot connect to Nintex RPA Central after you have set your security certificate in Nintex RPA Central and set the URL in Nintex Bot, check to see if you can browse to Nintex RPA Central in Google Chrome or Microsoft Edge. The security certificate should download automatically and allow you to connect to Nintex RPA Central securely. The same mechanism is used in web browsers as in Nintex Bot.

Note: 

If you are using Windows 10, you must update the server firewall settings to allow access from any machine on the domain.

  1. Navigate to System and Security > Windows Defender Firewall > Advanced settings.
  2. Click Inbound Rules on the left pane.
  3. Click New Rule on the right pane.
  4. Click Port and then click Next.
  5. Select TCP and, based on the format of your Nintex RPA Central URL, type the following number in the Specific local ports field.

    6. Note: The port number can be different depending on your machine and network environment. Consult with your Network Administrator.

    • If your Nintex RPA Central URL ends in a number, such as 8080, type that number.
    • If your Nintex RPA Central URL does not end in a number, type 443.
  6. Click Next.
  7. Select Allow the connection and click Next.
  8. Select Domain.
  9. Ensure Private and Public are not selected.
  10. Click Next.
  11. Type a rule Name, and optionally, type a rule description.
  12. Click Finish.
  13. Click Outbound Rules on the left pane.
  14. Complete steps 4-13 again.

Edit the SQL Server connection

Note: You must be using Nintex RPA Central 2.6.0 or above to edit your SQL Server connection.

Follow these instructions if you need to update these licensed Microsoft SQL Server (not Microsoft SQL Express) connections:

  • Username and password to your RPACentralWeb and RPACentralKeys databases on the SQL Server (simple setup)

  • Connection strings to your RPACentralWeb and RPACentralKeys databases on the SQL Server (advanced setup)

You can also modify your SQL Server setup and switch from a simple setup (username and password) to an advanced setup (connection strings). You cannot, however, switch from an advanced setup to a simple setup.

If you want to migrate your Nintex RPA LE data from Microsoft SQL Express to Microsoft SQL Server, go to Migrate SQL Server database.

Note: All botflows that are running will be paused while you update the SQL Server connections.

  1. Back up your files that contain botflows and schedules and the botflows in your Nintex RPA Central database. For more information, go to License and subscription.

  2. On the top navigation bar, click Settings.

  3. Click License and subscription in the side navigation menu.
  4. In the About section, to the right of the SQL Server, click and select Edit.

    The SQL Server connection panel is displayed on the right.

  5. Select which method you want to use to edit your Microsoft SQL Server:
    • Simple (username and password)
    • Advanced (connection string). Select this option if you need to set up connection values that a default connection may not contain. The advanced option provides you with full control over the connection string.

  6. If you selected to edit your Microsoft SQL Server using the simple method (username and password), follow the instructions below:

    1. Type the SQL Server name, Username, and Password for the RPACentralWeb and RPACentralKeys databases.
    2. Click Test connection to test the connection to the databases with the username and password.
    3. Click Save when the connection is successful.
  7. If you selected to edit your Microsoft SQL Server using the advanced method (connection string), follow the instructions below:
    1. If you have not already done so, in Microsoft SQL Server Management Studio (SSMS), create a new SQL user that is not a Windows user (for example, RPACentralService) and ensure that the user has proper access permissions (create tables, create and access schemas, select, references, insert, update, alter, and delete). This new SQL user will be specified in the connection strings used to connect to your Microsoft SQL Server. You must create this new SQL user because the Nintex RPA Central service uses a local system account.
    2. If you have not already done so, in Microsoft SQL Server Management Studio, create an RPACentralWeb database and an RPACentralKeys database on the same SQL Server and ensure that they have proper access permissions. Nintex RPA LE will populate the RPACentralWeb database with botflows and users, while the RPACentralKeys database will remain relatively small with encryption keys and log files.

      Note: You cannot change the name of the RPACentralWeb and RPACentralKeys databases.

    3. Copy your RPACentralWeb database SQL connection string and RPACentralKeys database SQL connection string and paste them into Nintex RPA Central.
      Tip: 

      • The correct connection string format for the RPACentralWeb database is: Server=ServerName;Database=RPACentralWeb;User ID=userid;Password=password

      • The correct connection string format for the RPACentralKeys database is: Server=ServerName;Database=RPACentralKeys;User ID=userid;Password=password

    4. Click Test connection to test the connection to the databases with the strings.
    5. Click Save when the connection is successful.