Integrate Oracle EBS with OAM

Introduction

Oracle© Access Manager (OAM) version 12.2.1.3 provides identity management and an access control system that enables users to access all supported applications. To integrate multiple Oracle E-Business Suites (EBS) version R12.2 with OAM for single sign-on (SSO), you need to perform integration steps on each EBS instance.

OAM systems

The following two systems comprise OAM:

• Identity System: Used to create and manage users and groups, providing self-registration and password management.
• Access System: Used to configure a single or multi-domain SSO solution for web and non-web-based applications, web pages, and other resources and to configure access management (authentication and authorization) to resources (web pages and applications).

Integration prerequisites

Before you begin integration, complete the following steps:

1. Apply the latest Active Directory® (AD) and EBS Technology Stack (TXK) Delta update packs.

2. Update the EBS application-tier Java® Development Kit (JDK) to a JDK 7 update 13
(January 2017 CPU) or later.

3. Install and configure OAM 12c Release 2 patch set 3 (12.2.1.3.0).

Steps to integrate EBS with OAM

1. Deploy EBS AccessGate

If there is no active online patching cycle, perform the registration on the run-file system. Otherwise, patch the file system. SSO is enabled only after completing the cycle and bouncing the instance.

Deploy AccessGate by running the EBS AccessGate provisioning utility with the following values:

• Context file for the target EBS environment
• Application value set to accessgate
• OAM server URL
• Managed server name, if you are not using the default
• Managed server listen port, if you are not using the default
• Log file location

The preceding script performs the following tasks:

1) Creates a managed server named oaea_server<n> if it does not already exist.
2) Creates a data source named OAEADatasource if it does not already exist.
3) Deploys the EBS AccessGate application named accessgate.

The utility has an optional managed server name value, which defaults to oaea_server1, and a managed server port value, which defaults to 6801 plus the port pool. If you want to deploy AccessGate to a non-default managed server, you can specify these values.

 2. Register EBS with OAM

Source the EBS environment on the RUN (R) file system. Confirm that the FILE_EDITION environment value returns run, which means you are on the correct file system. Ensure there is no active online patching cycle.

If you have integrated EBS with Oracle Internet Directory (OID), register OAM from the EBS technology stack utility by supplying the following values:

• OAM host and port
• OAM user name
• LDAP URL and port
• OID administrator user name
• Confirmation setting
• LDAP user search base
• LDAP group search base

 3. Test SSO integration

Log in to EBS from the standard application login page for your host, domain, and port.

When this redirects you to the OAM SSO page, log in by using valid OID user credentials.
After successful authentication, the system redirects you to your EBS home page.

4. Perform the online patching cycle

Run the file-system clone step to synchronize the changes to your run/patch file system before starting a new online patching cycle.

 OAM integration architecture differences
Two significant differences exist between OAM R12.1 and R12.2 architectures.

 R12.1 and 11i EBS integration with OAM and OID

To integrate EBS R12.1 with OAM, you need to install and deploy all the services, including Oracle HTTP Server (OHS) and Weblogic©, as shown in the following image. In R12.1, you need to manage more services, and it takes more resource hours to implement them in comparison to R12.2.

Insert image: Oracle EBS part 1.

Image source: Oracle E-Business Suite Technology Blog. 

 R12.2 Integration with OAM and OID

The integration of OAM has changed in EBS R12.2. Version R12.2, built on OHS, has Weblogic built-in, which significantly changes how you integrate EBS with other Oracle Fusion products, such as OAM. You need to configure and deploy Webgate and Accessgate. Deploy Webgate on top of R12.2 OHS 11g home, and deploy Accessgate as a separate managed server on top of R12.2 WebLogic, as shown in the following image:

Insert image: Oracle EBS part 2.

Image source: Oracle E-Business Suite Technology Blog. 

Conclusion
This blog describes how to integrate OAM with EBS 12.2 applications to maintain a single registration for an EBS instance. You can apply this integration on the run/patch file system in EBS 12.2 applications. Because OAM provides centralized, policy-based authentication and SSO for web-based applications and cloud services, this technology is necessary for organizations that use Oracle applications.