To create specific sizing proposals for your hardware with assistance from your hardware partner
Solution landscape plan
1. Do initial hardware sizing separately for each system, such as the development system, the quality assurance system, and the production system. Size other systems separately, such as template systems in a global environment, administration station and clients for mobile scenarios, or Web server for Internet scenarios.
2. Determine how many applications go live at the same time.
3.
Determine the requirements
for backup, recovery, and reset of the different systems.
Consider the following:
- What hardware platform will you use later for quality assurance and for your production system?
- Is a sandbox system or technical experimentation system needed?
- What language and time zone dependencies do you need to consider regarding the development system?
- What software development projects of your own do you intend to carry out in the future?
- What enhancements do you plan to make to the standard SAP system?
- What development system growth do you expect?
- What time window will you allow for a data backup in the future?
- What time window do you expect for system recovery in the future?
- How will you organize data backup in the SAP system in the future?
- What SAP interfaces will you have to use or administer in the future?
- Are you planning to use a high availability solution or split mirror technology?
- Mobile scenarios: Perform initial hardware sizing for middleware server, mobile clients, and administration station, considering data distribution and network environment.
- Internet scenarios: Perform initial hardware sizing for middleware, considering expected network traffic for each additional type of system you plan to use (such as Web server or firewall).
Specific sizing proposals for your hardware
Sizing the initial systems is the first concrete work you will do in collaboration with your hardware partner. Make it a test of the conditions you have agreed to.