Prerequisites and Pre-Installation Checklist

Applies to: Risk Controller 6 and higher

 

Overview

This article covers what must be in place before installing or upgrading Predict! Risk Controller (PRC) 6.

Completing these checks in advance will help avoid issues during the installation process.

Note: Administrator rights on the application server are required to install Predict! successfully.

 

Step 1 — Gather required information

The following details are needed during installation. Collect these before starting:

• Fully Qualified Domain Name (FQDN) of the application server
• Valid Predict! licence for the version being installed
• Database server hostname
• Database name (alphanumeric characters only)
• Database login username and password

 

Step 2 — Prepare the database

• Install and configure the database platform (SQL Server, Oracle, or MySQL) before beginning.
• Ensure the server date and time are set correctly
  • Predict! uses the server time.
• If using Microsoft SQL Server:
  • verify that the collation of the server instance and the database schema match before proceeding.
• If using database replication:
  • disable replication against the Predict! database before installation, as it can prevent schema changes.
• Close any open connections to the database (e.g. from database management tools) before starting.

 

Step 3 — Prepare an SSL certificate

An SSL certificate in X509 format with chain (.pem file) is required.

This can be:

• A certificate signed by a trusted Certificate Authority (e.g. Verisign, Thawte)
• A self-signed certificate generated during installation

 

Step 4 — Check firewall settings

• If a firewall is enabled on the server, temporarily disable it or open the required ports before installation.
• Default port is:
  • 8081 when upgrading from Predict! 5.2.1
  • 8080 for a fresh installation.

Resume the firewall once installation is complete and ports are confirmed open.

 

Step 5 — Gather optional component details (if applicable)

LDAP / Active Directory authentication:

• LDAP URL
• Bind credentials
• Base context and base filter
• Search scope

 

Email reminders (SMTP):

• SMTP server hostname
• Email login username, password, and sent-from address

 

Single Sign-On (SSO) via Azure Active Directory / Entra ID:

• Application (client) ID
• Directory (tenant) ID
• Client secret value and expiry date

 

Troubleshooting

• If the database collation does not match the server instance collation, installation will fail.
  • Check both collation values in SQL Server Management Studio before proceeding.
• If Risk Reporter users exist, their client installations must also be updated after the server upgrade.
  • Refer to the Predict! Risk Reporter Guide, Part 4.