Skip Headers
Oracle® Fusion Middleware Developer's Guide for Oracle Adaptive Access Manager
11g Release 1 (11.1.1)

Part Number E15480-08
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

17 Migrating Native Applications to OAAM 11g

This chapter covers the tasks involved in migrating an existing natively integrated 10.1.4.5 application that is currently using SOAP authentication to 11g.

17.1 Preparing for Migration

Pre-requisites are as follows for migration of your existing natively integrated application:

17.2 Migrating Native Static Linked (In Proc) Applications to OAAM 11g

This native integration involves only local API calls and therefore no remote server risk engine calls. The integration embeds the processing engine for OAAM with the application and enables it to leverage the underlying database directly for processing.

To migrate the natively integrated inproc application to OAAM 11g, proceed as follows:

17.2.1 Use the OAAM Shared Library Instead of Static Linking to OAAM Jars

To use the Oracle Adaptive Access Manager Shared Library, you must refer to the shared library by adding the following entry to your WebLogic deployment descriptor file, weblogic.xml:

<library-ref>
       <library-name>oracle.oaam.libs</library-name>
</library-ref>

17.2.2 Move All Configurable Properties into bharosa_server.properties File

As part of migrating the application, you must perform these steps:

  1. Move all the configurable properties to bharosa_server.properties.

  2. Remove/delete all other OAAM property files from the native application.

  3. Remove/delete all old OAAM jar files.

17.3 Migrating Native SOAP Applications to OAAM 11g

The web application communicates with OAAM via Web Services.

Follow the procedures in this section to migrate your native SOAP application to OAAM 11g.

17.3.1 Use OAAM Shared Library Instead of Static Linking to OAAM Jars

To use the Oracle Adaptive Access Manager Shared Library, you must refer to the shared library by adding the following entry to your WebLogic deployment descriptor file, weblogic.xml:

<library-ref>
       <library-name>oracle.oaam.libs</library-name>
</library-ref>

17.3.2 Move All Configurable Properties into the bharosa_server.properties File

As part of migrating the application, you must perform these steps:

  1. Move all the configurable properties to bharosa_server.properties.

  2. Make sure the following properties are set in bharosa_server.properties:

    • vcrypt.tracker.soap.useSOAPServer=true

    • vcrypt.soap.disable=false

    • bharosa.config.impl.classname=com.bharosa.common.util.BharosaConfigPropsImpl

    • bharosa.config.load.impl.classname=com.bharosa.common.util.BharosaConfigLoadPropsImpl

  3. Remove/delete all other OAAM property files from the native application

  4. Remove/delete all old OAAM jar files

17.3.3 Configure SOAP/WebServices Access

For details on configuring SOAP/WebServices Access, refer to "Configuring SOAP Web Services Access" in the Oracle Fusion Middleware Administrator's Guide for Oracle Adaptive Access Manager.

17.4 Migrating Native Applications that Cannot Use OAAM Shared Library

The process below covers migrating your existing 10.1.4.5 Natively Integrated application that is currently using SOAP authentication to 11g.

17.4.1 Use the OAAM 11g Jar Files

After those files are copied, you can copy the oaam_core.jar file from the $ORACLE_HOME/oaam/cli/lib folder into your applications library directory. $ORACLE_HOME is usually the ORACLE_IDM1 folder in the Middleware Home.

17.4.2 Copy the OAAM 11g Property Files

All updated property files and libraries are located in the $ORACLE_HOME/oaam/cli folder. The conf/bharosa_properties folder contains the updated properties, and the lib folder contains the updated libraries.

To upgrade your existing natively integrated application, you can start by removing the contents of your existing bharosa_properties folder, and replacing them with the contents of the $ORACLE_HOME/oaam/cli/conf/bharosa_properties directory.

17.4.3 Specify the Configurable Properties in the bharosa_server.properties File

In 10g all client specific configuration overrides were created in the bharosa_client.properties file, now those overrides need to be created in the bharosa_server.properties file. This was typically the file modified on the server side for the same purpose. A bharosa_server.properties file that contains the contents of your old bharosa_client.properties with the addition of the following new properties needs to be created in your application's bharosa_properties folder that contains the following information:

# New Properties

vcrypt.tracker.soap.useSOAPServer=true

vcrypt.soap.disable=false

bharosa.config.impl.classname=com.bharosa.common.util.BharosaConfigPropsImpl

bharosa.config.load.impl.classname=com.bharosa.common.util.BharosaConfigLoadPropsImpl

These new properties will tell the new libraries to use the Generic SOAP implementation classes for communicating with the OAAM Server component, and instead of looking to the OAAM database to read the properties typically retrieved from the BharosaConfig class to retrieve them from the local property files.

It is noted above that these properties are to be used in addition to the existing contents of your bharosa_client.properties file which should include your soap user name, and soap keystore information. Note: If you did not have SOAP authentication setup in 10g, you will need to refer to "Setting Up Encryption" in the 10.1.4.5 Oracle Adaptive Access Manager Installation and Configuration Guide for creating a SOAP keystore for use with the new 11g environment.