[Differences and changes between oracle EBusiness Suite 11i and 12i

Product: [Oracle E-Business Suite] Product Version: 12.0.x]
This document was authored by an Oracle customer and has not been subject to an independent technical review.

[Differences and changes between oracle E-Business Suite 11i and 12i.]

Document History
Author : [Syed Samiullah] Title: [Mr.] Date Created : [13-Apr-2009] Company : [Sierra Atlantic Software Services]

Enter the title of your white paper here
[Technical Differences and changes between oracle E-Business Suite 11i and 12i]

Changes at Database Level:
Database Version in 11i (11.5.9 & 11.5.10) was 9i Rel 2 where as in Release 12 its 10g R2 ( o Oracle Applications Tablespace Model (OATM) o Objects are classified by object type and access patterns o Transaction tables, Transaction indexes, Reference/SEED, Interface, Summary Management, Archive, No Logging, Queue, Media, Temporary, Undo, System o Uniform extents, locally managed, less fragmentation. o Total = 12 Tablespaces (11i: 400+) o Better Performance o PL/SQL operation 2x faster o PL/SQL Native Compilation

Changes at the Application Tier: The Below picture compares File system Structure difference between R11i and R12i 11i Apps file System Layout 12i Apps file System Layout • In Oracle Apps R12. Certificates (If SSL is enabled SSL Certificates & any other certificates specific to that server) and related log files or PID files (for Apache or any other process). This TOP will now hold any configuration files (specific to that server). You can see new TOP called INSTANCE_TOP in Application Tier. .

xml : defines J2EE applications and their shared libraries for runtime OC4J and points to other XML configuration files (rmi. global-web-application. Context file is under $INST_TOP/appl/admin 11i: $APPL_TOP/admin Configuration Files in 12i <apps_base>/inst/apps/<context_name>/ora/10. system-application.Apache/Apache/conf/ apps.xml.conf.xml. oracle_apache.xml.conf.env .properties in 11i are replaced with Oc4j.properties (used by EM agent) .xml.xml ./j2ee/oacore /application-deployments/oacore/ orion-application.xml .xml.conf. mod_oc4j.xml and etc) Orion-application.conf.conf & Jserv.xml : defines location of Java classes of all J2EE web modules deployed under J2EE application . security.Apache/Apache/conf/config/ ias. oc4j. application. oc4j-connectors./opmn/conf/ opmn. ssl.conf.xml.xml .xml. rmi./j2ee/oacore/config/ applications. system-jazn-data.xml.xml j2ee-logging. httpd.conf./j2ee/oacore /application-deployments/oacore/html/ orion-web.xml Jserv.jms.xml. default-web-site.3/ <context_name>.xml.properties. default-web-site.conf . global-web-application.1.In diagram tops with <>ST can be shared across servers (Shared Tier) and INSTANCE_TOP will be specific to Server.conf dms. url_fw.properties : defines basic Apps directory aliasing Server. server.xml.xml. jms.

xml rmi.err .log global-application.log jms.log log.1226534400.log jms. 4) Collection of configuration.log system-application.log jms.log .log global-application.forms_default_group_1 formsstd.log server.oacore oacore_default_group_1 (application. 3) Ability to share code (Applications.xml server.log log.log OC4J~oafm~default_group~1. code. ssl_engine_log .log log.Apache error_log.3 .log) Benefits of INST_TOP 1) Clear distinction between the location of data.out . .1226534400.log) .log global-application. Technology Stack) among multiple instances.out .oafm_default_group_1 oafmstd. access_log.log system-application.log system-application.log rmi.Oafm oafm_default_group_1 (application.oacore_default_group_1 oacorestd.1.Forms forms_default_group_1(application. logs is much easier since they are centrally located.log) .j2ee .err formsstd.Opmn opmn.xml : defines servlet level parameters for J2EE web modules LOG Files in 12i -----------------$LOG_HOME/ora/10. and configuration files.xml rmi.log OC4J~forms~default_group~1.log server. oacorestd.out .err oafmstd.log OC4J~oacore~default_group~1.log ascontrol-application. 2) Configuration and log files are centrally contained in the instance configuration home.Orion-web.log mapviewerapplication. in R12 D) Reports Version 6i in Apps 11i is replaced by Reports 10.3 which is built on Apache version 1. 4) Network traffic is more as HTTP protocol is more chatty so little bit Network bandwidth hungry when compared with SOCKET mode 5) No additional certificate requirement during SSL implementation for application tier.2 in R12 E) JDBC version is changed from version 9 in apps 11i to version 10.0 in R12 against JDK Version 1.2 built on Apache Version 1.3. Tech Stack changes in 12i Tech Stack in 11i Application Tier consist of iAS(1.3.2. 2) All connection is via HTTP Server so there is no need to start form server and no need to open form Server Port on firewall between client machine and application tier.5. 3) More secure as compared to Forms Socket Mode.0 in Apps R12 F) modplsql or mod_pls is removed from Apps R12 G) Java processes use JDK / JRE version 1.6) but in Applications R12 it is build on Fusion Middleware (10g Web Server and 10g Forms & Reports) Components differences in Application Tier A) HTTP Server or Web Server in R12 is Version 10.1.2 in Apps 11i Forms Servlet default deployment / communication mode Default Forms connection mode in Oracle Applications R12 is "SERVLET" where as in Oracle Apps 11i default form connect mode is "SOCKET" Oracle Form Servlet Overview in apps R12 ------------------------------------------------------1) In this mode.1.0.34. single .2.2) & Developer 6i (Forms & Reports 8.5) Can split ownership of apps and technology stack file systems.4. Java Servlet handles communication between forms client(java based) and Oracle Forms Service (10g).2.3.2. In apps 11i it is Version 1. 6) Ability to place the configuration home on a Network or a local file system for performance improvement.0.2.1 or 1.1.19 B) JServ in apps 11i is replaced by OC4J (mod_jserv is replaced by mod_OC4J) C) Forms Version 6i in Apps 11i is replaced by Forms 10.0.0.

rdf or files required to run CM node) Starting from R12. network traffic Metalink Advantage & Disadvantages of Forms Servlet Mode ------------------------------------------------------------------. covers some interesting points w. in multi node installation each APPL_TOP have its different name and files in each APPL_TOP will depend on type of Node (i.Simple SSL Configuration (as no separate SSL configuration is required for Forms as connections are via web/http server) -.1 Understanding the Network Overhead Of Forms Servlet Listener Architecture Compared to Forms Server. Forms Node will have fmx or forms related files where as APPL_TOP belonging to CM only node will have .More secure method of deployment over Internet -.e. it will use Unified APPL_TOP which means all files required for all middle tier services are included in all nodes of Multi Node installation (irrespective of services running on that node) .r. Unified APPL_TOP make more sense if you are using multi node Oracle Applications R12. In Oracle Applications 11i .Result in more network traffic because of HTTP is more chatty than socket (dedicated) so not preferred in WAN implementation.t.1 Using Forms Socket Mode with Oracle E-Business Suite Release 12 Are there any network overheads of using Forms in Servlet Mode ? --------------------------------------------------------------------------------------Note # 311091. -. How to change from default Servlet mode (in apps R12) to Socket mode ? --------------------------------------------------------------------------------------------Refer to Oracle Metalink Note # 384241.certificate will handle both forms & web connection.No port need to open to access forms in firewall. Unified APPL_TOP in Oracle Applications R12 -----------------------------------------------Unified APPL_TOP in Oracle Applications R12 which is different from Separate APPL_TOP in Oracle Applications 11i.

sh to start services on a node then it will start services which were configured to start during install on that node (You can still start a specific service even though it was not suppose to configure/start by calling startup script of that specific services). Now on Node1 when you use adstrtall.2 10g (BI publisher) (10. Summary of Changes from 11i to 12i ------------------------------------------------Component Database Release 11i 9.2) Fusion middleware 10g (1. only one copy (any one APPL_TOP) of Application Node files need to copy to target instance.sh script to start services as expected it will start Forms and Web services but unlike 11i.0.2 Release R12 10.Advantages of Unified APPL_TOP? Cloning of multi node Oracle Application install. To explain this better.2.1.sh FND_NODES From R12 all nodes will have Y against all services (For multi Node) in FND_NODES table. Services start/stop if you are using adstrtall. let’s assume you installed multi node R12 instance with Node 1 as Forms & Web Server where as Node 2 was installed with Concurrent Manager.3.2 (Apache Version ) (1.3.2. You can still start Concurrent Manager on Node1 by running adcmctl.0. Cloning of Multi Node to Single Node you don't have to merge APPL_TOP in R12 as required in 11i.19) Java Container Jserv .6) Application Server iAS OC4j Developer 6i (Forms & Reports) (8.

g.Rapid Install supports deploying the database node and the middle tier node into different domains. FORMS_TRACE_DIR FORMS_ environment variables replace FORMS60_ . Shared File System Support .Rapid install allows you to select if app servers are using shared APPL_TOP No hardcode apps password on Unix file system FNDCPASS Utility New Feature: Enhance Security With Non-Reversible Hash Password (enhance FND_USER password security) Improved Forgot password feature – Retrieve user_name and password – no workflow inbound process needed New environment variables e.Store Base Configuration in Database .No need to copy config.Client Plug-in Jinitiator Native Sun J2SE 1.txt Multiple Domain Support for Database and Middle Tier .5 Additional New Feature in R12 -------------------------------Rapid install .

Related: Note: 603104.increased downtime might be needed.Delete the lock file under persistence folder $ORA_CONFIG_HOME/10.1.lock Mod_plsql .1.3/j2ee/oacore/persistence/oacore_default_group_1/jms. stop. you should migrate your Web pages to Oracle Application Framework Oracle Reports Server Reports .Dependency on AutoConfig as a post step to everything .state.Delivers native runtime executables for Forms (frmweb) (11i: frmwebx) Forms Trace in addition to Forms Runtime Diagnostics (FRD) record both built-in Forms data and performance data in a single output (profile: Forms Runtime Parameters) Reports Only available through Concurrent Manager Reports Server is not used Reports executable rwrun is used directly Miscellaneous Challenges -------------------------R12 Cloning considerations .Need start.3/j2ee/forms/persistence/forms_default_group_1/jms.state. start .If you have custom development on mod_plsql. $ORA_CONFIG_HOME/10.3/j2ee/oafm/persistence/oafm_default_group_1/jms.1 Cloning Oracle Applications Release 12 with Rapid Clone Patch 6776948 : R12 RAPIDCLONE CONSOLIDATED FIXES JUL/2008 Problem with starting web services if web server crashed .1 Troubleshooting RapidClone issues with Oracle Applications R12 Note: 406982.1.Convert the reports to Oracle Application Framework (no automate tool to help you) .state.lock.lock $ORA_CONFIG_HOME/10. this method will not be supported in Oracle Fusion Applications) .Run the reports through the Concurrent Manager (rewrite any charts using the Oracle Reports Charting tool (BI Chart Bean).Convert the reports to Oracle XML Publisher (some automated tools are available to help you) .

. This document is provided for information purposes only and the contents hereof are subject to change without notice. . nor does it provide any other warranties or conditions. including implied warranties and conditions of merchantability or fitness for a particular purpose.603104. Oracle specifically disclaims any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. (it will not be supported in Oracle Fusion Applications ) References -.1 Troubleshooting RapidClone issues with Oracle Applications R12 -. Oracle does not warrant that this document is error-free. materials. information or software. Any content.Convert the chart to an Oracle Application Framework-based page that can be launched from Oracle Forms. information or software downloaded or otherwise obtained through the use of the site is done at your own discretion and risk. materials.1 Cloning Oracle Applications Release 12 with Rapid Clone Patch -. not of Oracle Corporation.6776948 : R12 RAPIDCLONE CONSOLIDATED FIXES JUL/2008 Disclaimer: The information in this document is the opinion of the author.406982.Oracle Graphics Integrations with Oracle Forms .Convert both the form and the chart to an Oracle Application Framework-based application. Oracle shall have no responsibility for any damage to your computer system or loss of data that results from the download of any content. whether expressed orally or implied in law.

Sign up to vote on this title
UsefulNot useful