Previous Topic: Additional SDK ConfigurationsNext Topic: RM_3.1--SSL Communication Between RiskMinder Components


Configuring a Backup RiskMinder Server Instance

RiskMinder enables you to configure the Java SDK to communicate with a primary RiskFort Server instance at any given time. However, you can configure it to fail over to a backup instance if the primary instance fails. To do so, you must edit the SDK properties file (riskfort.risk-evaluation.properties). In case the backup is unavailable for some reason, then the JDK fails over back to the primary instance.

By default, this properties file provides the entries to configure one RiskFort Server instance. These entries are appended with 1, which indicates that only one instance is configured. To configure the backup instance, you must duplicate these entries and append the instance number (2) accordingly.

To configure the backup server instance:

  1. Ensure that you have the required instances of RiskFort up and running.

    Book: Depending on your deployment - Single-System or Distributed - see "Deploying RiskFort On a Single System" or "Deploying RiskFort on a Distributed System", respectively, in CA RiskMinder Installation and Deployment Guide for detailed information on how to bring up instances of RiskFort.

  2. Navigate to the following location:
  3. Open riskfort.risk-evaluation.properties by using an editor of your choice.
  4. Ensure that the value of HOST.1 is set to the host name or the IP address of the primary server instance.
  5. Also ensure that the value of PORT.1 parameter is set to the port number on which the RiskFort Native or the Transaction Web Service protocol is listening.
  6. Add the following un-commented entry:
    HOST.2=
    PORT.2=
    
  7. Set the value of the corresponding TRANSPORT.<n> parameter to the required communication mode. By default, it is set to TCP.

    See "SSL Communication Between RiskMinder Components" if you want to change the communication mode to SSL.

  8. Save the changes and close the file.