Skip Headers
Oracle® Adaptive Access Manager Installation and Configuration Guide
Release 10g (10.1.4.5)

Part Number E12050-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

4 Creating a SQL Server Schema

The Oracle Adaptive Access Manager Application Server which hosts Adaptive Risk Manager and/or Adaptive Strong Authenticator products needs access to the database server that contains the Oracle Adaptive Access Manager schema and it needs to be populated with some initial data.

The creation of the database schema is the same for both Adaptive Risk Manager Online and Offline.

You can install the Oracle Adaptive Access Manager schema in either an Oracle database or a SQL Server 2005.

If you are planning to install the schema in an Oracle database, go to Chapter 3, "Creating an Oracle Database Schema."

Note:

If you are planning a proxy installation, you must install the Adaptive Manager Access Manager schema first before proceeding to the proxy installation.

This chapter provides the steps and information about the scripts to be run for installation and initialization of the Oracle Adaptive Access Manager Database on SQL Server 2005.

This chapter contains the following topics:

4.1 Prerequisites

The scripts for installing and initializing the Oracle Adaptive Access Manager database are located in oaam_db/full_schemas/sqlserver2005_database_setup.zip.

For a database with globalization support, the scripts are located in oaam_db/full_schemas/sqlserver2005_globalized_database_setup.zip.

Ensure the following pre-installation tasks have been completed before you install and initialize your database.

  1. Create the directories for the database files. For example: x:\sqldata.

  2. Update the 010_cr_bharosa_db.sql with the directory path for the database using the same path that you used in step 1.

  3. Optionally, you can change the database name. If you change the name, you need to update all the files manually for the new database. The default database name is bharosa_db.

4.2 Installation Steps

Installing and initializing the Oracle Adaptive Access Manager Database schema is a three-step process.

Refer to Section 4.1, "Prerequisites" to ensure that you have completed the preliminary steps before using the scripts.

The steps for installing and initializing the Oracle Adaptive Access Manager Database are:

  1. Create Database

  2. Create Login

  3. Load Initialization Data

4.3 Scripts

The following SQL scripts will be used to set up the database for the Oracle Adaptive Access Manager Database. Use the SQL Server Management Console to run the scripts in the order presented below.

4.3.1 Create Database

010_cr_bharosa_db.sql - This script creates the bharosa_db database. Modify the location of data file prior to executing this script.

4.3.2 Create Login

020_cr_bharosa_db_login.sql - This script creates the database user called brsamain and grants the appropriate privileges.

Note:

Update the script for the password in order to set a non-default password.

4.3.3 Load Initialization Data

The scripts to load initialization data are listed below.

  • 040_mssql_user_init.sql - This script populates the user group as part of the database initialization.

  • 050_mssql_policy_init.sql - This script creates the default policy and policy set as part of the data base initialization process.

  • 055_mssql_default_locales.sql - This script populates the locale table with seed data.

  • 070_mssql_scoringpolicy.sql - This script will populate the seed data for challenge question scoring.

  • 080_mssql_answerhints.sql - This script will populate the default answer hints set.

  • 090_mssql_validations.sql-This script will populate the seed data for the validation of the challenge questions.

  • 100_mssql_bharosaconfig.sql - This script will populate the Oracle Adaptive Access Manager configuration table with the Oracle Adaptive Access Manager configuration.

4.4 Database Properties

The recommended properties to be set at the Instance Level are

Advanced

Processors: