This post covers FREE video on Architecture & Components in Oracle EBS R12.2-OAM/OID/OUD Integration for Single Sign-On (SSO) taken from the Lessons II of Module I in our Oracle EBS – OAM integration Training.
In this lesson, We are going to look at Architecture & various Components that are part of EBS-OAM/OID/OUD Integration
Below is one of the slide from our Training showing Architecture & Components that are part of Integration i.e. WebGate, AccessGate, Access Manager, Oracle Directory Service (OID or OUD), and DIP (not shown in diagram)
Oracle E-Business Suite R12.2 comes with Oracle Fusion Middleware and We have two Components in that Fusion Middleware, that are Oracle HTTP Server (or Web Server) and Oracle Weblogic Server.
Oracle Weblogic Server is the application server on which we have forms, oacore and other applications (In R12.2 Access Gate is also deployed on this WebLogic Domain).
In a typical Non-SSO environment, a user tries to access EBS 12.2 URL and submit username and password. Then username and password will be validated against FND_USER table in EBS 12.2 database.
When you integrate Oracle E-Business Suite with Oracle Access Manager(OAM), then the flow is slightly different. In SSO environment we deploy two components, Oracle Access Manager and Oracle Internet Directory (OUD is supported from 12.2.5+) which is an LDAP Server.
On E-Business Application tier, we put two more components, one is AccessGate and second is Webgate.
Webgate is nothing but a Policy Enforcement Point (PEP) whereas OAM acts as Policy Decision Point (PDP). Whenever any request comes to EBS from User, WebGate will first take that request to Oracle Access Manager for Authentication (ATN) & Authorization (ATZ).
AccessGate is a Java Application that gets deployed on Oracle Weblogic Server (Part of R12.2). Note: In R12.1 and prior, you install & create Weblogic Domain and deploy AccessGate on this domain
Once authentication is successful with OAM and request comes back to WebGate with an authenticated User ID & GUID, then Accessgate will take this User ID & GUID connects behind the scene with E-business Database, Validate this user one more time to see if the user exists in EBS 12.2 Database FNS_USER table.
If User exists with same User ID, it will link this user with the user coming from OID/OAM Authentication. AccessGate will create a session in E-Business Suite FND_SESSION in Oracle E-Business Suite Database and allow the user to access E-Business Suite application tier.
Note: In Oracle EBS R12.1, there is a slight difference and that is accessgate and webgate are deployed outside the E-Business Application tier. They can be on the same machine or can be on a separate machine as of E-Business Suite.
Whether you are new to Oracle Apps or an Expert Oracle Apps DBA, Register for this FREE Oracle EBS-OAM integration webinar with Me (Oracle ACE & Author Atul Kumar).
Did you find this video about “Architecture and Components in Oracle EBS R12.2-OAM integration”useful?
Are you having any queries about architecture and components in Oracle EBS 12.2-OAM integration?
Have a question related to your Oracle Apps DBA Career or Training in Oracle?
Post under comments below for instant reply or feedback so we can post more FREE videos like above.
If you have not yet downloaded FREE eBook – 7 Docs every Oracle Apps DBA must-read for EBS R12 integration with OAM/OID for SSO get a copy in your Email