Monday, November 5, 2012

Technical Architecture of Oracle Applications R12

Oracle Applications R12 architecture is a framework for multitiered, distributed computing that supports Oracle Applications Products.

In this type of architecture various servers or services are distributed among three levels or tiers. 

A tier is a logical grouping of services, spread across more than one physical machine. Oracle Applications R12 is a three tier architecture therefore it consists of the following

Desktop/Client Tier -> This tier provides the user interface that could comprise of mobile devices, PC, MAC book, laptops, Desktops and among others. It's purpose is to enter information, review information and to interact with the system to perform business operations, reporting tasks.

Application Tier -> This tier is also referred to as the Middle tier and is often associated with the Application logic or where the data transformation takes place within the Application. Typically within implementation it is advised not to tamper with the code installed for a module, since if the changes are not done as specified it could lead to tampering of the application logic that supports and managed all the related modules and components. So in general proceed with caution and customize or touch code only when necessary. Oracle does not support service agreements once the code installed has been tampered with and then you might have to rely on expensive consultancy services to fix the issue.

Database Tier -> This tier supports and manages the Oracle database and is responsible for storing and retrieving application data queried by the business user. PL/SQL queries are run on the Database Tier in order to query, insert, update or delete data from the Oracle Application backend tables. Database activity could be clustered by providing a series of machines to form the Database tier.

Network -> The glue that unifies and helps transfer data from the Desktop/Client tier and the Application Tier is the Internal Networks like WAN (Wide Area Network) and the External Network (Internet, VPNs) since the exchange of information is minimal at most. Data intensive tasks can be performed more effectively on the Self Service or HTML versions of the Application that run on the Internet Browser supported by the R12 E-Business Suite.

Network can have a great impact on your system performance as even though it is the least visible the connection links themselves can vary from slow speed dial up to high speed fiber optic channels. If you are using a slow connection optimizing the Application or Database tier is not useful if the network connection is slow and not effective.

This kind of setup benefits business that run global operations since they could potentially have people sitting in different parts of the globe but still being connected on WAN/Network and therefore being able to send and receive information via the network connections.

Some of the benefits are that this requires less network traffic and helps reduce the telecommunication costs and improves response time for users.

It is suggested that the Application Tier and the Database tier are located more or less in a setup that felicitates optimal situation for data transfer as these exchanges are quite data intensive and might require additional time for processing if otherwise. 

1 comment: