Internet Computing Architecture
Internet Computing Architecture is a framework for three-tiered, distributed computing that supports Oracle Applications products. Internet Computing Architecture distributes services among as many nodes on a network as are required to support the processing load. Each node is a machine on the network. Services are processes that run in the background, listening for requests and process these requests.
The below three tiers are the database tier, which manages Oracle database; the application tier, which manages Oracle Applications and other tools; and the desktop tier, which provides the user interface display. With the Internet Computing Architecture, only the presentation layer of Oracle Applications is on the desktop tier in the form of a plug-in to a standard Internet browser.
Forms-based Products
Desktop Tier ===> Browser running Jinititator, a Java plug-in ===>HTTP Server ( Apache HTTP Server) ===> Forms Server===> Data Server
Forms Server===>Forms Client running in the same browser
Desktop Tier -- Java enabled Web browser. The components required on the desktop tier are the Forms Client Applet and Oracle JInitiator.
Forms Client Applet -- 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.
Oracle Jinitiator -- 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.
The Forms server mediates between the Forms client, a Java applet running on the desktop, and the Oracle database server on the back end. The Forms server produces the effects a user sees on the desktop screen and causes changes to database records based on user action. The forms client can display any Oracle Applications screen A Java-enabled We browser manages the downloading , start-up, and execution of the Forms client on the desktop. HTTP server helps start a client session over the internal or external Web.
HTML-based products ( Self-Service Web Applications)
http://aaserver01.us.oracle.com:8585/OA_HTML/ApplLocalLogin.jsp
SSWA provide a fast and cost-effective way to get information to and from people within an organization or business. SSWA doesn't use the Forms server as the application tier software or the Forms client on the desktop, but rely on HTTP-based servers on the application tier and a Java-enabled Web browser on the desktop. SSWA interface is familiar to Web users, easy to work with, and doesn't require any training.
Oracle Workflow automatically enforce business rules and policies and to provide a common notification system. ( Show an example here ) --> login to SSWA to do a internal order or expense report.
Most Oracle SSWA and Oracle WF are designed in HTML-based tools such as HTML, XML, and JavaScript. They operate by direct connection to the Apache HTTP server. Logic is controlled through stored procedures executed by the PL/SL cartridge and by Java servlets and JavaServer Pages (JSP) executed by the Apache JServ module. Apache communicates with the database using JDBC ( Java Data Base Connectivity)
Relationship between Oracle Applications and Oracle Server
Oracle Applications is built on top of Oracle Database. However, when we talk about Oracle Database and Oracle Applications, we should also have an understanding from two sides. Terminology is different, the elements usage and maintenance is also different. The below table shows the key factors inside database and applications.
DATABASE | APPLICATIONS |
RDBMS 9.2.0.1.0 | Application 11.5.10 |
DB_NAME ( ORACLE_SID ) | TWO_TASK |
Oracle_Home ( 8.1.7, 9.1.0.1 ...) | Always 8.0.6 Oracle_Home ( split configuration allows Applications to use the Oracle Developer 6i tools built technology stack with the Oracle 8 database libraries, and to use the advanced features of the Oracle 8i database ) |
Database Owner | APPL_TOP Owner |
Database Host ( one for primary DB, up to 8 hosts for physical standby or logical standby ) | Middle Tier Hosts ( Forms Server, Web Server, Concurrent Manager, Administration Server for adpatch ) |
Database Environment File ( normally one environment file ) | Applications Environment File ( more than 10 environment file, such as APPLSYS.env, appsweb.cfg, adovars.env and so on ) |
Key Variables -- $PATH, $ORACLE_SID, $ORACLE_HOME, $TNS_ADMIN and so on | Key Variables are much much more !! -- $PATH, $APPL_TOP, $TWO_TASK, $LD_LIBRARY_PATH, $CLASSPATH, $OA_JRE_TOP, $<all_product>_TOP and so on |
Database Executables ( $ORACLE_HOME/bin, such as sqlplus, exp, imp, nid, orapwd, sqlldr, lsnrctl and so on ) | Applications Executables ( $FND_TOP/bin or $<Product_Top>/bin, such as f60webmx, ar60run, startmgr, FNDCRM, FNDLOAD and so on ) |
Database Up Means " Database is running and listener is up " | Environment is Up means " Database is up, Sqlplus works, forms server, webserver and concurrent manager are all up " |
Database users such as system, sys and so on (created by using sqlplus ). A DB user may not be a product schema. | 1. APPS & APPLSYS schema |
Change DB users password by using sql statement "alter user xx identified by xx" . | 1.Change APPS, APPLSYS and all product schemas' password by using utility FNDCPASS ( using "alter user..." statement will screw up the whole environment ) |
DB Performance Tuning ( server, memory, parameters, SQL tuning and so on ) | Environment Performance Tuning ( middle tier distribution, concurrent manager definition and so on ) |
DB cold backup, regular hot backup, RMAN backup, export | File System backup ( copy command or tar command ) |
If DB is crashed, applications must not be accessible | If Applications is crashed, DB might be still good |
Oracle Applications Product Schemas
Oracle Applications cover almost 200 product, such as Financial products ( GL, AR, AP, FA and so on ), Human Resources products ( PER, PAY, and so on) . In general, for each product there is a corresponding schema that stores that product's data objects.
GL Schema includes hundreds and thousands objects for GL, such as table GL_BALANCES, GL_JE_LINES ...
AR Schema includes hundreds and thousands objects for AR, such as table AR_INVOICES.
Use of the APPS Schema
Oracle Applications are tightly integrated. A procedure in one schema ( product) may access data in another schema (product ) and call a function in a third schema ( product). To accomplish this, the procedure needs access to all three schemas, but maintaining the access rights to all three is time-consuming and error prone (you have to specify schema for each objects such as gl.gl_balances, ar.ar_invoices). Using the APPS schema solves this problem Each product's schema grants full privileges to the APPS schema. The APPS schema has synonyms to all base product tables and sequences. The APPS schema, therefore, has access to all Oracle Applications data.
Additional Schemas
The data objects for some products are combined within a single database account and schema. For example, tables for the Human Resources products ( PER, PAY and so on ) are combined under the database account and schema HR; tables for the Business Productivity Layer products (AOL, AD, and so on ) are combined under the database account and schema APPLSYS. There is an additional database account, APPLSYSPUB, that is used during sign-on process and doesn't actually own any database objects.
Schemas Used During Sign-on
1) When a user starts up Oracle Applications and reaches the 'Username Password' screen they have already been connected to the database
2)The APPLSYSPUB Oracle Userid ( often referred to as the 'Gateway Userid' or GWYUID) is used for the initial connection. The APPLSYSPUB schema has read only access via views to certain objects in the APPLSYS schema such as FND_USERS and FND_RESPONSIBILITIES.
3)once the User has entered a valid Username/Password combination and, if required, selected a Responsibility the User is automatically re-connected to the APPS schemas
4) The APPS schema owns all the code objects required by the user when navigating around and using Oracle Applications and Self-Service Web Applications and also has full access to all the product related schemas such as GL for General Ledger.
Oracle Applications product families and their members
The applications that make up Oracle Applications are grouped into product families. Each product family includes some products:
Oracle Financial Family :
Oracle Application Report Generator ( RG )
Oracle Assets ( FA )
Oracle Cash Management ( CE )
Oracle General Ledger ( GL )
Oracle Payable ( AP )
Oracle Receivables (AR )
Oracle Sales Family:
Oracle Manufacture Family:
Oracle Human Rescues Family:
Oracle Distribution Family:
Application Objects Library ( AOL / FND )
The Application Object Library is a primary element of the Business Productivity Layer. The Application Object Library is a collection of programs and database tables that provide common functionality across all applications products such as Receivables, General Ledger, Fixed Assets and Inventory. Using the Application Object Library ensures that the processing of flexfields or the procedure for report submission does not vary from one application to another
No comments:
Post a Comment