Oracle’s E-Business Suite (also known as Applications/Apps or EB-Suite/EBS) consists of a collection of enterprise resource planning (ERP), customer relationship management (CRM), and supply-chain management (SCM) computer applications Oracle applications is the widely used EBS application in the world.Oracle’s E-Business Suite requires extensive work from Oracle Application Database Administrator(Oracle apps DBA). So Oracle Application Database Administrator is a rewarding career with great potential to scale new heights.it demands great responsibility and thorough knowledge of the system. Applications DBA should have a clear understanding of the concepts, architecture and internals to be able to do the job effectively
I am presenting here the Online oracle apps technical training Course to equip the Oracle apps DBA with various training material, how to tips and various trouble shooting tips. I will be presenting this in Parts.
Here is Online oracle apps technical training Course Part 1 . Here I will giving the notes on Architecture on Oracle E-Business Suite 11i, R12.1.3/12.2.X
Introduction to Oracle E-Business Suite 11i, R12.1.3/12.2.5
Oracle apps is a bundle of Ebuisness applications that provide complete solution to the business need of the Oracle customers.
Oracle applications utilizes a three tier architecture
The three tier are Database Tier, Application tier and Desktop Tier. The distributed architecture shifts software administration from the desktop onto the middle, or application tier, thus reducing client-side maintenance and lowering administration costs.
What is Desktop Tier:
The client interface is provided through HTML for HTML based application and via a Java applet in a Web browser for the traditional Forms-based applications. The desktop client with Oracle JInitiator/JRE downloads the applet on demand and the applet is cached locally for future use.
Self Service Application
The Self-Service Web Applications architecture consists of the following components Web browser,The Oracle HTTP server,Java Server Pages, JavaBeans and Servlets
An HTML-based Applications module uses the following access path:
The user clicks the hyperlink of a function from a browser.
The browser makes a URL request to the Web listener.
The Web listener contacts the Servlet engine (OC4J), where it runs a JSP.
The JSP obtains the content from the Oracle E-Business Suite tables and uses information from the metadata dictionary to construct the HTML page.
The resulting HTML page is passed back to the browser, via the Web server.
Forms Based Application
It consists of two part Forms client Applet and Oracle Jinitiater/JRE
Forms Client Applet
The Forms client applet is a general-purpose presentation applet that supports all Oracle Applications products, including those with customizations and extensions. The Forms client applet is packaged as Java archive (JAR) files. The JAR files contain all Java classes typically required to run Oracle Applications forms.
The Forms client applet displays Oracle Applications screens and supports field-level validation, multiple coordinated windows, and data entry aids like lists of values. The Forms client applet sends user requests to the Forms server and handles responses from the Forms server such as screen updates and pop-up lists.
The required and commonly used JAR files are downloaded from the Web server at the beginning of the client’s first session. Afterwards the JAR files remain in the browser’s local disk cache, ready for future sessions until updated versions are released. All updates are installed on the application tier and downloaded to the client automatically through the use of the JInitiator/JRE-enabled Web browser. Other less commonly used JAR files are downloaded on demand, or as needed.
The Forms client applet must run within a Java Virtual Machine (JVM) on the desktop. For Oracle Applications the JVM is supplied by Oracle JInitiator/JRE . Oracle JInitiator/JRE works in conjunction with the Web browser.
Oracle JInitiator/JRE is implemented on the desktop client as ActiveX component (Microsoft Internet Explorer).
When an end user enters the desired Oracle Applications signon URL within the Web browser, Oracle JInitiator/JRE is executed. If Oracle JInitiator has not been installed, the Web browser prompts you to download the necessary installation executable to the desktop client.
Once installed, Oracle JInitiator/JRE runs the Forms client applet and starts an Oracle Applications session.
The Application Tier is the location of servers that provide the business logic and code processing. This tier is sometimes referred to as the middle tier. Each Application release has different technology components in Middle Tier
Here are the main parts in Middle Toer
The Web Server
The Forms Server
The Concurrent Processing Server
The Reports Server( This is present in R11i only)
The Admin Server ( This is present in R11i only)
This tier provides the communication between the desktop tier and the database tier. The application tier also supports load balancing among multiple forms servers to provide optimal scalability and processing.
R11i Middle Tier Architecture
R11i Middle Tier consists of Apache, Jserv, Forms 6i and concurrent Processing server
Application Server: iAS188.8.131.52.2
Servlet Container: JServ
Forms & Reports: 6i
Java/JDK: 1.4.2 -> 1.5
R12.0/R12.1 Middle Tier Architecture
Servlet Container: OC4J
Forms & Reports: 10g(10.1.2)
We have two 10g Oracle Home.
R12.2 Middle Tier Architecture
Application Server: 11gR1 Fusion Middle ware
Servlet Container: Oracle Web logic Server
Forms & Reports: 10.1.2
All the Middle Tier technologies working can be understood from the below articles
The database tier contains the Oracle database server that stores and manages all the data maintained by Oracle E-Business Suite. This includes the various types of file in which the tables, indexes, and other database objects for your system physically reside, as well as the database executables.
The database server communicates with the services and servers on the application tier, which mediate the communications between the database and the clients. There is no direct communication between the database and clients.
Related Posts for EBS Architecture
Next Training Post