This chapter covers the tasks involved in migrating an existing natively integrated 10.1.4.5 application to 11g.
This chapter contains the following sections:
Prerequisites for Migration of an Existing Natively Integrated 10.1.4.5 Application
Migrating Native Static Linked (In-Proc) Applications to OAAM 11g
Migrating Native Applications that Cannot Use OAAM Shared Library
You must follow these prerequisites for migrating your existing natively integrated application:
Client must use the OAAM Shared Library for Native Integration which uses SOAP.
Client must specify the configurable properties in oaam_custom.properties and this file must be in the Java Classpath of the client application.
See Section 27.4, "Migrating Native Applications that Cannot Use OAAM Shared Library" if the Native Application cannot use the OAAM Shared Library
To migrate the natively integrated in-proc application to OAAM 11g, you must:
Add a reference to the OAAM Shared Library in the weblogic.xml file so that you can use the OAAM Shared Library.
Move all configurable properties to the custom properties file.
To use the OAAM Shared Library in Web applications, you must reference the oracle.oaam.libs shared library in the WebLogic deployment descriptor file, weblogic.xml file. Add the following entry to weblogic.xml:
<library-ref>
<library-name>oracle.oaam.libs</library-name>
</library-ref>
As part of migrating the application, you must perform these steps:
Move all the configurable properties to oaam_custom.properties.
In 10g all custom configuration overrides were created in the bharosa_client.properties file.
Remove/delete all other OAAM property files from the native application.
Remove/delete all old OAAM JAR files.
Follow the procedures in this section to migrate your native SOAP application to OAAM 11g.
To use the OAAM Shared Library in Web applications, you must reference the oracle.oaam.libs shared library in the WebLogic deployment descriptor file, weblogic.xml file. Add the following entry to weblogic.xml:
<library-ref>
<library-name>oracle.oaam.libs</library-name>
</library-ref>
As part of migrating the application, you must perform these steps:
Move all the configurable properties to oaam_custom.properties.
Add the following properties to oaam_custom.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.
Remove/delete all other OAAM property files from the native application.
Remove/delete all old OAAM JAR files.
For details on configuring SOAP/WebServices Access, refer to Section 4.3, "OAAM SOAP Integration.".
The following process covers migrating your existing 10.1.4.5 Natively Integrated application that is currently using SOAP authentication to 11g.
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 folder. $ORACLE_HOME is usually the ORACLE_IDM1 folder in the Middleware Home.
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 folder.
In 10g all client specific configuration overrides were created in the bharosa_client.properties file, now those overrides need to be created in the oaam_custom.properties file. This was typically the file modified on the server side for the same purpose. A oaam_custom.properties file that contains the contents of your old bharosa_client.properties with the addition of the following new properties must 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 set up in 10g, you will need to refer to "Setting Up Encryption" in the Oracle Adaptive Access Manager Installation and Configuration Guide, Release 10g (10.1.4.5) for creating a SOAP keystore for use with the new 11g environment.