CA RiskMinder UNIX Installation Guide › Upgrading RiskMinder › Upgrading to Release 3.1 › Migrating the Database to Release 3.1 for RiskMinder Components › Reinstalling RiskMinder on a Single System

Reinstalling RiskMinder on a Single System

Perform the tasks described in the following sections to reinstall RiskMinder on a single system:

Important! Use the database that you had migrated earlier during the upgrade operation.

Important! The information in these sections applies to both a fresh installation of RiskMinder and an upgrade of an existing RiskMinder installation. Some of the steps that are mentioned in these sections do not apply in an upgrade scenario. For example, MySQL-related steps do not apply because MySQL is supported only from release 3.1 onward.

1. Install RiskMinder.

   Note: While installing RiskFort 3.1, ensure that you specify the same primary and backup database details from arcotcommon.ini in the $ARCOT_HOME/conf/ directory.

2. Verify the database setup.
3. Prepare the application server.
4. Deploy Administration Console.
5. Log in to Administration Console.

   Important! Ensure that you use the current MA password and not the default password, because the MA password has been reset during the bootstrap process that you performed during 2.x installation.

6. Start the RiskMinder Server.
7. Start the Case Management Queuing Server.
8. Verify the installation.

   Note: If there are any warnings during the Server startup and if your transactions fail, then the upgrade has not been performed successfully. You can revert to your initial setup by following the steps listed in (In Error Scenario Only) Reverting to Your Initial Setup.

9. Deploy User Data Service.
10. Deploy Sample Application.
11. Use the Sample Application to test the migration by verifying whether the user accounts and the related data from the earlier setup have been successfully migrated to the new database.
12. Apply the post-installation checklist.