Difference between MVC and 3-Tier model?

What is the difference between a Model View Controller design and a 3-tier design? I have read that the 3 tiers are independant, but that is also the case in the MVC design so are the two kind of designs not rather similar??

When I think of the 3-Tier system, doesn't necessarily mean hardware, but a separation of laters of logic, which may or may not be physically independent.
The 3 tiers are presentation, domain logic, and data source. When mapping these three layers to Model View Controller, the layers are not 1:1.
Presentation maps pretty close to the View, but Model encompases both the Data Source and the most of the Domain Logic. It includes how you get the data and what you do with it. The Controller is that part of the domain logic that determines a request-response control (progression from one view to the next, calling the model logic necessary along the way).

Similar Messages

What is the difference between ERP2004 and SAP 47 Enterprise?

Currently we have SAP 47 Enterprise with WAS 6.2. I understand ERP2004 is NW and 6.4 sp9. Can any one please let me know the major difference between ERP2004 and SAP 4.7 Enterprise ( more from abap / workflow view)?
Thanks
Swamy

From Abap point of view some of the major add-on in erp2004,netwever :
1) Development of webdynpro studio for java development for portal and iviews.
2) Major abap development uses <b>Abap object oriented</b> methodology, rathet hten old conventional Abap,i.e MVC model (Model,View,Controller) where in it uses concept of classes,interfaces,etc.
3) Advanced BSP tech using MVC model to develop web based modules
4) It is closesly integrated with web-based CRM and BW/APO

Please give the diagrams to explain the difference between MVC1 and MVC2

Please give the functional diagrams to explain the difference between MVC1 and MVC2

there is no MVC1 or MVC2, only the MVC pattern. The implementation of the MVC is fairly open-ended and there are some variations that are not named as different "versions" because each variation still has the same pattern: there is a model, there are views and there are controllers. What you list as a "feature" of MVC2 in your other post:
http://forum.java.sun.com/thread.jspa?threadID=719812&tstart=0
is merely the implementation of a front controller (becoming more popular nowadays) in stead of using multiple controllers. There is no change in pattern, only in implementation.

Difference between JSP and JSF

What is the difference between JSP and JSF?
Is it necessary to learn JSP before starting with JSF?

JSP is a view technology providing a template to write plain HTML/CSS/JS in. JSP supports Java based taglibs to generate output and/or control the page flow dynamically. A well known example is JSTL. JSP also supports access to backend data with help of EL (Expression Language).
JSF is a component based MVC framework which provides taglibs for use in JSP, the JSF core tags in <f:xxx> and the JSF HTML tags in <h:xxx>. Those tags generate HTML output and are tied to JSF component tree in the server memory so that the FacesServlet can work on them to gather request parameters, validate/convert them, update the model values (javabean properties), invoke some actions (javabean action methods) and render the response.
You can use JSF on top of either JSP or Facelets. Facelets is another view technology. JSP is ancient and has its shortcomings when JSF comes into picture. Facelets is designed with JSF in mind and much more well-suited for it and provides great templating/composition capabilities to reuse specific groups of components without the need to wrap them in another custom component (so that you don't duplicate the same code over and over, e.g. label+input+message.

What's the difference between thunderbolt and mini displayport?

I'm trying to connect my Macbook with a monitor and I'm thinking of what cable to get. I will have to connect using a (Thunderbolt to HDMI cable) or a (mini displayport to HDMI cable).
I was wondering what's the difference between Thunderbolt and mini displayport
Thanks

@bontistic: it is not true that only the Macbook Air supports Thunderbolt. All models(!) support thunderbolt: also the Macbook Pro's and Mini's. Eg.: http://www.apple.com/nl/macbookpro/features.html#thunderbolt
My Macbook Pro from 2011 already supported Thunderbolt...

Difference Between BAPI And RFC in ABAP

Hi,
i want to know difference between BAPI and RFC in SAP,
can we call SAP GUI screen from NON SAP System Using BAPI.
Reg,
Hariharan

Hi Ravishankar,
The difference is not importat while you understand the concept.
I think, RFC is the protocol for calling functions from external systems in R/3.
I understand like BAPI a series of complet functions that SAP offers you for use and model a business use.
But if I need program a function that can be called for external system i would call it RFC_NAME, because is a unique function that makes a single task.
In other words, the difference i think is about work idea more than another thing.
RFC
A remote function call is a call to a function module running in a system different from the caller's. The remote function can also be called from within the same system (as a remote call).
RFC consists of two interfaces : A calling interface for ABAP Programs and a calling interface for Non-SAP programs.
The RFC Interface takes care of :-
- Converting all parameter data to the representation needed in the remote system
Calling the communication routines needed to talk to the remote system.
Handling communications errors, and notifying the caller, if desired ( using EXCEPTIONS paramater of the CALL FUNCTION).
BAPI
BAPIs are standardized programming interfaces (methods) enabling external applications to access business processes and data in the R/3 System.
BAPIs provide stable and standardized methods to achieve seamless integration between the R/3 System and external applications, legacy systems and add-ons.
BAPIs are defined in the BOR(Business object repository) as methods of SAP business object types that carry out specific business functions.
BAPIs are implemented as RFC-enabled function modules and are created in the Function Builder of the ABAP Workbench.
The most critical difference btwn BAPI and FM is that BAPI can be wrapped in Business objects whereas RFC cant.
BAPI are RFC enabled function modules. the difference between RFc and BAPI are business objects. You create business objects and those are then registered in your BOR (Business Object Repository) which can be accessed outside the SAP system by using some other applications (Non-SAP) such as VB or JAVA. in this case u only specify the business object and its method from external system in BAPI there is no direct system call. while RFC are direct system call Some BAPIs provide basic functions and can be used for most SAP business object types. These BAPIs should be implemented the same for all business object types. Standardized BAPIs are easier to use and prevent users having to deal with a number of different BAPIs. Whenever possible, a standardized BAPI must be used in preference to an individual BAPI.
The following standardized BAPIs are provided:
Reading instances of SAP business objects
GetList ( ) With the BAPI GetList you can select a range of object key values, for example, company codes and material numbers.
The BAPI GetList() is a class method.
GetDetail() With the BAPI GetDetail() the details of an instance of a business object type are retrieved and returned to the calling program. The instance is identified via its key. The BAPI GetDetail() is an instance method. BAPIs that can create, change or delete instances of a business object type
The following BAPIs of the same object type have to be programmed so that they can be called several times within one transaction. For example, if, after sales order 1 has been created, a second sales order 2 is created in the same transaction, the second BAPI call must not affect the consistency of the sales order 2. After completing the transaction with a COMMIT WORK, both the orders are saved consistently in the database.
Create( ) and CreateFromData! ( )
The BAPIs Create() and CreateFromData() create an instance of an SAP business object type, for example, a purchase order. These BAPIs are class methods.
Change( )
The BAPI Change() changes an existing instance of an SAP business object type, for example, a purchase order. The BAPI Change () is an instance method.
Delete( ) and Undelete( ) The BAPI Delete() deletes an instance of an SAP business object type from the database or sets a deletion flag.
The BAPI Undelete() removes a deletion flag. These BAPIs are instance methods.
Cancel ( ) Unlike the BAPI Delete(), the BAPI Cancel() cancels an instance of a business object type. The instance to be cancelled remains in the database and an additional instance is created and this is the one that is actually canceled. The Cancel() BAPI is an instance method.
Add<subobject> ( ) and Remove<subobject> ( ) The BAPI Add<subobject> adds a subobject to an existing object inst! ance and the BAPI and Remove<subobject> removes a subobject from an object instance. These BAPIs are instance methods.
Check these Links out
http://searchsap.techtarget.com/ateQuestionNResponse/0,289625,sid21_cid558752_tax293481,00.html
http://www.sap-img.com/abap/interview-question-on-bapi-rfc-abap-objects-tables.htm
http://www.sap-img.com/fu033.htm
http://www.sap-img.com/abap/ale-bapi.htm
Refer following SDN threads:
Diff. Between BAPI and RFC
Re: BAPI and RFC
Hope this resolves your query.
Reward all the helpful answers.
Regards

What's the Difference Between OLAP and OLTP?

HI,
What's the difference between OLAP and OLTP ? and which one is Best?
-Arun.M.D

Hi,
The big difference when designing for OLAP versus OLTP is rooted in the basics of how the tables are going to be used. I'll discuss OLTP versus OLAP in context to the design of dimensional data warehouses. However, keep in mind there are more architectural components that make up a mature, best practices data warehouse than just the dimensional data warehouse.
Corporate Information Factory, 2nd Edition by W. H. Inmon, Claudia Imhoff, Ryan Sousa
Building the Data Warehouse, 2nd Edition by W. H. Inmon
With OLTP, the tables are designed to facilitate fast inserting, updating and deleting rows of information with each logical unit of work. The database design is highly normalized. Usually and at least to 3NF. Each logical unit of work in an online application will have a relatively small scope with regard to the number of tables that are referenced and/or updated. Also the online application itself handles the majority of the work for joining data to facilitate the screen functions. This means the user doesn't have to worry about traversing across large data relationship paths. A heavy dose of lookup/reference tables and much focus on referential integrity between foreign keys. The physical design of the database needs to take into considerations the need for inserting rows when deciding on physical space settings. A good book for getting a solid base understanding of modeling for OLTP is The Data Modeling Handbook: A Best-Practice Approach to Building Quality Data Models by Michael C. Reingruber, William W. Gregory.
Example: Let's say we have a purchase oder management system. We need to be able to take orders for our customers, and we need to be able to sell many items on each order. We need to capture the store that sold the item, the customer that bought the item (and where we need to ship things and where to bill) and we need to make sure that we pull from the valid store_items to get the correct item number, description and price. Our OLTP data model will contain a CUSTOMER_MASTER, A CUSTOMER_ADDRESS_MASTER, A STORE_MASTER, AN ITEM_MASTER, AN ITEM_PRICE_MASTER, A PURCHASE_ORDER_MASTER AND A PURCHASE_ORDER_LINE_ITEM table. Then we might have a series of M:M relationships for example. An ITEM might have a different price for specific time periods for specific stores.
With OLAP, the tables are designed to facilitate easy access to information. Today's OLAP tools make the job of developing a query very easy. However, you still want to minimize the extensiveness of the relational model in an OLAP application. Users don't have the wills and means to learn how to work through a complex maze of table relationships. So you'll design your tables with a high degree of denormalization. The most prevalent design scheme for OLAP is the Star-Schema, popularized by Ralph Kimball. The star schema has a FACT table that contains the elements of data that are used arithmatically (counting, summing, averaging, etc.) The FACT Table is surrounded by lookup tables called Dimensions. Each Dimension table provides a reference to those things that you want to analyze by. A good book to understand how to design OLAP solutions is The Data Warehouse Toolkit: Practical Techniques for Building Dimensional Data Warehouses by Ralph Kimball.
Example: let's say we want to see some key measures about purchases. We want to know how many items and the sales amount that are purchased by what kind of customer across which stores. The FACT table will contain a column for Qty-purchased and Purchase Amount. The DIMENSION tables will include the ITEM_DESC (contains the item_id & Description), the CUSTOMER_TYPE, the STORE (Store_id & store name), and TIME (contains calendar information such as the date, the month_end_date, quarter_end_date, day_of_week, etc).
Database Fundamentals > Data Warehousing and Business Intelligence with Mike Lampa
Search Advice from more than 250 TechTarget Experts
Your question may have already been answered! Browse or search more than 25,000 question and answer pairs from more than 250 TechTarget industry experts.

Difference between idoc and rfc

what is the difference between idoc and rfc? when and where it is used? when there is idoc, why rfc vice versa?

IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system.
IDocs are used for asynchronous transactions: Each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database.
Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.
IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.
An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication
layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model.
The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system
RFC
Remote Function Calls (RFC) and data exchange through IDoc message documents. RFC makes direct and synchronous calls of a program in the remote system. If the caller is an external program it will call an RFC-enabled function in R/3 and if the calling program is the R/3 system it will call an RFC-function in another R/3-system or it will call a non-R/3 program through a gateway-proxy (usually rfcexec.exe). BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
note:reward points if solution found helpfull.....
regards
chandrakanth.k

DIFFERENCE BETWEEN BAPI AND ALE

HI
COULD ANYBODY TEL ME
DIFFERENCE BETWEEN BAPI AND ALE

Hi Kalyan
ALE is a SAP specific method how to distribute data from and to SAP. It uses the asynchronous calls based on IDOC structures.
However in the distribution modell of ALE can also be used BAPIs. They will then automatically converted into IDOC structures. After creating the IDOCs they will be passed over to the receiver using the tRFC protocol.
Wheras the BAPIs are using the sRFC protocol.
fir more information please check this:
http://www.sap-img.com/abap/ale-bapi.htm
regards
Srinivas

Differences between rfc and ale/idoc.

hi ..
       will u please send the differences between rfc and ale/idoc's.

Hi,
Please reward with points if helpful................
ALE is SAP proprietary technology that enables data communications between two or more SAP R/3 systems and/or R/3 and external systems. There are three layers in ALE system: application services, distribution services, and communication services.
For communication services, ALE performs a Remote Function Call (RFC) using the port definition and RFC destination specified by the customer model. RFC is used to communicate between applications of different systems in the SAP environment includes connections between SAP systems as well as between SAP systems and non-SAP systems. Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. The RFC calls a function to be executed in a remote system.
Means of creating and operating distributed applications.
The purpose of Application Line Enabling is to guarantee a distributed, but integrated, R/3 installation. This involves business-controlled message exchange with consistent data across loosely linked SAP applications.
Application integration is achieved not via a central database, but via synchronous and asynchronous communication.
Application Link Enabling comprises the following three layers:
application services
distribution services
communication services
Two Development Models
     Distribution using BAPIs
     Distribution using Message type
The programming model "Distribution using message types" contains the definitions of message types and IDoc types and the ABAP code for processing inbound and outbound IDocs.
Defining message types and IDoc types:
If you want to create message type enhancements for master data distribution, you also have to create a new message type for each enhancement.
The ALE interface does not allow you to create different segment data for different IDoc types for the same message type.
Writing ABAP code:
         Outbound Processing
           Inbound Processing
You can find information on other ALE functions under:
                               Master Data Distribution
                              Communicating with Non-R/3 Systems
1. The Remote Function Call facility allows you to call an R/3 Function module on a remote machine.
2. To communicate between two R/3 Systems and also with an External System. External Application program also can call these function module for integration.
3. RFC or sRFC - Synchronous RFC
                 aRFC - Asynchronous RFC
                  tRFC - Transactional RFC
                  qRFC - Queued RFC (I.e. Serialization of tRFC)
Types of RFC Call
Synchronous
CALL FUNCTION Func Destination Dest
CALL FUNCTION func DESTINATION 'NONE' ...
CALL FUNCTION func DESTINATION BACK' ...
Asynchronous
CALL FUNCTION func STARTING NEW TASK taskname
PERFORMING form ON END OF TASK
RECEIVE RESULTS FROM FUNCTION func
Thanks
sivaparvathi

Can someone explain the difference between TIER_WEB and TIER_WEBDEV

Hi All,
We have two sets of values in Context file as below.
<TIER_ADWEB oa_var="s_isAdWeb">NO</TIER_ADWEB>
<TIER_ADFORMS oa_var="s_isAdForms">NO</TIER_ADFORMS>
<TIER_ADFORMSDEV oa_var="s_isAdFormsDev">NO</TIER_ADFORMSDEV>
<TIER_ADWEBDEV oa_var="s_isAdWebDev">NO</TIER_ADWEBDEV>
Could you explain the difference between
TIER_WEB and TIER_WEBDEV
and
TIER_ADFORMS and TIER_ADFORMSDEV

These values in a shared APPL_TOP system. Pl see ML Doc 745580.1 (Apply Patches in a Shared Application Tier File System Environment) for an explanation.Not necessarily in Shared APPL_TOP, even in traditional multi-node installation you will find these values in the application context file.
I never came across any document which describes the difference between TIER_WEBDEV and TIER_WEB, I just can say that these variables always have the same value.

What are the differences between inactive and active ABAP objects?

Can anybody tell me what are the differences between inactive and active ABAP objects?
In my opinion, an active object is compiled and system wide available, that means the system do not have to compile the program again before run or use the object. While An inactive object is not system wide available and every time you run an inactive object, firstly the abap runtime will have to generate a tempory runtime object and this inactive object can not seen by others.
Am I right? Can anybody kindly tell me other differences?

Hi,
"When it is inactive, it is like it would not exist at all:" no - it's like it only exists to you
"If we just saved that one means it is stored in application server not in database": no - the inactive version is also stored in the database. You can log off and log on and it will still be there, in its inactive status.
"Only active objects can be executed.": no - inactive objects can be executed by you
When you create or modify a program, it is inactive until you activate it.
With a change, there are two versions of the program stored in the database - the active version (as it was before you made your change), and the inactive version. If you attempt to run the program, you'll run the inactive version - the one with your changes. Everyone else on the system will run the active version.
In this way, you can make changes without affecting anyone else.
Once you activate your program, then the inactive version becomes the active version.
With a create, there is no active version, until you hit the activate button. This means ONLY you can run the program.
An additional benefit of this model, is that if you make a change, save it, and then change your mind without activating, you can recover the active version into the editor, using version management.
A downside is that sometimes you have to activate your change before you can test it, if it interacts with other, active, programs.
Regards,
Kumar

Looking for new laptop what are the differences between pro and air? Besides size. Does the air preform like the pro?

Looking for new laptop what are the differences between pro and air? Besides size. Does the air preform like the pro?

The NEW macbook Pro and Air are EXTREMELY close in form factor
The newest macbook Pro is essentially a larger macbook Air with Retina display and options for speed in increasing prices up to an independent graphics and quad core processor.
both Air and new Pro now have PCIe SSD and permanent RAM.
The Air is the lightweight portable form factor, fast to boot and shut down, but with longer battery life than any of the macbook pro in 13"
Now the new macbook Pro and macbook Air are extremely close in form factor and nature.
both have 802ac wifi
both have permanent RAM, no superdrive
both are slim profiles and SSD
The only real differences now are (in the most expensive Pros) faster processors and quadcore processors and top end model autonomous graphics.
....and of course the retina display
both are now "very good for travel"
Other than features the form factor of the Air and Pro are VERY close now,....so now its merely a matter of features and price more than anything.
You need an external HD regardless of what you get for backups etc. Drop into an Apple store and handle both and make your choice based on features, such as Retina or non-retina, .... both at a distance now look like the same computer.
The Pro weighs more, ....but nowhere near what it used to just a month ago on the older macbook Pros
The NEW macbook Pro is a different creature entirely than the older macbook Pro, .....the new Pro is thicker than the Air, but id frankly call the NEWEST Pro a "macbook Air with Retina display" , or
Maybe a “macbook Air PRO with Retina display”
Instead of Air VS Pro now,.....its really a smooth transition from Air to pro without comparing say, 2 different creatures, now its like contrasting a horse from a race horse.
Either one in 8gig of RAM (preferably)... the 4gig upgrade costs very little, the I7 you will notice only 15% faster on heavy applications over the I5, and NOTHING on most APPS.....I5 has longer battery life.
As you see below, the non-Retina 13" AIR is 82% of the Macbook with Retina display in resolution
there is no magical number of pixels per inch that automatically equates to Retina quality.
http://www.cultofmac.com/168509/why-you-might-be-disappointed-by-the-resolution- of-those-new-retina-display-macs-feature/
A huge internal SSD isnt a game changer for anything, you need an external HD anyway
what you WONT READ on Apple.com etc. is that the larger SSD are MUCH FASTER due to SSD density
"The 512GB Samsung SSD found in our 13-inch model offers roughly a 400MB/s increase in write speeds over the 128GB SanDisk/Marvell SSD"
http://blog.macsales.com/19008-performance-testing-not-all-2013-macbook-air-ssds -are-the-same
Here is an excellent video comparison between the 11” I5 vs. I7 2013 Macbook Air.
http://www.youtube.com/watch?v=oDqJ-on03z4
http://www.anandtech.com/show/7113/2013-macbook-air-core-i5-4250u-vs-core-i7-465 0u/2
I5 vs. I7 performance 13” Macbook Air 2013
Boot performance
11.7 I5 ……11.4 I7
Cinebench
1.1 I5….1.41 I7
IMovie Import and Opt.
6.69 I5….5.35 I7
IMovie Export
10.33 I5…8.20 I7
Final Cut Pro X
21.47 I5…17.71 I7
Adobe Lightroom 3 Export
25.8 I5….31.8 I7
Adobe Photoshop CS5 Performance
27.3 I5…22.6 I7
Reviews of the newest Retina 2013 Macbook Pro
13”
Digital Trends (13") - http://www.digitaltrends.com/laptop-...h-2013-review/
LaptopMag (13") - http://www.laptopmag.com/reviews/lap...play-2013.aspx
Engadget (13") - http://www.engadget.com/2013/10/29/m...-13-inch-2013/
The Verge (13") - http://www.theverge.com/2013/10/30/5...ay-review-2013
CNet (13") - http://www.cnet.com/laptops/apple-ma...-35831098.html
15”
The Verge (15") - http://www.theverge.com/2013/10/24/5...w-15-inch-2013
LaptopMag (15") - http://www.laptopmag.com/reviews/lap...inch-2013.aspx
TechCrunch (15") - http://techcrunch.com/2013/10/25/lat...ok-pro-review/
CNet (15") - http://www.cnet.com/apple-macbook-pro-with-retina-2013/
PC Mag (15") - http://www.pcmag.com/article2/0,2817,2426359,00.asp
Arstechnica (15") - http://arstechnica.com/apple/2013/10...-pro-reviewed/
Slashgear (15") - http://www.slashgear.com/macbook-pro...2013-26303163/

Difference between BI and BW 3.5

10 basic difference between BI and BW 3.5

Hi the following documentation will be helpful to you,
Regards,
SUbha
Pls grant me points if helpful
This documentation provides you with a starting point for administration and optimal maintenance of the Enterprise Data Warehousing IT scenario. It contains business-intelligence-specific information for various tasks, lists the relevant tools and functions, and provides links to the more detailed documentation that you need to carry out the tasks.
The Enterprise Data Warehousing IT scenario supports you in setting up and managing a data warehouse in a company-wide environment. It allows you to integrate, transform, consolidate, clean up, store, and stage data of any origin (SAP and non-SAP sources), or age (historic and up-to-date), to be analyzed and interpreted. It provides flexible structures and layers so that you can react quickly to business developments. It also allows businesses to report in real time and improve the design time and runtime of BI models and processes.
For more information, see Enterprise Data Warehousing.
Administration of this IT scenario is part of the Running the Enterprise Data Warehouse scenario variant. Therefore the tasks described below refer to this scenario variant.
Integration
Enterprise Data Warehousing provides data for the following IT scenarios:
IT Scenario
Description
Information About IT Scenario Administration
Enterprise Reporting, Query and Analysis
This IT scenario shows how business experts can use the reporting and analysis tools available in SAP NetWeaver Business Intelligence (BI) to provide BI information customized for the different categories of user within your company.
Enterprise Reporting, Query, and Analysis
Business Planning and Analytical Services
This IT scenario includes processes that collect data from InfoProviders, queries, or other BI objects, convert them using various methods, and write back new information to BI objects (such as InfoObjects or DataStore objects).
Business Planning and Analytical Services
Tasks
In most cases, running an enterprise data warehouse involves general tasks for managing the Application Server for ABAP (AS ABAP) and the Application Server for Java (AS Java), as well as scenario-specific tasks. For more information, see:
●     AS ABAP (Application Server for ABAP)
●     AS Java (Application Server for Java)
●     Enterprise Data Warehousing: Preparation for EDW Processes
●     Enterprise Data Warehousing: Tasks Performed Regularly
●     Enterprise Data Warehousing: Tasks on Demand
●     Enterprise Data Warehousing: Saving and Recovering Data
For information about the general administration of BI systems, see BI (Business Intelligence).

Can you tell me some differences between R2 and R3 systems?

Hi,
Can you tell me some differences between R2 and R3 systems?
I guess R2 is used only for mainframe systems some time back. But i dont know why we prefered R3 over R2.
Please clarify this!
Thanks,
Venkatesh.R.

SAP R/3 is
Client server
3 tier
Presentation
Application
Database
Relatively hardware and database independent
ABAP/4 applications runs on application servers.
Dispatcher, shared memory, gateway, work processes are major components of an application server.
SAP R/3 offers
Comprehensive suite of integrated applications meeting the needs of most business
Best practice process design
Ability to configure to
Industry sector
Unique business requirements
In a R/2 System - it is a 2 Tier System based on Mainframe Systems with Intelligent terminals
R/3 is based 3 tier Client Server architechture and supports the R/2 system as well.
R/3 Middleware -
Client server
Uses underlying relational databases
Oracle
SQL server
Ingress
Sybase
Its graphical user interface
Sap GUI
hence R/3 is preffered over R/2 systems because they support Client Server Architecture which is easily configurable,scalable and can integrate with ERP systems and integrate with SOA or Web based Apps.
Thanks,
Saurabh Shukla

Difference between MVC and 3-Tier model?

Similar Messages

Maybe you are looking for