Previous Topic: Deploy User Data ServiceNext Topic: Install CA Risk Authentication on the Second System

CA Risk Authentication Windows Installation Guide › Deploy User Behavior Profiling Application

Deploy User Behavior Profiling Application

The User Behavioral Profiling (UBP) model measures the similarity or dissimilarity of the current transaction to prior access by the same user, or that of their peer group in cases of insufficient data. CA Risk Authentication communicates with the UBP application to get the similarity score and include it in the risk evaluation score.

You need the ca-userprofiling-2.0-application.war file to deploy UBP.

Follow these steps:

  1. Deploy ca-userprofiling-2.0-application.war on the application server. This file is available at the following location: 
    <install_location>\Arcot Systems\java\webapps\

    Example: For Apache Tomcat, deploy the WAR file at <APP_SERVER_HOME>\webapps\.

    Note: The deployment procedure depends on the application server that you are using. For more information, see Application Server Vendor documentation.

  2. (For WebSphere) Configure to reload the UDS class when the application files are updated.
    1. Navigate to Application, Enterprise Applications, UDS Settings.
    2. Select the Class loader order, Classes loaded with local class loader first (parent last) option.
    3. Select the WAR Class loader policy, Single class loader.
    4. Copy bcprov-jdk15-146 jar file from <ARCOT_HOME>/sdk/java/lib/external to the the following location: 
      <JRE_HOME>/lib/ext folder

      Note: Here, JRE_HOME is the jre installation used by WebSphere application server.

    5. Click Apply.

    (For WebLogic: Refer to WebLogic documentation on how to use third party JDBC drivers)

  3. Restart the application server.
  4. Verify if UDS is 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 ubp_logfile.log file in any editor and locate the following statement:
    3. Verify that the log files do not contain any FATAL and WARNING messages.
    4. Close the file.