CA RiskMinder Windows Installation Guide › Upgrading RiskMinder › Database Privileges Required for Upgrade › Reinstalling RiskMinder › Reinstalling RiskMinder on a Distributed System

Reinstalling RiskMinder on a Distributed System

Perform the tasks that are described in the following sections to reinstall RiskMinder on a distributed system:

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.

Important! Use the database that you had migrated earlier during the upgrade operation. In addition, install RiskMinder at the same location where the older release was installed. If you install in a different location, the RiskMinder Server will not start.

1. Installing on the First System

   Note: When you install release 3.1, ensure that you specify the same primary and backup database details from arcotcommon.ini in the %ARCOT_HOME%\conf\ directory.

2. Verifying the Database Setup
3. Preparing Your Application Server
4. Deploying Administration Console
5. Logging 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. Starting RiskMinder Server
7. Starting the Case Management Queuing Server
8. Verifying 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 that are listed in the "(In Error Scenario Only) Reverting to Your Initial Setup" section in the CA RiskMinder Installation and Deployment Guide for UNIX Platforms.

9. Deploying User Data Service
10. Installing on the Second System
11. Deploying Sample Application
12. Configuring Sample Application for Communication with RiskMinder Server (scenario).
13. Using Sample Application (scenario) (distributed) to test the upgrade by verifying whether the user accounts and the related data from the earlier setup have been successfully migrated to the new database.
14. Post-Installation Checklist.