Post-Installation Checks

Applies to: Predict! Risk Controller 6 and Higher

 

Overview

After installation and licensing, complete the following checks to confirm Predict! Risk Controller is functioning correctly.

Run these before making the system available to users.

 

Check 1 — Verify the service is running

• Open the Windows Services Manager.
• Confirm the Predict! Risk Controller service is installed and shows the status of Started.

 

Check 2 — Verify the database

• Ask the database administrator to confirm that the database now contains the expected tables.
  • it will have been empty prior to installation.

 

Check 3 — Log in to the application

1. Open the Windows Start menu and run the Risk Controller shortcut from the Predict! group.
   1. The default web browser will open and display the Predict! login screen.
2. Log in with the default credentials:
   1. Username: ADMIN, Password: sqlsql.
      1. usernames are not case-sensitive
      2. passwords are case-sensitive.
3. Confirm the Predict! home page loads successfully.
4. To verify the version, select the Help icon in the menu bar and click About.
   1. Confirm the version matches the installed release.

 

Check 4 — Test the client connection

1. On a client machine, open a web browser.
2.  Navigate to [host_server]:[port_number]/prc6/
3. Replace the placeholders with
   1. the server's FQDN or IP address
   2. the port number Predict! is running on.
      1. The port number can be omitted if Predict! is on port 80 or Apache is in use.

The Predict! login screen should appear.

 

Check 5 — Test Risk Analyser (if licensed)

1. Navigate to the profile icon in the top-right corner and select My Profile.
2. If a Risk Analyser licence is assigned (visible in the Licences section), a download button will be present.
3. Download and install Risk Analyser on the local machine.
4. Launch Risk Analyser.

After a brief splash screen, the application home screen should appear.

 

Check 6 — Test search

1. Create a test risk in Predict! Risk Controller.
2. Use the search box in the top menu to search for the risk by name.
3. Confirm the risk appears in the search results.

 

Troubleshooting

• If the service is not running:
  • open an admin Command Prompt
  • run: sc start PRC62, then sc query PRC62 to confirm it started.
• If the login screen does not appear:
  • a port conflict may exist.
  • Run netstat -a -b -n in Command Prompt to identify which application is using each port.
• If Predict! is not deployed:
  • navigate to \prc6\wf26\standalone\deployments and check for a file named prc4.ear.failed.
  • If present, rename the extension from .failed to .dodeploy and wait for WildFly to redeploy automatically.
• If the Risk Analyser download button is not visible:
  •  the account does not have a Risk Analyser licence assigned.
  • Contact the system administrator.