Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Oracle Applications R12 architecture

5,985 views

Published on

Oracle Applications R12 architecture

Published in: Technology
  • ➤➤ 3 Reasons Why You Shouldn't take Pills for ED (important) ★★★ https://tinyurl.com/rockhardxx
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • ➤➤ How Long Does She Want You to Last? Here's the link to the FREE report ◆◆◆ http://ishbv.com/rockhardx/pdf
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • ♣♣ 10 Easy Ways to Improve Your Performance in Bed...  http://ishbv.com/rockhardx/pdf
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • ♣♣ 10 Easy Ways to Improve Your Performance in Bed... ●●● https://tinyurl.com/rockhardxx
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Oracle Applications R12 architecture

  1. 1. Agenda • Technical Architecture – Architecture Diagram – 11i v/s R12 – Technology Components – Client, Application and Database Tiers – File System and Directory Structure • Swan User Interface • Multi-Org Access Control (MOAC) – Technical Considerations • Concurrent Processing – Program Definition – Restarting Request Set – OAF based Request Set Submission UI – Enhanced request security via RBAC • Oracle Application Framework – New and Enhanced Features • Oracle XML Publisher – New and Enhanced Features • Integration Repository
  2. 2. Technical Architecture
  3. 3. R12 Technical Architecture Diagram
  4. 4. 11i v/s R12 Architecture Comparison
  5. 5. New and Changed Technology Components – Client Tier Moving from Jinitiator to Native Sun Java plug-in – J2SE 1.5 Supported Browsers:  Internet Explorer (IE) 6.0  Netscape 7.2  FireFox 1.5  Safari 2.0
  6. 6. New and Changed Components – Application Tier Tech stack in Application tier builds on Fusion Middleware: Uses – Application Server 10.1.2 for Forms and Reports Services Replaces the 8.0.6 based 9iAS 1.0.2.2 tech stack Application Server 10.1.3 for Oracle Containers for Java (OC4J) Replaces the 8.1.7 based 9iAS 1.0.2.2 tech stack Oracle Jdeveloper 10.1.3 Following Middleware Components can be optionally integrated: Integration Services (OID 10g, BPEL Process Manager 10.1.3 etc) Identity Management (Single Sign On 10.1.2.0.2) Discoverer 10g (10.1.2.0.2) WebCache 10g (10.1.2.0.2) Portal 10.1.4 Oracle Collaboration Suite Oracle SOA Suite Oracle Master Data Management
  7. 7. New and Changed Components – Database Tier 9i R2 database in 11i has been upgraded to 10gR2 (10.2.0.2) in R12 Data model enhancements – Major enhancement to Trading Community Architecture to include Suppliers and Banks. Effectively TCA now includes following parties – Customers, Suppliers, Banks and Employees. Master Data Management - Data Hubs Single source of truth. Common Repository.
  8. 8. File System Changes – 11i File System 11i File System
  9. 9. New R12 file system model segregates Code, Data, Configurations INST_TOP - Release 12 introduces the concept of a top-level directory for an Applications instance. File System Changes – R12 File System
  10. 10. Compare R12 and 11i
  11. 11. Directory Structures Data Directory – $DATA_TOP - Located in database node and contains DB files like redo logs, table spaces and datafiles. <APPS_BASE>/db/apps_st/data DB Directory – $DB_TOP – Contains Oracle_Home for 10g Database. <APPS_BASE>/db/tech_st/10.2.0 Application Top – $APPL_TOP – Located on Application tier, contains product directories and files. <APPS_BASE>/apps/apps_st/appl Common Top – $COMN_TOP – directories and files used across products like HTML files, jar files etc. <APPS_BASE>/apps/apps_st/comn Instance Home – $INST_TOP – Introduced in R12 stores all the config files, log files, SSL certificates, document root etc on Application node. <APPS_BASE>/inst/apps/<appl_context>
  12. 12. Shared Application File System Application tier file system installed on a shared disk resource and is mounted from each application tier node. All nodes must be on same OS. Ability to provide any standard service from any node. Patching and maintenance to be performed once on a single node. Reduction in overall storage requirement. Simplifies addition of additional application tier node. Changes on shared file system are reflected immediately on all nodes. Global Single Instance
  13. 13. Multi-Org Access Control Technical Aspects
  14. 14. Access multiple operating units within a single application responsibility Perform tasks for and across multiple operating units Enter transactions Process data View information Run reports Increase effectiveness of shared services centers Multi-Org ....To Multi-Org Access Control
  15. 15. New Changes from Multi-Org ....To Multi- Org Access Control •As discussed above, security Profiles for data security oMO: Security Profile oList of operating units for a responsibility •OU field on UI oall transactions osetup data specific to OU, like transaction type •Enhanced Multi-Org Reporting and Processing •Ledger/Ledger Set parameter on accounting reports and processes •OU parameter on other standard reports and processes oFor example: submit the Payables Open Interface Import w/OU param null to import all records across all OUs
  16. 16. Where and how to define a security ProfileUsing Oracle HRMS, you can define your security profile using two forms: •The Security Profile form •The Global Security Profile form that is shown here.
  17. 17. Run Security List Maintenance Program Navigation: HR Responsibility  Processes and Reports  Submit Processes and Reports
  18. 18. Multi-Org Profile Options Profile Value Description MO: Security Profile (New in R12) MO: Default Operating Unit (New in R12) Controls the list of operating units that a responsibility or user can access MO: Operating Unit R11i profile option that will be maintained for those products and customers not leveraging Multiple Organizations. Controls which operating unit will default when accessing an application page
  19. 19. Multi-Org Preferences User Level Preferences Specify User Level Preferences Identify a subset of operating units to access Set default Operating Unit specific to that user
  20. 20. Add Preferences to Sub Menu Navigation: System Administrator  Application  Menu Application Developer  Application  Menu
  21. 21. To accomplish access to more than one operating unit within single responsibility –  Multi-org views have been replaced with synonyms. For example MY_TABLE will no longer be a view on MY_TABLE_ALL but a synonym pointing to MY_TABLE_ALL.  Data restriction is accomplished by assigning a Virtual Private Database (VPD) policy to the synonym. This policy allows system to dynamically generate additional restriction conditions when queries are run against the synonym. MOAC Technical Considerations
  22. 22. MOAC Technical Considerations How is client_info (org context) being replaced by policy context in Release 12? Prior to R12 a. A table is created in application schema, eg: PO_HEADERS_ALL IN PO schema. b. A synonym named PO_HEADERS_ALL is created in APPS schema, referring to PO.PO_HEADERS_ALL c. Create a view PO_HEADERS in APPS schema, as "select * from po_headers_all where org_id=client_info" In R12 a. A table is created in PO Schema, named PO_HEADERS_ALL b. A synonym named PO_HEADERS_ALL is created in APPS schema, referring to PO.PO_HEADERS_ALL c. Another synonym named PO_HEADERS is created in APPS, referring to PO_HEADERS_ALL synonym d. A Row Level security is applied to PO_HEADERS, using package function MO_GLOBAL.ORG_SECURITY. e. The effect of this policy is that,whenever you access PO_HEADERS, Oracle RLS will dynamically append WHERE CLAUSE - SELECT * FROM PO_HEADERS WHERE EXISTS (SELECT 1 FROM mo_glob_org_access_tmp oa WHERE oa.organization_id = org_id)
  23. 23. MOAC Technical Considerations Database Multi-Org Access Control Prior to R12 standard the org context was established using either DBMS_APPLICATION_INFO.SET_CLIENT_INFO or FND_CLIENT_INFO.SET_ORG_CONTEXT In R12 the org context is established using API MO_GLOBAL.INIT. This API accepts a single parameter “Application short name”.
  24. 24. Concurrent Processing
  25. 25. Concurrent Processing – Program Definition A new attribute in Concurrent Program definition “Operating Unit Mode” to categorize a program as MOAC enabled or not.  Single OU Concurrent Program  Multiple OU Concurrent Program  None (Null or blank value) This value can be set through Program definition OAF page in System Administration responsibility. Standard Request Submission – New Operating Unit field is displayed which has a LOV populated with operating units accessible to the user. Allows user to run programs for multiple operating units without changing responsibility.
  26. 26. Concurrent Processing – Restarting Request Set Prior to R12 – If a process in the middle of request set fails, user has to fix the cause and then either run remaining processes manually or re-submit the entire set. Secondly ones a request set is submitted, user had no control whatsoever. In R12 – If a process in the middle of request set fails, user can fix the cause of failure and restart the request set from the point of failure. User can put a running request set on hold and later remove hold to continue.
  27. 27. Concurrent Processing – OAF Request Set Submission UI Request Sets can now be submitted through a new OAF User Interface available in Release 12.
  28. 28. Oracle Application Framework
  29. 29. OA Framework - Overview What is OA Framework?  Oracle Applications development and deployment platform for HTML-based business applications.  Composed of a set of middle-tier runtime services as well as a design-time extension to Oracle JDeveloper called the OA Extension.  Based on J2EE based Model-View-Controller architecture.
  30. 30. OA Framework MVC Architecture OA Framework Model – implemented using Oracle Business Components for Java (BC4J). OA Framework View – implemented using an Oracle technology called User Interface XML (UIX). OA Framework Controller – Pure Java class implementation.
  31. 31. OA Framework New Features in R12 Personalization Administration Command line personalization import/export is now available in HTML pages included in Functional Administrator Responsibility. About This Page Now includes  Last 10 patches applied on the instance  Flexfield definitions on the page  Ability to launch Admin Personalization Corporate Branding Image Corporate branding logo can be changed using profile “Corporate Branding Image For Oracle Applications” Configurable Start Page Use preferences link to set the start page that displays after login.
  32. 32. Oracle XML Publisher 5.6.3 New and Enhanced Features
  33. 33. Overview XML Publisher 5.6.3 Technology means business !! Business means brilliant reporting !! Business Reports common requirements –  Segregation of data and presentation  Flexible output formats  Multi-lingual reports  Effective presentation with graphics  Pre-printed stationary  Regulatory compliance
  34. 34. XML Publisher Flexible Reporting Flexible Data sources Flexible Layouts Flexible Formats (output) Flexible Delivery Channels
  35. 35. New Features XML Publisher 5.6.3  Data Extraction Engine  Bursting Engine  Consolidated Document Publishing  Template Enhancements  Template Manager  Integration
  36. 36. XML Publisher Content in R12 Used across products from Finance to SCM to CRM 800+ seeded templates Seeded data definitions for modules like Payments Payment formats leverages XML Publisher
  37. 37. Sample RTF Template
  38. 38. XML Publisher Administrator Responsibility
  39. 39. XML Publisher Data Definition
  40. 40. XML Publisher Template Definition
  41. 41. Oracle Integration Repository
  42. 42. Integration Repository (iRep) Introduction R12Oracle Integration Repository –  Catalogue of all E-Business suite integration points  Acts as service broker  Shipped as part of E-Business Suite Includes screens for searching and viewing all available integration points with just a web browser. Interface Types supported –  PL/SQL APIs  Open Interface Tables  Interface views  Concurrent Programs  Java  Web Service  XML Gateway Messages  eCommerce Gateway Messages  Business Events
  43. 43. Navigation: Integration Responsibility  Integration Responsibility Integration Repository Screen
  44. 44. Integration Repository Search Screen
  45. 45. Integration Repository Search Result

×