Previous Topic: Configure Sample Application and CA Risk Authentication on the Same SystemNext Topic: Performing Risk Evaluation


Configure Sample Application and CA Risk Authentication on Different Systems

If Sample Application and RiskMinder Server are running on different systems, then you must complete the following steps to configure Sample Application:

  1. Ensure that the ca-riskauth-8.0-sample-application.war is deployed on the application server.

    Book: To ensure that Sample Application is deployed correctly, refer to the CA RiskMinder Installation and Deployment Guide for details.

  2. Navigate to the location where the Sample Application WAR file is deployed and open riskfort.risk-evaluation.properties file.

    Note: The deployment procedure (and App_Home) will depend on the application server that you are using.
    Refer to your application server documentation for detailed instructions.

    On Apache Tomcat, riskfort.risk-evaluation.properties is typically available at <Tomcat_Home>\webapps\riskfort-3.1.01-sample-application\WEB-INF\classes\properties\riskfort.risk-evaluation.properties.

  3. Change the value of HOST.1.

    HOST.1 represents the host name or IP address of RiskMinder Server. For example, HOST.1=10.150.1.111.

  4. Change the value of PORT.1.

    PORT.1 represents the port on which RiskMinder Server is listening to the incoming requests. For example, PORT.1=7680.

  5. (Optional, if RiskMinder Server not running in SSL mode) Perform this step only if you want to secure the communication between Sample Application and RiskMinder Server over SSL.

    In this case, change the value of TRANSPORT_TYPE to SSL:

    TRANSPORT_TYPE=SSL

  6. (Optional, if RiskMinder Server not running in SSL mode) Specify server CA certificate location for CA_CERT_FILE=<Server_CA_certificate_location>.

    Important! The certificate must be in PEM format.

    For example, CA_CERT_FILE=C:\certs\riskfort_ca.pem

  7. Save the changes and close the open files.
  8. Restart the application server on which the Sample Application is running.

With the completion of these steps, your Sample Application deployment is also complete. You can now start using it to understand the API workflow for each supported operation, as demonstrated in the following sections.