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

C Upgrading from 3.5 to 10.1.4.3

This appendix contains information about upgrading the Oracle Adaptive Access Manager application and database repository from 3.5 to 10.1.4.3.

If you are upgrading the Oracle Adaptive Access Manager application and database repository from 3.5 to 10.1.4.5, there are two steps involved:

  1. Upgrade from 3.5 to 10.1.4.3.

  2. Upgrade from 10.1.4.3 to 10.1.4.5

This appendix covers information to upgrade from 3.5 to 10.1.4.3. For information on upgrading from 10.1.4.3 to 10.1.4.5, please refer to Appendix B, "Upgrading from 10.1.4.3 to 10.1.4.5."

C.1 Upgrading the Oracle Adaptive Access Manager Application Layer

In order to upgrade the Oracle Adaptive Access Manager application, please perform the procedures documented in this section.

This section contains the following topics:

C.1.1 Shut Down and Clean Up Logs

  1. Shut down Oracle Adaptive Access Manager-related web applications.

  2. Clean up all old logs.

C.1.2 Back Up the Existing Web Applications

To back up existing web applications:

  1. For both Adaptive Strong Authenticator and Adaptive Risk Manager, back up all the properties files under the <WEBAPPS_INSTALLED_DIR>/<WEBAPPS_NAME>/WEB-INF/classes directory to an <UPGRADE_TEMP_DIR> directory. The properties files will be used later in the upgrade process. An example of backing up the files is shown below.

    Mkdir c:\upgrade_10g_temp
    Copy  c:\tomcat\webapp\oarm\WEB-INF\classes c:\upgrade_10g_temp\oarm\classes
    

    Note:

    Ensure that this step is performed because certain property files must be copied back into their respective directories once the new war files have been exploded or unjarred.
  2. Back up Oracle Adaptive Access Manager (the deployed application) if you want to upgrade the Oracle Adaptive Access Manager components listed below.

    • Adaptive Strong Authenticator (Authenticator)

    • Adaptive Risk Manager (Tracker)

    You could back up Oracle Adaptive Access Manager applications by renaming the webapps directory or moving the files to a different directory.

    Note:

    This is an important step if you should need to restore an old application or any customer specific customizations.

C.1.3 Deploy and Configure the Web Applications

To deploy and configure the web applications:

  1. Copy and explode or unjar the new 10.1.4.3 war files (oasa.war and oarm.war) in the webapps directory. These war files are provided with the upgrade patch.

  2. Deploy the web applications.

    Please follow your platform-specific vendor-supplied deployment guide for instructions on how to install web applications.

  3. Once your web application is deployed, copy the properties files you saved (during Step 1 of the "Back Up the Existing Web Applications" section) into their respective WEB-INF\classes directories.

    • For the OASA directory (For example, <ASA_HOME>\WEB-INF\classes)

      • bharosa_client.properties

      • bharosa_app.properties

    • For the OARM directory (For example, <ARM_HOME>\WEB-INF\classes)

      • bharosa_server.properties

      • bharosa_app.properties

  4. Under the OARM directory (For example, <ARM_HOME>\WEB-INF\classes), modify the bharosa_server.properties by commenting out the following lines.

    • bharosa.hibernate.config.file

    • bharosa.c3p0.config.file

    • bharosa.db.driver

    • bharosa.db.ur

    • bharosa.db.username

    • bharosa.db.password

    Oracle Adaptive Access Manager no longer uses hibernate for object-relational mapping; therefore these lines must be commented out.

  5. Since Oracle Adaptive Access Manager 10.1.4.3 uses Oracle's TopLink for object-relational mapping, configure the sessions.xml for the connection manager. First, copy the sample_sessions.xml to sessions.xml under Adaptive Risk Manager's webapps classes directory. For example, <ARM_HOME>\WEB-INF\classes.

    Second, modify sessions.xml by following the directions in Chapter 13, "Configuring Database Connectivity."

C.2 Upgrading the Oracle Adaptive Access Manager Database Repository

The Oracle Adaptive Access Manager database repository must be upgraded as part of the Oracle Adaptive Access Manager upgrade process because the Oracle Adaptive Access Manager database is not backwards-compatible. Ensure that you upgrade the Oracle Adaptive Access Manager repository before starting the newly deployed application; otherwise, exceptions will appear in the log files.

If you are using an Oracle database, perform all the steps in the "Upgrading the Oracle Database Repository" section.

If you are using a SQL Server database, skip the "Upgrading the Oracle Database Repository" section, and perform all the steps in the "Upgrading the SQL Server Database Repository" section.

C.2.1 Upgrading the Oracle Database Repository

Upgrading the Oracle Database Repository involves:

Descriptions of the various scripts are also provided in this section for your reference.

C.2.1.1 Backing Up the Oracle Adaptive Access Manager Repository

Please make sure to take a full back up of the Oracle Adaptive Access Manager database repository before starting any migration step.

C.2.1.2 Running the Set Up Scripts

Using SQL*Plus on the database server, run the setup scripts as an Oracle Adaptive Access Manager repository user (For example, BRSAADMIN). The scripts must be run individually and in the following order:

  1. upd_oaam_obj_10_1_4_3.sql

  2. oracle_default_questions.sql (optional- if required)

  3. oracle_answerhints.sql

  4. oracle_bharosaconfig.sql

  5. oracle_scoringpolicy.sql

  6. oracle_validations.sql

After running the scripts, check the upd_oaam_obj_10_1_4.log for any errors.

C.2.1.3 Setup Scripts

The scripts used to upgrade the database for the Adaptive Access Manager database from 3.5 to 10.1.4.3 are described in detail below.

Run these scripts using the Oracle Adaptive Access Manager repository user.

For example, BRSAADMIN.

upd_oaam_obj_10_1_4_3.sql

The upd_oaam_obj_10_1_4_3.sql script will create or alter objects to support Oracle Adaptive Access Manager 10.1.4.3.

oracle_default_questions.sql (Optional)

The oracle_default_questions.sql script will populate the default questions set. Default questions are listed in the script.

Do not run this script if you already have challenge questions enabled.

Modify the script if changes are needed.

oracle_answerhints.sql

The oracle_answerhints.sql script will populate the default answer hints set.

oracle_bharosaconfig.sql

The oracle_bharosaconfig.sql script will populate the Oracle Adaptive Access Manager configuration table with the Oracle Adaptive Access Manager configuration.

oracle_scoringpolicy.sql

The oracle_scoringpolicy.sql script will populate the seed data for challenge question scoring.

oracle_validations.sql

The oracle_validations.sql script will populate the seed data for the validation of the challenge questions.

C.2.2 Upgrading the SQL Server Database Repository

Upgrading the SQL Server database repository involves:

Descriptions of the various scripts are also provided in this section for your reference.

C.2.2.1 Backing Up the Oracle Adaptive Access Manager Repository

Please make sure you take a full back up of the Oracle Adaptive Access Manager database repository before starting any migration step.

C.2.2.2 Running the Setup Scripts

Please use the SQL Server Management Console to run the setup scripts as an Oracle Adaptive Access Manager repository user (i.e. BRSAADMIN). You must run the scripts individually and in the following order.

  1. 001_mssql_upd_oaam_obj_10_1_4_3_sqlserver.sql

  2. 060_mssql_default_questions.sql (optional)

  3. 070_mssql_scoringpolicy.sql

  4. 080_mssql_answerhints.sql

  5. 090_mssql_validations.sql

  6. 100_mssql_bharosaconfig.sql

C.2.2.3 Setup Script Reference

The SQL scripts used to upgrade the database for the Adaptive Access Manager database from 3.5 to 10.1.4.3 are described below.

001_mssql_upd_oaam_obj_10_1_4_3_sqlserver.sql

This script will create or alter objects to support Oracle Adaptive Access Manager 10.1.4.3.

060_mssql_default_questions.sql (Optional)

This script creates default questions (seed data) as part of the database initialization process. The set of user challenge questions are loaded through this script

Note:

Run this script if you are using challenge questions for the first time. If you already have challenge questions enabled, please do not run this script

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.

C.3 Validating the Upgrade Process

To ensure upgrade process is successfully completed, please perform following steps.

  1. Log in to the Oracle Adaptive Access Manager repository.

  2. Check the number of tables in the database. There should be 183 tables.

  3. Check the entries in vcrypt_db_patches. The database should entries inserted for 10.1.4.3

    Select * from vcrypt_db_patches 
    
  4. Check the application logs for any error.

  5. Log in to Adaptive Risk Manager URL (for example: http://test.upgrade.com:9090/oarm) and go to HELP > ONLINE HELP >ABOUT.

    It should say, "Welcome to Oracle Adaptive Access Manager version - 10.1.4.3.xxxxxxx"

C.4 Backing Out or Rolling Back the Upgrade Process

In case a failure in the upgrade process occurred or for any other reason, you can back out or roll back the upgrade process by following the steps documented below.

  1. Stop the Oracle Adaptive Access Manager web applications.

  2. Restore the old database backup.

  3. Undeploy the newly deployed web applications.

  4. Copy and deploy the old backed up web applications.

  5. Restart the web applications.

  6. Validate the applications using the Adaptive Risk Manager and Adaptive Strong Authenticator URLs.