Within these systems, we have clients which are a commercially and organizationally independent unit in the R/3 System, which means that it has its own data environment.
CUST: Master Configuration - Customising and Developing client
TEST: Unit testing client
QAS: Quality Assurance Client
PROD: Production (Live) Client
One tier system would have all of the above clients on the same machine. This has the advantage of using minimal hardware and requires fewer administration however there are disadvantages which include
• Global customisation will affect all clients – for example when configuring / testing the printer, it will affect all clients.
• Other clients can affect productions performance and performance is a big deal in SAP.
• Cannot test upgrade in a one tier system.
• Development immediately affects production.
Two tier system would have the production client on a separate machine to the other clients. This allows the data to be secure, performance from other clients does not affect production and development is kept separate from the production. The disadvantage is that DEV and QAS testing is carried out in the same environment and transports (Moving ABAP which is custom SAP Code from one client to another) from development immediately become active in production.
Three tier system is the recommended and most common landscape. It has the following advantages
• Production data is kept secure from other clients.
• Production performance is not affected by other clients.
• There is an independent test and QAS environment
• Transports are verified (in QAS) before they are delivered to production.
The main disadvantage of the three tier system is that it is the most expensive because of the increase in hardware requirements.
All that said, because I dont have the hardware and because I am only going to be building my environment for playing around (SAP SandBox), it will be a one tier system.
No comments:
Post a Comment