Oracle Applications R12 architecture
•Transferir como PPT, PDF•
4 gostaram•8,053 visualizações
Oracle Applications R12 architecture
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Semelhante a Oracle Applications R12 architecture
Semelhante a Oracle Applications R12 architecture (20)
Mais de Sekhar Byna
Mais de Sekhar Byna (20)
Último
Último (20)
Oracle Applications R12 architecture
- 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
- 3. R12 Technical Architecture Diagram
- 4. 11i v/s R12 Architecture Comparison
- 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. 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
- 8. 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.
- 9. File System Changes – 11i File System 11i File System
- 10. 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
- 11. Compare R12 and 11i
- 12. 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>
- 13. 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
- 14. Multi-Org Access Control Technical Aspects
- 15. 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
- 16. 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
- 17. 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.
- 18. Run Security List Maintenance Program Navigation: HR Responsibility Processes and Reports Submit Processes and Reports
- 19. 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
- 20. 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
- 21. Add Preferences to Sub Menu Navigation: System Administrator Application Menu Application Developer Application Menu
- 22. 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
- 23. 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)
- 24. 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”.
- 26. 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.
- 27. 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.
- 28. Concurrent Processing – OAF Request Set Submission UI Request Sets can now be submitted through a new OAF User Interface available in Release 12.
- 30. 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.
- 31. 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.
- 32. 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.
- 33. Oracle XML Publisher 5.6.3 New and Enhanced Features
- 34. 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
- 35. XML Publisher Flexible Reporting Flexible Data sources Flexible Layouts Flexible Formats (output) Flexible Delivery Channels
- 36. New Features XML Publisher 5.6.3 Data Extraction Engine Bursting Engine Consolidated Document Publishing Template Enhancements Template Manager Integration
- 37. 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
- 40. XML Publisher Data Definition
- 41. XML Publisher Template Definition
- 43. 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
- 44. Navigation: Integration Responsibility Integration Responsibility Integration Repository Screen
Notas do Editor
- In the traditional, Forms-based Oracle Applications environment, the JVM (which in earlier releases was Oracle JInitiator) was run as part of the standard Applications sign-on process.Now,with the move to a mainly HTML-based environment, the JVM (now the J2SE Plug-in)is only invoked when a user chooses to access functions that require it, such as running a form. The Forms client applet no longer uses browser JVM for this instead uses the plug-in.
- The Oracle E-Business Suite Release 12 uses several individual components delivered as part of the Oracle Application Server suite. These individual components include the Oracle HTTP Server (powered by Apache), PL/SQL, Forms Server, Reports Server, Workflow, and many others In particular, E-Business Suite Release 12 uses OracleAS 10g 10.1.2 for Forms & Reports Services, replacing the 8.0.6-based ORACLE_HOME provided by the Oracle9i Application Server 1.0.2.2.2 in E-Business Suite Release 11i. In addition, E-Business Suite Release 12 uses OracleAS 10g 10.1.3 for Oracle Containers for J2EE (OC4J), replacing the 8.1.7-based ORACLE_HOME provided by Oracle9i Application Server 1.0.2.2.2 in E-Business Suite Release 11i.
- Using an Instance Home provides the ability to share Applications and technology stack code among multiple instances,for example a development instance and a test instance.Equally,the centralization of configuration log files for a particular instance makes their management simpler.
- Instance Home - Provides the ability to share Applications and technology stack code among multiple instances,for example a development instance and a test instance.
- Shared APPL_TOP v/s shared application file system: Shared APPL_TOP means only APPL_TOP and COMN_TOP are shared across application tier node but in case of shared application file system, entire application tier file system is shared. Environment settings Handout.
- Now let’s take a look at the new security feature Multi-Org Access control.
- In 11i, when a user had to enter or process data for multiple operating units, he or she had to login to different responsibilities because each responsibility could only access one operating unit. So if you had a centralized payment processing center where a single user processed payments for multiple organizations, he would have to keep logging in and out of different responsibilities to process payments for a different organization or operating unit. Now in Release 12, Multi-Org Access Control enables users to access, process, and report on data for an unlimited number of operating units within a single applications responsibility.
- When you’re done with setting up your security profile, you open the Submit Request window and run the Security List Maintenance program. And this will ensure that all of your security profiles that you created will be available for assignment to your responsibilities. This is an important step to do, otherwise you will not see your security profile in the list of values when you try to assign to the MO: Security Profile profile option. So make sure you run this program and make sure it completes successfully. In the next setup step, when you set your system profile options, you will see that your newly created security profiles will be available.
- Here, we have the list of profile options related to Multiple Organizations or MO for short in Release 12. The first two are new. Actually they both existed in 11i, but they didn’t do anything. Now in Release 12, the MO Security Profile controls the list of operating units that a responsibility or user can access. So you would assign the Security Profile that you just created to this profile option. The second profile option called MO: Default Operating Unit is optional and allows you to specify a default operating unit that will be the default when you open different subledger application pages. Because users can access multiple operating units, you may want to set up a default one instead of forcing users to constantly have to choose one. When we talk about the User Preferences later, you can also specify a default operating unit at the user level. The last profile option is really for backwards compatibility and to support products that do not use Multiple Organizations. Whatever your Release 11i setting was for this will be preserved during upgrade. That leads me to my next point. If you’re happy with how you processed transactions in 11i, then when you upgrade to R12, you don’t have to do anything. You only need to define a security profile and assign it to the first profile option if you want to take advantage of this exciting feature. If you specify a security profile for the MO: Security Profile, then those products that use Multiple Organizations will ignore the MO: Operating Unit profile option. If you set the security profile at the responsibility level, then all users using that responsibility will have access to only the operating units available in the security profile. If you set the security profile at the user level, then the user will have access to only those operating units, irrespective of application responsibility that they log into. Use the MO: Default Operating Unit profile option to set the operating unit context or default operating unit when accessing an applications. The Release 11i MO: Operating Unit profile option will continue to be supported in Release 12 as not all customers or Oracle products require multiple organizations.
- Multi-Org Preferences really allows the user to control the list of operating units they have access to. So the system administrator may create a security profile that has 10 operating units assigned and assign it to the user or his/her responsibility. But, let’s say that a user only deals with 5 of them on a daily basis and he doesn’t want his work space cluttered with extraneous operating units. The user could set up Multi-Org preferences to restrict the list of OUs. And because the user has complete control over this, he can change it at anytime. In addition, the user can specify a default operating unit. Of course, this default operating unit will override the Default Operating Unit profile option.
- To enable and display Preferences in your menu, request your System Administrator to add the function, FNDMOPREFS to your menu definition. The System Administrator should use either the System Administrator or Application Developer responsibility and select the Menu (Application) option. Select your product’s menu and add the function named User Preferences (FNDMOPREFS). Above screenshot is an example using the Oracle Payables setup menu.
- Need to add screen shot.
- Was introduced in 11i10 as an additional service and was not shipped with 11i E-business suite. As an instance is patched, the repository is automatically updated with appropriate content to ensure consistency.