CA RiskMinder UNIX Installation Guide › Planning the Deployment › Deployment Overview › If You Are Performing a Fresh Installation

If You Are Performing a Fresh Installation

This section provides a quick overview of steps for deploying a fresh instance of RiskMinder and provides pointers for choosing a deployment model that is based on your requirements:

1. Choose a deployment model. RiskMinder can be installed on a single system or across multiple systems.

   See "Choosing a Deployment Model" for more information.

2. Ensure that the system where you plan to install RiskMinder and its components meets all hardware requirements.

   See "Hardware Requirements" for more information.

3. Install the prerequisite software products.

   See "Software Requirements" for more information.

4. Create a database user in the SQL database.

   See "Configuring Database Server" for more information.

5. Install RiskMinder:
   • See "Performing Complete Installation" for more information about installing in a single-system environment.
   • See "Installing on the First System" for more information about installing in a distributed environment.
6. Run SQL scripts in the database to create the RiskMinder schema and set initial configuration preferences:
   • See "Running Database Scripts" for more information about running SQL scripts for single-system deployments.
   • See "Running Database Scripts" for more information about running SQL scripts for distributed deployments.
7. Copy the required files and JARs on your application server. Administration Console and User Data Service (UDS) use these for proper functioning:
   • See "Preparing Your Application Server" for more information about deploying and starting UDS and Administration Console for single-system deployments.
   • See "Preparing Your Application Server" for more information about deploying and starting UDS and Administration Console for distributed deployments.
8. Deploy Administration Console:
   • See "Logging In to Administration Console" on deploying Administration Console for single-system deployments.
   • See "Logging In to Administration Console" on deploying Administration Console in a distributed environment.
9. Log in to Administration Console as a Master Administrator to initialize it:
   • See "Bootstrapping the System" for more information about initializing Administration Console for single-system deployments.
   • See "Bootstrapping the System" for more information about initializing Administration Console in a distributed environment.
10. Start RiskMinder Server and Case Management Queuing Server, and verify that the services are coming up correctly:
    • See "Starting RiskMinder Server", "Starting the Case Management Queuing Server", and "Verifying the Installation" for more information about initializing Administration Console for single-system deployments.
    • See "Starting RiskMinder Server", "Starting the Case Management Queuing Server", and "Verifying the Installation" for more information about initializing Administration Console in a distributed environment.
11. Deploy User Data Service (UDS):
    • See "Deploying User Data Service (UDS)" for more information about deploying and starting UDS for single-system deployments.
    • See "Deploying User Data Service (UDS)" for more information about deploying and starting UDS for single-system deployments.
12. (For Distributed Installation Only) Install RiskMinder on the subsequent systems.

    See "Installing on the Second System" for more information.

13. Deploy and run Sample Application to test RiskMinder installation:
    • See "Deploying Sample Application" and "Using Sample Application" for more information about performing this task in a single-system environment.
    • See "Deploying Sample Application", "Configuring Sample Application for Communication with RiskMinder Server", and "Using Sample Application" for more information about performing this task in a distributed environment.
14. (Optional) Change the HSM settings that you specified during installation:

    See appendix, "Changing Hardware Security Module Information After the Installation" for more information.