Professional Documents
Culture Documents
Sara Woodhull
Principal Product Manager, EBS ATG
Siva Puthurkattil
1 Copyright 2012, Oracle and/or its affiliates. All rights reserved.
The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle's products remains at the sole discretion of Oracle.
2 Copyright Oracle 2012, Oracle its affiliates. All reserved. rights Copyright 2012, and/or and/or its affiliates. All rights reserved.
Program Agenda
Integration examples
Lake County Purchasing Portal
EBS Screen
EBS Screen
Custom Screen
EBS Screen
Custom Screen
EBS Screen
EBS Screen
Custom Screen
EBS Screen
Custom Screen
EBS Screen
Custom Screen
EBS Screen
Custom Screen
EBS Screen
EBS Screen
EBS Screen
EBS Screen
Custom Screen
Custom Screen
Custom Screen
Custom Screen
Web Services, URL, Java Have multi-channel rich user interfaces Same development platform as Oracle Fusion Applications Support mobile devices
10
Database
11 Copyright 2012, Oracle and/or its affiliates. All rights reserved.
Web Services
Legacy Systems
Applications Unlimited
12
needs to:
Use flexfields
Have rich user interface components that are specific to ADF (hierarchy
viewer, carousel)
Have same look and feel as the E-Business Suite application
13
14
15
Custom Application
ADF Application EBS SDK
16
Messages
AppsDataSource
17
including ADF and deploy on external application server Use E-Business Suite security Use AppsDataSource to access EBS database
AppsDataSource
UMX|APPS_SCHEMA_CONNECT role
External server does not need APPS
password
External application can call stored
Users
AppsDataSource
JAAS
Custom Application (ADF)
not need to share session context with EBS (UI independent of EBS UI)
Use AppsDataSource to provide access to
database
AppsDataSource Users
Roles
20
Seamless Navigation
EBS
to database
Either separate ADF pages or Hybrid
OAF Pages
Resps
information
Identified by ICX session cookie on browser
22
23
Using JAAS
Session uses JAAS for authentication/authorization
Must use AppsDataSource to access EBS data Does not share EBS session or context Use EBS users and UMX roles instead of responsibilities Can use services and EBS routines that do not need EBS context Can use logging
24
25
If user logs out of external application, user automatically logs out of EBS
User will see pages in language set in EBS preference Embed ADF regions on OA Framework pages
26 Copyright 2012, Oracle and/or its affiliates. All rights reserved.
27
28
Three Examples
Different Use Cases
Standalone application using JAAS, independent session
Lake County
29
(R12.HR_PF.B.Delta.5)
30
management Launches from EBS home page Logging out logs out EBS too Calls EBS PL/SQL APIs
31
Added to existing responsibility Built ADF application using enterprise role for security
32
33
34
Purchasing Portal
35
Purchasing Portal
Purpose deliver a solution that meets the major business needs of the purchasing domain.
Currently these are scattered around in EBS and the custom application - Bid Interface. Bid Interface (written in ASP)- Allows vendors to register with the Lake County for various service areas.
Whenever there is a bid published on the Lake County website, the registered vendors would get an
Leveraging EBS SDK for Role/Responsibility based security solution for the purchasing portal. Unified reporting solution.
36
Purchasing Portal
EBS Environment Oracle R12.1.3 (Oracle Financials, HR & Payroll), Oracle DB 11g, RHEL 5.7 on
VMWare ESX 5
JDeveloper 11.2.1.0, WebLogic 10.3.6, Oracle E-Business Suite SDK for Java. EBS - UMX Roles to Responsibilities Mapping:
UMX|BOSS_BID_ACCESS_REPORTS -> BOSS Inquiry
37
Purchasing Portal
Login Page
38
Purchasing Portal
Reports Tab Users need BOSS Inquiry Responsibility
39
Purchasing Portal
Purchasing Portal
EBS Security
User who doesnt have the access to the Reports Tab.
41
Purchasing Portal
Legacy application drawbacks.
Information retrieval was cumbersome for users as it is from multiple
application sources.
Multiple applications with its own access credentials made application access
42
Purchasing Portal
Benefits of the new portal with ADF and EBS SDK
Unified web application interface to support the purchasing functionality.
43
Purchasing Portal
Phase 1 Status: Live
Went live in Aug 2012.
Challenges
Page not authorized message due to deployment issues. System-jazn.xml was not updated with the Resource grants after deployment. Solution: Check the resource permissions in application policies from EM.
44
Purchasing Portal
Next Phase
Phase 2 of the project would replace all the legacy and custom applications with the unified
https://blogs.oracle.com/jruiz/entry/securing_adf_applications_using_the
45
Roadmap
46
47
Summary
Choose the right technology for your EBS extension
OA Framework, Oracle ADF, or both
Use Oracle E-Business Suite SDK for Java with Oracle ADF
AppsDataSource EBS security With or without EBS context
48
Resources
Oracle E-Business Suite Software Development Kit for Java (My
Oracle Support Doc ID 974949.1) Oracle E-Business Suite System Administrator's Guide Security
See Oracle Application Framework Documentation Resources, Release 12
(Doc ID 391554.1)
See OA Framework - How to find the correct version of JDeveloper to use with
49
50
Statements of Direction
Early Adopter Programs Subscribe via email or RSS
51
52
Q&A
53