Example: Enable Transaction Logging and Rule Processing

3-18 Oracle Fusion Middleware Developers Guide for Oracle Adaptive Access Manager profile.type.enum.pretransaction.name=PreTransaction profile.type.enum.pretransaction.description=Pre Transaction profile.type.enum.pretransaction.ruleTypes=user,device,location,in_session profile.type.enum.pretransaction.listTypes=vtusers profile.type.enum.pretransaction.finalactionrule=process_results.rule profile.type.enum.pretransaction.isPreAuth=false profile.type.enum.posttransaction=80 profile.type.enum.posttransaction.name=PostTransaction profile.type.enum.posttransaction.description=Post Transaction profile.type.enum.posttransaction.ruleTypes=user,device,location,in_session profile.type.enum.posttransaction.listTypes=vtusers profile.type.enum.posttransaction.finalactionrule=process_results.rule profile.type.enum.posttransaction.isPreAuth=false Transaction Page ■ Dynamically generates the transaction type selection menu based on transaction enums defined in property file bharosa_common.properties ■ On selecting transaction type, dynamically renders the transaction fields based on field definitions defined in properties files. ■ Either creates a transaction by calling AppUtil.createTransaction or updates the transaction by calling AppUtil.updateTransactiondepending on the current form being submitted. ■ Runs pre and post transaction rules by calling AppUtil.RunPreTransactionRules or AppUtil.RunPostTransactionRules. Depending upon the result, the browser is redirected to the next appropriate page. 4 Integrating Native Java Applications 4-1 4 Integrating Native Java Applications This chapter explains how to integrate Java applications with Oracle Adaptive Access Manager Server using the Oracle Adaptive Access Manager Java API. This integration is supported for applications written in Java 1.4 or higher. This section contains the following sections: ■ About the Oracle Adaptive Access Manager Shared Library ■ About VCryptResponse ■ Oracle Adaptive Access Manager APIs ■ Rules Engine ■ Customer Care

4.1 About the Oracle Adaptive Access Manager Shared Library

The Oracle Adaptive Access Manager Shared Library is the Java SDK for integrating with Oracle Adaptive Access Manager. This has to be deployed and targeted into the WebLogic Managed Server where the integrated application is deployed. Make sure the WebLogic Managed Server is part of the same WebLogic domain where OAAM is deployed.

4.1.1 Using Oracle Adaptive Access Manager Shared Library in Web Applications

Deploy the OAAM Web Applications Shared library IAM_HOMEoaamoaam_ libswaroaam_native_lib.war as a library. To use the Oracle Adaptive Access Manager Shared Library in Web applications, you must refer to the shared library by adding the following entry to your WebLogic deployment descriptor file, weblogic.xml: library-ref library-nameoracle.oaam.libslibrary-name library-ref

4.1.2 Using Oracle Adaptive Access Manager Shared Library in Enterprise Applications

Deploy the OAAM Enterprise Applications Shared library IAM_ HOMEoaamoaam_libsearoaam_native_lib.ear as a library. To use the Oracle Adaptive Access Manager Shared Library in Enterprise applications, you must refer to the shared library by adding the following entry to your WebLogic deployment descriptor file, weblogic-application.xml: library-ref 4-2 Oracle Fusion Middleware Developers Guide for Oracle Adaptive Access Manager library-nameoracle.oaam.libslibrary-name library-ref

4.1.3 CustomizingExtendingOverriding Oracle Adaptive Access Manager Properties

To override any Oracle Adaptive Access Manager properties or extend Oracle Adaptive Access Manager enumerations, add those properties and enumerations to bharosa_server.properties and place that file in WEB-INF\classes folder of the native web application. For instructions on customizing, extending, or overriding Oracle Adaptive Access Manager properties, refer to Chapter 7, Customizing Oracle Adaptive Access Manager.

4.2 OAAM Java InProc Integration

Follow these steps: 1. Make sure you have set the reference to OAAM shared library oracle.oaam.libs. 2. To override any Oracle Adaptive Access Manager properties or extend Oracle Adaptive Access Manager enumerations, add those properties and enumerations to bharosa_server.properties and place that file in the WEB-INF\classes folder of the native web application. 3. Set up OAAM Data Source with the JNDI name as jdbcOAAM_SERVER_DB_DS and point it to the OAAM database.

4.3 OAAM SOAP Integration

To call the OAAM APIs via SOAP instead of inproc, follow these steps in these sections.

4.3.1 Set up SOAP Security

Setup SOAP User on WebLogic Server and OWSM Policy Out-of-the-box, OAAM publishes Web services at the URL: oaam_ serverservices. This URL is protected with HTTP Basic authentication. Create a user that will be used for SOAP authentication, and add that user in the proper group. This user can access this URL. The user must be in the OAAMSOAPServicesGroup group. To set up the OWSM Policy to set HTTP Basic Authentication on oaam_ serverservices follow these steps: 1. Log in to Enterprise Manager using the URL http:weblogic-admin-hostname:portem. 2. Under weblogic_domain, select the domain and select oaam_server_ server1 under that and right click and select the Web Services option. 3. Click the Attach Policies link in top right area.

4. Select all the rows corresponding to OAAM Web Services and click the Next

button 5. To enable SOAP Authentication: