<Insert Picture Here>

Oracle E-Business Suite Release 12 Upgrade

Ray Lin
Customer Service Support Manager
 Agenda

• Introduction <Insert Picture Here>

• New Technology Review

• New Features
• Upgrading Your Applications
• Summary
 <Insert Picture Here>

Introduction
 R12 Technology Enables You
to Deliver Best ROI
• Uptaking new technology lowers costs
• Proven technologies deliver better experience
• Latest standards provide better integration
• Less training with familiar and improved Apps
• New features empower administrators and users
• OC4J
• Instance Home
• Identity Management, Portlets, Certificate Management
• Upgrading is easy
• Maintain your investment
• Productive new development tools
• Transform configurations
 <Insert Picture Here>

New Technology Review

 Overview of Technology Stack
Changes from EBS 11i to 12
• New Versions of Mid Tier Technology
• Application Server: 1.0 -> 10.1
• Servlet Container: JServ -> OC4J
• Apache: 1.3.19 -> 1.3.34
• Forms & Reports: 6 -> 10
• R12 File System Change:
• The two 11i middle tier Oracle homes are replaced with
newer versions
• Instance Home vs. Source Home
11i Installed & Managed File System

iAS 1.0.2.2 Developer6i Database Major Components:

ORACLE HOME ORACLE HOME ORACLE HOME
•Java Home: 8.1.7-based
iAS 1.0.2
RSF 8.1.7 RSF 8.0.6 RSF 10.2
•C Home: 8.0.6-based
Apache 1.3 Forms 6 Developer 6
RDBMS
Components
•Database Home: 10.2
JServ Reports 6
•Appl Top: Applications’
code staging area
APPL TOP •Common Top: Runtime
location for Java, HTML,
run-time generated files
COMMON TOP
R12 Installed & Managed File System

iAS 10.1.3 Developer10.1.2 Database Major Components:

ORACLE HOME ORACLE HOME ORACLE HOME
•Java Home: 10.1-based
iAS 10.1.3 –new
RSF 10.1 RSF 10.1 RSF 10.2
•C Home: 10.1-based
Apache 1.3 Forms 10 Developer 10 standalone
RDBMS install of AS 10.1.2
Components phase2 –new
OC4J Reports 10
•Database Home: 10.2
•Appl Top: Applications’
APPL TOP code staging area
•Common Top: Runtime
COMMON TOP location for Java, HTML
•Instance Top:
configuration and run-
INSTANCE TOP time generated files –new
 Desktop Client Tier

• Moving from JInitiator to Native Sun Java plug-in

• Native Sun J2SE 1.5 (5.0)

• Supported Browsers:

Browser Version Client OS

Browser - IE 6.0 Windows 2000 and XP
Browser - FireFox 1.5 Windows 2000 and XP
Browser - Safari 2.0 Macintosh OSX 10.4
 Application Server Tier

• OracleAS 10g 10.1.2 for Forms & Reports Services

• Replaces the 8.0.6-based Oracle_Home provided by iAS
1.0.2.2 in 11i
• OracleAS 10g 10.1.3 for Oracle Containers for Java
(OC4J)
• Replaces the 8.1.7-based Oracle_Home provided by iAS
1.0.2.2 in 11i
• Oracle JDeveloper 10.1.3
• JDBC 10.2
 Database Server Tier

• 10g Database 10.2

• Improved Manageability
• Automatic Workload Repository
• Automatic SGA Tuning
• Better Performance
• PL/SQL operation 2x faster
• PL/SQL Native Compilation for
RAC
• Functional Improvements
• Enhanced VPD support
simplifies multi-org access
control architecture for R12
Release 12 Technology Stack
3-Tier Logical Architecture

Client Application Database

OC4J Global Single

JDBC/SQL Net
Data Model

HTTP / S
JSP

Web Listener
BC4J RAC & ASM

UIX
Partitioning
Reports

Forms Data Guard

 Technologies Inside EBS R12
Highlights

• OracleAS 10.1.3 J2EE • JDK 1.5.0_08 on apps server

• OracleAS 10.1.2 Forms • JDK 1.5.0_09+ on desktop
• Database 10.2.0.2 • Pre-patched file system
• XDK 10.2 • New shared file system with
• OJSP 10.1.3 Oracle Config Home so that
• JDBC 10.2.0.2 Appl Top and Oracle Homes
can be read only
• JEWT 2.3.36
• Newer versions of everything
 Technologies External to EBS R12
Highlights

• Installed and integrated separately from Rapid Install

• Discoverer 10.1.2
• SSO/OID 10.1.2
• Portal 10.1.4
• WebCache 10.1.2
• Collab Suite 10.1.2
• Warehouse Builder 10gR1
• Enterprise Manager 10.1.2
• Integration Server 10.1.3
• BPM 10g
 <Insert Picture Here>

New Features
 New Features

• File System
• Forms10
 <Insert Picture Here>

New Features:
File System
 Instance Home Advantages

• Clear distinction between the shared file system and

the file system unique to an instance
• Ability to share code (Apps, technology stack) among multiple
nodes and even instances (Dev,Test, Production)
• Enables split ownership of applications and technology stack
file systems
• Improves code safety by making shared file system read-only
while not patching
• Configuration and log files are co-located
• Easier collection of instance state
• Ability to use network or local storage for various file
system portions
• Minimize disk usage and maximize performance
 File System Overview
FILESYSTEM CHANGES
APPMGR
OLD NEW
APPL_TOP $HOME/<SID>appl $HOME/apps/apps_st/appl
COMMON_TOP $HOME/<SID>comn $HOME/apps/apps_st/comn
ORACLE_HOME $HOME/<SID>ora/8.0.6 $HOME/apps/tech_st/10.1.2

IAS_ORACLE_HOME $HOME/<SID>ora/iAS $HOME/apps/tech_st/10.1.3

ORACLE
OLD NEW
ORACLE_HOME $HOME/<SID>db/10.2.0 $HOME/db/tech_st/10.2.0
ORADATA $HOME/<SID>data $HOME/db/apps_st/data
INSTANCE TOP
OLD NEW
INST_TOP N/A $HOME/inst/apps/<context_name>
 Environment Variable Overview

ENVIRONMENT FILE/VARIABLE CHANGES

OLD NEW
Env Source File APPSORA.env APPS<SID>.env
This file executes the following env files
$ORA_CONFIG_HOME/10.1.2/$TWO_TASK.env
$APPL_CONFIG_HOME/$TWO_TASK.env

Context File (MT) $APPL_TOP/admin/$TWO_TASK.xml $APPL_CONFIG_HOME/admin/$TWO_TASK.xml

OA_HTML $COMMON_TOP/html $COMMON_TOP/webapps/oacore/html

JAVA_TOP, OA_JAVA $COMMON_TOP/java $COMMON_TOP/java/classes

AF_JLIB N/A $COMMON_TOP/java/lib

JAVA_BASE N/A $COMMON_TOP/java/
FND_SECURE $FND_TOP/secure/<SID>/ $INST_TOP/apps/fnd/12.0.0/secure/
ADMIN_SCRIPTS_HOME $COMMON_TOP/admin/scripts/<SID>/ $INST_TOP/admin/scripts/

LOG_HOME $APPL_TOP/admin/<SID>/logs/ $INST_TOP/logs

FORMS_WEB_CONFIG_FILE $OA_HTML/appsweb.cfg $INST_TOP/ora/10.1.2/forms/server/appsweb.cfg

 <Insert Picture Here>

New Features: Forms10

 What is New in Forms10

• Native Forms runtime executable (frmweb) with shared

library for user exits (fndfmxit), replaces the statically
linked Applications runtime executable (frmwebx)
• Updated Swan UI
• Forms Trace in addition to Forms Runtime Diagnostics
(FRD)
• Forms Servlet is default deployment / communication
mode
• Customers with severe WAN performance problems
can use Forms Server only in conjunction with
hardware for SSL and load balancing
 What is New in Forms10

• FORMS_ environment variables replace FORMS60_

• New environment variables e.g. FORMS_TRACE_DIR
• The Forms builder is available as part of the AS 10.1.2 home in
EBS R12 on Solaris/Linux/Win for debugging situations
• For development use, Forms builder needs to be installed
separately as part of the Developer Suite
• $ORACLE_HOME/bin/frmbld.sh replaces f60desm for design
• Modify frmbld.sh shell script to customize settings e.g. FORMS_PATH
• Generation tools are delivered as part of the Runtime Services and
Developer Suite installations
• frmcmp.sh and frmcmp_batch for generation
• Modify the shell script to customize settings
 Architecture Overview

• 10.1.3 Home delivers

• OC4J instances including one for Forms
• Service Management
• 10.1.2 Home delivers
• Runtime (10.1.2.0.2) executables $ORACLE_HOME_1012/bin/frmweb
• Forms generator
• Forms diagnostics and translation utility
• Applications delivers
• Configuration Files via the Instance Home
• Shared library for the user exits $FND_TOP/bin/fndfmxit (referenced by
the FORMS_USEREXITS environment variable)
 Oracle Reports

• Oracle Reports, like Forms, is supplied from the

Oracle Applications 10.1.2 home
• Only available through Concurrent Manager
• Reports Server is not used, and no servlet or cgi is
used
• Reports executable rwrun is used directly
 Deployment Decisions
Forms Servlet vs. Server

• Forms10 is deployed in 10.1.3 oc4j container

• By default configured as servlet
• Instructions on configuring Forms Server
• No native SSL – must use hardware solution
• No native load balancing – must use hardware solution
• To migrate execute: $FND_TOP/bin/txkrun.pl
-script=ChangeFormsMode -mode=socket
• For more details see Oracle MetaLink Note 384241.1
 <Insert Picture Here>

Upgrading Your
Applications
 What You Can Start Today

• Increase storage available for your database since

upgrade to Apps R12 will likely increase your dbf’s
(some tests implied 10%)
• Upgrading your database to 10gR2 – it is certified
with 11i (Oracle MetaLink Note 362203.1) and this
upgrade is a mandatory part of the EBS R12 upgrade
• Apps R12 no longer uses (disables) mod_plsql; if you
have any custom use for it, start planning a migration
• Oracle Graphics is no longer present in Application
Server. Reports which rely on it will need to be
modified and we recommend using XML Publisher
Analysis & Planning
Application Migration Path

Release Level Upgrade Path

R11.0 Release 11.5.10 CU2

Release 12
R11.5.1 - R11.5.6 Release 11.5.10 CU2
Release 12
R11.5.7 - R11.5.8 Release 12

R11.5.9 - R11.5.10 Release 12

Analysis & Planning
OS Requirement

Release Level Notes

Sun Solaris (SPARC) 402312.1

Linux 402310.1
Microsoft Windows 402311.1

HP-UX (PA-RISC) 402308.1

HP-UX (Itanium) 402307.1

IBM AIX 5L 402306.1

 Analysis & Planning
OS Requirement
• Certification Information
• Operating Systems Requirements
• Operating System Supported Versions
• Required OS Patches
• Required Packages
• Software Requirements
• ar
• ld
• make
• X Display Server
• Other Requirements
• ulimit Value Settings
• Kernel Settings
 Analysis & Planning
Custom Code Requiring Changes

• Forms
• Reports
• C code
• Java code
• Framework
• AutoConfig Configuration Customizations
• Development Tools: compilers, Forms/Reports
Builder 10.1.2, JDev 10.1.3
• User Interfaces: new look & feel
 Analysis & Planning
Workload Estimates

Here is what we found in transitioning our own code to

the new technology stack:
• Most code upgraded seamlessly
• Percent of files manually touched:
• Forms: ~10% of forms and libraries needed touching
• Reports: ~1% of reports needed touching
• C code: ~20% of C code needed touching
• Java code: ~1% of overall Java code needed touching
• JSP’s: ~50% of JSP’s needed touching

• The above might not reflect your applications /

customizations being upgraded
 Upgrade Phases

• Plan uptake project

• Perform build of customizations to identify failures
• First make changes which DO NOT require new
technology stack
• Roll out central infrastructure for development with
the new technology stack
• Make changes that DO require new stack
• Complete switch to new code and technology
• Perform run time testing
 <Insert Picture Here>

Summary
 R12 Technology Enables You
to Deliver Best ROI
• Uptaking new technology lowers costs
• Proven technologies deliver better experience
• Latest standards provide better integration
• Less training with familiar and improved Apps
• Upgrading is easy
• Maintain your investment
• Productive new development tools
• Transform configurations
 Uptaking New Technology Lowers
Costs
• Proven technologies deliver better experience
• AS technologies fine tuned through three 9.0.x releases
• New native RAC tools simplify advanced configurations
• Latest standards provide better integration
• Industry standard specs like J2EE servlet, JSP, SOAP, JMS
• EBS Portlets publishable on any WSRP 1.0 compliant Portal
• Less training with familiar and improved Apps Stack
• Oracle Wallet Manager provide consumer side certificate
management
• Desktop use of native Sun JDK simplifies administration of
multiple Java applications
 Easy to Upgrade

• Maintain and extend your investment

• Customizations and custom applications have simple
upgrades
• Administration tools persist from 11i with added abilities
• Existing SSL certificates can be reused
• Productive new development tools
• JDeveloper 10.1.3
• Forms10 Builder
• Latest compilers and libraries
• Transform configurations
• AutoConfig simplifies upgrades
 New E-Business Suite Technology Stack Blog

http://blogs.oracle.com/schan

• Certification, desupport announcements

• Discussion architectures, advanced
configurations
• Early Adopter Programs
• Statements of Direction
• Supports RSS feedreaders
• Discuss Apps technology stack topics
with senior Development Architects
The preceding 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 remain at the sole discretion of Oracle.