8 Installing and Configuring Adaptive Access Manager Offline

Note:

If you do not plan to use Adaptive Risk Manager Offline, you may skip this chapter.

Adaptive Risk Manager Offline is an offline fraud analysis tool that evaluates existing transaction data for three main purposes:

First, Adaptive Risk Manager Offline can be used as a stand alone security tool to analyze, detect and alert high risk transactions.
Secondly, Adaptive Risk Manager Offline can be used as a research and development tool to create and verify new models and rules using offline customer data without impacting customers in real-time environment.
Thirdly, Adaptive Risk Manager Offline can be used as a supplemental offline analysis tool in the tuning of rules and verification of rules behavior against real customer data without impacting customers in real-time environment.

Figure 8-1 Adaptive Risk Manager Offline Architecture

This illustration shows the ARM Offline architecture

8.1 Installation Checklist for Adaptive Risk Manager Offline

The installation and configuration of the Adaptive Risk Manager Offline is similar to the Adaptive Risk Manager Online. A table is provided below for your reference.

Task	Adaptive Risk Manager Offline
Verify prerequisites are met for offline installation	[ ]
Create Oracle Adaptive Access Manager database schema. Refer to Chapter 3, "Creating an Oracle Database Schema," or Chapter 4, "Creating a SQL Server Schema."	[ ]
Install application server. Refer to the vendor-supplied documentation for instructions on how to install the application server.	[ ]
Configure database connectivity (JNDI or JDNBC). Refer to Chapter 13, "Configuring Database Connectivity."	[ ]
Unzip oaam_rm_offline.zip.	[ ]
Under the webapps directory, create a rmoffline folder.	[ ]
Unjar oarm_offline.war into rmoffline folder.	[ ]
Create user roles in application server. Refer to the vendor-supplied documentation for instructions on how to create user roles. A list of the expected groups/roles is provided in Chapter 6, "Installing Adaptive Risk Manager."	[ ]
Install the Sun JDK. Go to http://java.sun.com Click the download link, and follow the instructions to install the Sun JDK.	[ ]
Generate KeyStore. Refer to Chapter 10, "Setting Up Encryption." The oarm_offline.zip does not include the oaam_utils directory. The file is part of oaam_bin.zip.	[ ]
Copy bharosa_server.properties.sample to bharosa_server.properties. If bharosa_server.properties.sample is not in the offline package, copy it from an online installation. Refer to Chapter 12, "Configuring Server Properties."	[ ]
Update bharosa_server.properties. Refer to Chapter 12, "Configuring Server Properties." Note: You do not need to set up the background images path.	[ ]
Copy sample.sessions.xml or sample_jndi.sessions.xml to sessions.xml and update it accordingly. Refer to Chapter 13, "Configuring Database Connectivity."	[ ]
Create log directories. Refer to Chapter 16, "Setting Up Logging."	[ ]
Update log4j.xml. Refer to Chapter 16, "Setting Up Logging."	[ ]
Copy the bharosa_app.properties file from an online installation or package. You will not need to modify this file. Note: The bharosa_app.properties file that shipped with the offline package must be replaced with the one from online.	[ ]
Rejar and deploy the war file.	[ ]
Take backup of all updated files.	[ ]
Verify that the database is running.	[ ]
Verify that the listener is running.	[ ]
Verify that the application server is running.	[ ]
Verify that the users are set up	[ ]
Verify that the connection URL, username, and password are in the sessions.xml	[ ]
Verify that Log4J is set up properly.	[ ]
Log in to Adaptive Access Manager Offline. Refer to Chapter 20, "What to Do Next."	[ ]
After logging into the application, please verify the logs for any issues.	[ ]

8.2 The Offline Database

The following sections provide best practices for the Adaptive Risk Manager Offline database.

8.2.1 Database Server with Good I/O capability

Make sure the host that runs the database server has good I/O capability. Offline processing in most cases is I/O intensive.

8.2.2 Proper Database Server Configuration

Make sure the database initialization parameters are set as per the recommendations in Section 3.3, "Oracle Initialization Parameters."

8.2.3 Database Indexes

Make sure to obtain and apply the latest Oracle Adaptive Access Manager database patch to ensure that the proper indexes are present.

8.3 What to Do After Installing Adaptive Risk Manager Offline

After you have completed the installation procedures, refer to the Oracle Adaptive Access Manager Administrator's Guide for information on how to use the Adaptive Risk Manager Offline to evaluate existing transaction data.