CA RiskMinder Windows Installation Guide › Deploying RiskMinder On a Single System › Performing Post-Installation Tasks › Bootstrapping the System › Performing Bootstrapping Tasks

Performing Bootstrapping Tasks

When you first log in to Administration Console as the Master Administrator (MA), the Summary screen for the Bootstrap wizard screen appears.

To bootstrap the system by using the wizard:

1. Click Begin to start the process.

   The Change Password screen appears.

2. Specify the Current Password, New Password, Confirm Password, and click Next.

   The Configure Global Key Label screen appears.

3. On the Configure a Global Key Label page:
   • Specify the Global Key Label, and click Next.

     RiskMinder enables you to use hardware- or software-based encryption of your sensitive data. (You can enable hardware-based encryption by using arcotcommon.ini file, while software-based encryption is enabled by default.) Irrespective of hardware or software encryption, Global Key Label is used for encrypting user and organization data.

     If you are using hardware encryption, then this label serves only as a reference (or pointer) to the actual 3DES key stored in the HSM device, and therefore must match the HSM key label. However in case of software-based encryption, this label acts as the key.

     Caution: After you complete the bootstrapping process, you cannot update this key label.

   • Specify the Storage Type to indicate whether the encryption key is stored in the database (Software) or the HSM (Hardware).
4. Click Next to continue.

   The Configure Default Organization screen appears.

5. Under the Default Organization Configuration section, specify the following parameters for the Default Organization:
   • Display Name: The descriptive name of the organization. This name appears on all other Administration Console pages and reports.
   • Administrator Authentication Mechanism: The mechanism that is used to authenticate administrators who belong to the Default Organization. Administration Console supports three types of authentication methods for the administrators to log in:
     • LDAP User Password

     If you select this option, then the administrators are authenticated by using their credentials that are stored in the directory service.

     Note: If this mechanism is used for authenticating administrators, then deploy UDS, as discussed in the section, "Deploying User Data Service (UDS)".

     • Basic

       If you select this option, then the built-in authentication method that is provided by Administration Console is used for authenticating the administrators.

     • WebFort Password

       If you select the WebFort Password option here, then the credentials are issued and authenticated by the AuthMinder Server. For this, the CA AuthMinder Server must be installed.

     Note: For information about installing and configuring AuthMinder, see the CA AuthMinder Installation and Deployment Guide.

6. Under the Key Label Configuration section of the Configure Default Organization screen, specify the following values:
   • Use Global Key: This option is selected by default. Deselect this option if you want to override the Global Key Label you specified in the preceding step and specify a new label for encryption.
   • Key Label: If you deselected the Use Global Key option, then specify the new key label that you want to use for the Default Organization.
   • Storage Type: This field indicates whether the encryption key is stored in the database (Software) or the HSM (Hardware).
7. Click Finish to complete the bootstrapping process.

   The Administration Console initialization is completed, as indicated in the Finish screen.

8. Click Continue to proceed with other configurations by using Administration Console.

Starting RiskMinder Server

To start RiskMinder Server:

1. Click the Start button on your desktop window.
2. Navigate to Settings, Control Panel, Administrative Tools, and then Services.
3. Locate and double-click Arcot RiskFort Service.
4. Click Start in the service window.

Note: If you want to stop RiskMinder Server, then follow the Steps 1 through 3, and click the Stop button in the service window.

Starting the Case Management Queuing Server

To start Case Management Queuing Server:

1. Click the Start button on your desktop window.
2. Navigate to Settings, Control Panel, Administrative Tools, and then Services.
3. Locate and double-click the Arcot RiskFort Case Management Queuing Service.
4. Click Start in the service window.

Note: If you want to stop the Case Management Queuing Server, then follow the Steps 1 through 3, and click the Stop button in the service window.

Deploying User Data Service (UDS)

RiskMinder can access user data either from a relational database (RDBMS) or directly from an LDAP server by using UDS, which is an abstraction layer that provides RiskMinder seamless access to the third-party data repositories deployed by your organization.

You need the arcotuds.war file to deploy UDS, as follows:

1. Deploy arcotuds.war on the application server. This file is available at:

   <install_location>\Arcot Systems\java\webapps\
   

   For example, in the case of Apache Tomcat, deploy the WAR file at <APP_SERVER_HOME>\webapps\.

   Note: The deployment procedure depends on the application server that you are using. See the application server vendor documentation for detailed instructions.

