Installing or Upgrading

Applies to: Predict! Risk Controller 6 and Higher

 

Overview

This article walks through every screen of the Predict! Risk Controller 6 (PRC6) installation wizard.

The same process applies to fresh installations and upgrades from Predict! 4.5.4 or 5.2.

Notes:

1. Complete all steps in the Prerequisites article before starting.
2. Back up the database and the \prc4\ folder before proceeding with any upgrade.
3. Notify all users to save their work and log out before starting.
   1. Stopping the Predict! service will disconnect anyone currently logged in.

 

Before Starting the Installer

• Back up the database and the \prc4\ folder and all sub-folders.
• Advise all active users to save work and log out.
• Disable or restrict URL access to the server to prevent users from reconnecting during installation.

 

Running the Installer

 

1. Navigate to the installation media and run SetupPRC6.exe.
   1. If running Windows Server 2008 R2 and higher or Windows 7/8/10
      1. right-click and select Run as Administrator.
2. Click Next on the Welcome Screen
3. Read the End-User Licence Agreement and click I Agree.
   1. The installer will detect and stop any running Predict! services automatically.
4. Select the installation folder.
   1. For upgrades, the existing path is used.
   2. Avoid paths with spaces and keep the path under 260 characters.
5. Choose Components
   1. Select the components to install:
      1. Predict! Risk Controller is required.
      2. Apache 2.4 is recommended
      3. Password Encryption, OpenID Connect, and LDAP Authentication are optional.
6. Application Memory Settings
   1. For the WildFly Web server:
      1. Set Starting Memory and Maximum Memory
      2. On upgrades, existing values are retained.
7. Application Port Settings
   1. Confirm or change port numbers.
      1. Apache is recommended on port 80.
      2. Verify the Fully Qualified Domain Name (FQDN) shown is correct.
8. Password Vault Settings (optional)
   1. if Password Encryption was selected, configure the vault.
   2. Record the keystore password, alias, salt, and iterations in a safe location.
9. SSL Settings (optional)
   1. Set the HTTPS port (default 443) and certificate details.
   2. The installer generates
      1.  a self-signed certificate
      2. a Certificate Signing Request (.csr) for submission (if needed)
10. Mod Security Settings (optional)
    1. Enter the server's external IP address and gateway IP address if selected.
11. SSO Settings (optional)
    1. If OpenID Connect was selected, enter the following from the Azure App registration:
       1. the Tenant ID
       2. Client ID
       3. Client Secret
12. LDAP Authentication Settings (optional)
    1. If LDAP was selected, enter the following:
       1. LDAP URL
       2. bind credentials
       3. base context
       4. other Active Directory details.
13. Email Settings (optional)
    1. Enter SMTP server details for email reminders.
       1. These can be configured after installation if not available now.
14. Database Connection Settings
    1. Select the database type (SQL Server, Oracle, or MySQL)
    2. Enter the info below:
       1. hostname FQDN
       2. port
       3. database name
       4. credentials. 
    3. Choose the Prepare Database option:
       1. Empty Database (fresh install)
       2. Update Database (upgrade)
       3. No Preparation.
15. Database Connection Test
    1. Confirms the connection is successful.
       1. On Windows Server 2022 with SQL Server, an 'Unable to test' error may appear.
       2. Click Next to continue.
16. Summary of Options
    1. Review all chosen settings.
    2. Click Back to make changes or Install to proceed.
17. Installation
    1. Files are copied to the selected directory.
    2. This may take around 5 minutes.
18. Database Update
    1. The database schema is created or updated automatically.
19. VC15
    1. If Apache is selected, agree to the Microsoft Visual C++ licence terms and click Install.
20. Installation Complete
    1. Click Finish.
    2. If SSL was configured without a CA-signed certificate, submit the .csr file to a Certificate Authority.

 

After Installation

• Set up an automated overnight restart of the Predict! service for optimal performance.
• Apply a licence — see the Licensing article.
• Reapply any manual customisations from a previous installation (session timeout, LDAP config, NAT firewall settings, bind address changes).
• Run post-update database health checks using the Predict! Database Health Check Guide.
• Remove old JBoss or WildFly folders manually (e.g. WF201) once the upgrade is confirmed successful.

Note: If database credentials were entered incorrectly during installation, the setup must be completed manually. Contact Risk Decisions support: support@riskdecisions.com

 

Troubleshooting

• If the Predict! service does not start after installation
  1. Open an admin Command Prompt
  2. Run: sc start PRC62, then sc query PRC62 to confirm it is running.
• If Risk Reporter client installations exist
  • they must be updated separately.
  • Refer to the Predict! Risk Reporter Guide, Part 4.