Installing on the First System

CA RiskMinder Windows Installation Guide › Deploying RiskMinder on a Distributed System › Installing on the First System

Installing on the First System

To install (and later configure) RiskMinder on Microsoft Windows successfully, the user account that you plan to use for the installation must belong to the Administrators group. Else, some critical steps in the installation, such as DSN creation and configuration, and RiskMinder service creation, are not completed successfully, though the installation may complete without any errors.

In a distributed scenario, irrespective of how many systems you are distributing RiskMinder, Administration Console, Java SDKs, and web services across, you typically install RiskMinder Server on the first system. Custom installation allows you to install only the selected components from the package. This option is recommended for advanced users.

Note: Before you proceed with the installation, ensure that all prerequisite software components are installed and the database is set up, as described in "Preparing for Installation".

To install the RiskMinder components, perform the following tasks:

Navigate to the directory where the Arcot-RiskFort-3.1-Windows-Installer.exe file is located and double-click the file to run the installation wizard.
The Welcome screen appears.
Click Next to continue.
The License Agreement screen appears.
Carefully read the license agreement, select the I accept the terms of the License Agreement option, and click Next.
The installer now checks if any other CA product is installed on the computer.

If it does not find an existing CA product installation, then you are prompted for an installation directory. In this case, the Installation Location screen appears.

If the installer detects an existing CA product installation (an existing ARCOT_HOME), then:
- You are not prompted for an installation directory.
- In addition, you are not prompted for the database and encryption setup. The installer uses the existing database and encryption settings. As a result, you will see the screen in Step 8, though the configuration is disabled, and the screen corresponding to Step 12 is not displayed at all.
Click Next to install in the specified directory.
The Installation Type screen appears.
Select Custom to install the selected components in one ARCOT_HOME.
The Component Selection screen appears.
Deselect the components that are not required. By default, all components are selected for the installation.
For example, to install RiskMinder Server, Case Management Queuing Server, and Administration Console (without the SDKs and Sample Application) on the current system, you must select only the following options:
1. Arcot Risk Evaluation Server
2. Arcot Case Management Queuing Server
3. Arcot Administration Console
4. Arcot User Data Service
Note: To install Sample Application only, select the Arcot RiskFort SDKs and Sample Application option and then proceed with the installation.

The following table describes all components that are installed by the RiskMinder installer.

Component	Description
Arcot Risk Evaluation Server	This option installs the core Processing engine (RiskMinder Server) that serves the following requests from Administration Console: Risk Evaluation Configuration In addition, this component also installs the following Web services that have been built into the server: Risk Evaluation Web Service: Provides the web-based programming interface for risk evaluation with RiskMinder Server. User Management Web Service: Provides the web-based programming interface for the creation and management of users. Administration Web Service: Provides the web-based programming interface that is used by RiskMinder Administration Console.
Arcot Case Management Queuing Server	This option installs the core Queuing engine (Case Management Queuing Server) that allocates cases to the Customer Support Representatives (CSRs) who work on these cases. Note: At any given point in time, all instances of Administration Console can only connect to this single instance of Case Management Queuing Server.
Arcot RiskFort SDKs and Sample Application	This option provides programming interfaces (in form of APIs and Web services) that can be invoked by your application to forward risk evaluation requests to RiskMinder Server. This package comprises the following sub-components: Risk Evaluation SDK: Provides the Java programming interface for risk evaluation with RiskMinder Server. Sample Application: Demonstrates the usage of RiskMinder Java APIs. In addition, it can also be used to verify if RiskMinder was installed successfully, and if it is able to perform risk evaluation requests. Refer to "Configuring RiskMinder SDKs and Web Services" for more information on configuring these components.
Arcot Administration Console	This option provides the Web-based interface for managing RiskMinder Server and risk evaluation-related configurations.
Arcot User Data Service	This option installs UDS that acts as an abstraction layer for accessing different types of user repositories, such as relational databases (RDBMSs) and directory servers (LDAPs.)

Note: If you did not select the Arcot Risk Evaluation Server option on this screen, then screens in Step 7 through Step 9 does not appear.

Select Next to continue.
The Database Type screen appears.
Depending on the type of database you have, you can select Microsoft SQL Server, Oracle Database, or MySQL. Click Next to proceed.
If you selected Microsoft SQL Server on the Database Type screen, then the Microsoft SQL Server Database Details screen appears.

Note: If you are using Microsoft SQL Server database, then ensure that the ODBC Driver version you are using is the same as the one mentioned in the Configuring Database Server.

If you selected Oracle Database on the Database Type screen, then the Oracle Database Details screen appears.

If you selected MySQL on the Database Type screen, then the MySQL Database Details screen appears.
Based on your database choice in the preceding screen:
- If you selected Microsoft SQL Server, then fill in the following information in the fields.

Parameter	Description
ODBC DSN	The installer creates the DSN by using this value. RiskMinder Server then uses this DSN to connect to the RiskMinder database. The recommended value to enter is arcotdsn. Note: Database Source Name (DSN) specifies the information that is required to connect to a database by using an ODBC driver. This information includes database name, directory, database driver, User ID, and password.
Server	The host name or IP address of the RiskMinder datastore. Default Instance Syntax: <server_name> Example: demodatabase Named Instance Syntax: <server_name>\<instance_name> Example: demodatabase\instance1
User Name	The database user name for RiskMinder to access the database. This name is specified by the database administrator. (MS SQL Server, typically, refers to this as login.) This user must have the create session and DBA rights. Note: The User Name for the Primary and Backup DSNs must be different.
Password	The password associated with the User Name you specified in the previous field and which is used by RiskMinder to access the database. This password is specified by the database administrator.
Database	The name of the MS SQL database instance.
Port Number	The port at which the database listens to the incoming requests. The default port at which an MS SQL database listens is 1433. However, if you would like to specify another port, enter the port value in this field.

If you selected Oracle Database, then fill in the following information in the fields.

Parameter	Description
ODBC DSN	The installer creates the DSN by using this value. RiskMinder Server then uses this DSN to connect to the RiskMinder database. The recommended value to enter is arcotdsn. Note: Database Source Name (DSN) specifies the information that is required to connect to a database by using an ODBC driver. This information includes database name, directory, database driver, User ID, and password.
User Name	The database user name for RiskMinder to access the database. This name is specified by the database administrator. (MS SQL Server, typically, refers to this as login.) This user must have the create session and DBA rights. Note: The User Name for the Primary and Backup DSNs must be different.
Password	The password associated with the User Name you specified in the previous field and which is used by RiskMinder to access the database. This password is specified by the database administrator.
Service ID	The Oracle System Identifier (SID) that refers to the instance of the Oracle database running on the server.
Port Number	The port at which the database listens to the incoming requests. The default port at which an Oracle database listens is 1521. However, if you would like to specify another port, enter the port value in this field.
Host Name	The host name or IP address of the RiskMinder datastore. Syntax: <server_name> Example: demodatabase If you selected MySQL, then fill in the following information in the fields.
Parameter	Description
ODBC DSN	The installer creates the DSN by using this value. RiskMinder Server then uses this DSN to connect to the RiskMinder database. The recommended value to enter is arcotdsn. Note: Database Source Name (DSN) specifies the information that is required to connect to a database by using an ODBC driver. This information includes database name, directory, database driver, User ID, and password.
Server	The host name or IP address of the RiskMinder datastore. Default Instance Syntax: <server_name> Example: demodatabase Named Instance Syntax: <server_name>\<instance_name> Example: demodatabase\instance1
User Name	The database user name for RiskMinder to access the database. This name is specified by the database administrator. This user must have the create session and DBA rights. Note: The User Name for the Primary and Backup DSNs must be different.
Password	The password associated with the User Name you specified in the previous field and which is used by RiskMinder to access the database. This password is specified by the database administrator.
Database	The name of the MySQL database instance.
Port Number	The port at which the database listens to the incoming requests. The default port at which an MySQL database listens is 3306. However, if you would like to specify another port, enter the port value in this field.

After you specify the database details, test if you can successfully connect to the database by clicking the Test Data Source button and then verify the result of the same in the field below the button.
Note: If the connection was not successful, ensure that you have specified the correct database details and click Test Data Source again. Proceed only if the database connectivity is successful.
Click Next to continue.
The Encryption Setup screen appears. Use this screen to select the encryption mode and configure the information that is used for encryption.
Specify the following information:

Field Name	Description
Master Key	Specify the password for the Master Key, which is stored at <install_location>\Arcot Systems\conf\securestore.enc and will be used to encrypt the data stored in the database. By default, this value is set to MasterKey. Note: If you want to change the value of Master Key after the installation, then you must regenerate securestore.enc with a new Master Key value. See Changing Hardware Security Module Information After the Installation for more information.
Configure HSM	Select this option only if you will use a Hardware Security Module (HSM) to encrypt the sensitive data. If you do not select this option, then, by default, the data is encrypted by using the Software Mode.
PIN	Enter the password to connect to the HSM.
Choose Hardware Module	Choose one of the following HSMs that you plan to use: Luna HSM nCipher netHSM
HSM Parameters Note: The HSM parameter values are recorded in arcotcommon.ini, that is available at <install_location>\Arcot Systems\conf\. To change these values after installation, edit this file, as discussed in appendix, "Configuration Files and Options".	Set the following HSM information: Shared Library: The absolute path to the PKCS#11 shared library corresponding to the HSM. For Luna (cryptoki.dll) and for nCipher netHSM (cknfast.dll), specify the absolute path and name of the file. Storage Slot Number: The HSM slot where the 3DES keys used for encrypting the data are available. For Luna, the default value is 0. For nCipher netHSM, the default value is 1. The Pre-Installation Summary screen appears.

Review the information on this screen, and to change a previous selection, click Previous. After you change the required selection, click Next to go to the next screen.
Click Install to begin the installation process.
The Microsoft Visual C++ 2010 x86 Redistributable Setup screen appears. This screen appears only if the current system where you are installing RiskMinder does not have Microsoft Visual C++ 2010 x86.
On the Microsoft Visual C++ 2010 x86 Redistributable Setup screen:
1. Select the I have read and accept the license terms option, and click Install.
  The Installation Progress screen appears. This may take a few seconds. After some time the Installation Is Complete screen appears.
2. Click Finish to close the Microsoft Visual C++ 2010 x86 Redistributable Setup dialog and continue with the RiskMinder installation.
The Installing Arcot RiskFort screen appears. This may take several minutes. After some time the Install Complete screen appears.
Click Done to complete the installation.

Note: After the installation is completed, perform the post-installation tasks that are discussed in the following sections.

Installation Logs

After you complete the installation, you can access the installation log file (Arcot_RiskFort_Install_<timestamp>.log) in the <install_location> directory. For example, if you had specified the C:\Program Files directory as the installation directory, then the installation log file is created in the C:\Program Files directory.

If the installation fails for some reason, then error messages are recorded in this log file.