2. (For WebSphere Only) Configure to reload the UDS class when the application files are updated.
   1. Navigate to Application, Enterprise Applications and access the UDS settings page.
   2. Under Class loader order, select the Classes loaded with local class loader first (parent last) option.
   3. Under WAR class loader policy, select the Single class loader for application.
   4. Click Apply to save the changes.
3. (For JBoss Only) Perform the following steps, if you have deployed UDS on a JBoss application server:
   1. Copy the Bouncy Castle JAR file (bcprov-jdk15-146.jar) from <install_location>\Arcot Systems\java\lib\ to the following location:

      <JBOSS_HOME>\common\lib\
      

   2. Navigate to the following location:

      <JBOSS_HOME>\server\default\conf\
      

   3. Open jboss-log4j.xml file in a text editor.
   4. Add the following log configuration in the <log4j:configuration> section:

      <appender name="arcotudslog" class="org.apache.log4j.RollingFileAppender">
      <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"></errorHandler>
      <param name="Threshold" value="INFO"/>
      <param name="MaxFileSize" value="10MB"/>
      <param name="MaxBackupIndex" value="100"/>
      <param name="Encoding" value="UTF-8"/>
      <param name="Append" value="true"/>
      <param name="File" value="${arcot.home}/logs/arcotuds.log"/>
      <layout class="org.apache.log4j.PatternLayout">
      <param name="ConversionPattern" value="%d{yyyy-MM-dd hh:mm:ss,SSS z} : [%t] : %-5p : %-5c{3}(%L) : %m%n"/>
      </layout>
      <filter class="org.jboss.logging.filter.TCLMCFilter">
      <param name="AcceptOnMatch" value="true"/>
      <param name="DeployURL" value="arcotuds.war"/>
      </filter>
      <!-- end the filter chain here -->
      <filter class="org.apache.log4j.varia.DenyAllFilter"></filter>
      </appender>
      

   5. Add the following line in the com.arcot category that you created while Deploying Administration Console:

      <appender-ref ref="arcotudslog"></appender-ref>

   6. Add the following line in the cryptographic category that you created while Deploying Administration Console:

      <appender-ref ref="arcotudslog"></appender-ref>

   7. Save and close the file.
4. Restart the application server.
5. Verify if UDS was deployed successfully:

   Note: The arcotuds.log file is used for logging UDS-related information.

   1. Navigate to the following location:

      <install_location>\Arcot Systems\logs\
      

   2. Open the arcotuds.log file in any editor and locate the following line:
      • User Data Service (Version: 2.0.3) initialized successfully.

      This line indicates that UDS was deployed successfully.

   3. Also ensure that the log files do not contain any FATAL and WARNING messages.
   4. Close the file.

Deploying Sample Application

Important! Sample Application must not be used in production deployments. It is recommended that you build your own web application by using Sample Application as a code-reference.

Sample Application can be used to verify if RiskMinder was installed and configured properly. In addition, it demonstrates:

• The typical RiskMinder workflows
• The basic operations (invocation and post-processing) of RiskMinder APIs
• Integration of your application with RiskMinder

Sample Application is automatically installed as a part of Complete installation of RiskMinder. To deploy Sample Application:

1. Deploy the riskfort-3.1-sample-application.war file from the following location:

   <install_location>\Arcot Systems\samples\java\
   

2. If necessary, restart the application server.
3. Access Sample Application in a Web browser window. The default URL for Sample Application is:

   http://<host>:<appserver_port>/riskfort-3.1-sample-application/index.jsp
   

Verifying the Installation

After you have seeded the database schema, deployed UDS and Administration Console, and bootstrapped the system, and started the Server, ensure that all these components have started correctly. The log files that you must verify for this purpose is arcotriskfort.log.

To verify if the server started correctly:

1. Navigate to the following location:

      <install_location>\Arcot Systems\logs\
   

2. Open the arcotriskfortstartup.log file in any editor and locate the following lines:
   • STARTING Arcot RiskFort 3.1_w
   • Arcot RiskFort Service READY
3. Open the arcotriskfortcasemgmtserverstartup.log file in any editor and locate the following lines:
   • STARTING Arcot RiskFort Case Management 3.1_w
   • Arcot RiskFort Case Management Service READY

Note: Also ensure that the log files do not contain any FATAL and WARNING messages.