[293] in SAPr3-news
Re: R3 - Centralized vs Separate?
daemon@ATHENA.MIT.EDU (Thomas Kohaut)
Mon Jul 3 18:47:10 1995
To: sapr3-news@MIT.EDU
Date: Tue, 4 Jul 1995 00:17:17 (MET)
From: 100.5858@GermanyNET.de (Thomas Kohaut)
In article 3t1qpn$jut$1@mhafc.production.compuserve.com,
Mark Minyard <76050.1516@CompuServe.COM> writes:
> I am wondering how companies run R3 that are geographically
> dispersed? Is it more common to run R3 at each site or have only
> one central computer(s) with remote sites connected with a WAN?
> If running multiple R3 systems, how do they share information?
> What are the pros/cons of each strategy? I am wondering if
> anyone has any info to share.
>
> Thanks, Mark
There are two solutions:
1. You use exact one r/3 system with one or more r/3 instances.
In this case, you need a central db-server. The r/3 instances
are communicating about the central SAP R/3 Message Server.
2. You use two or more R/3 (or R/2) systems. These systems
communicate about the SAP Gateway.
If possible, solution one is used. The benefits are:
- all changes are 'just in time'
- no individual programming of distribution and consolidation
is necessary
Solution two is only used, if a single db-server isn`t fast
enough. In this case, different parts are distributed on
different r/3 systems. The data is consolidated asynchron
about the SAP-Gateway. The distribution and consolidation
is individual programming!
---
100.5858@GermanyNET.de is Thomas Kohaut from 60529 Frankfurt
