This appendix contains examples of three deployment configurations:
Small (100 users)
Medium (300 to 400 users)
Large (1000 users)
The hardware proposed for each deployment size is based on the equation for calculating capacity presented in "Hardware Sizing Guidelines".
The examples presented here are based on the number of concurrent users, which is only one criteria used to determine hardware sizing. The examples are general and are intended as a learning tool. Estimates on equipment and configuration settings cannot be exact because needs vary between MetaSolv Solution installations based on issues such as the number of users, the volume of transactions, whether the application is being used on a WAN, and so on. To ensure that you have planned for the appropriate equipment and software, Oracle recommends that you contact its Professional Services Organization before you proceed with an installation.
When assessing your business situation to estimate hardware needs, you should consider a combination of factors such as API transactions and the type and number of transactions being processed, then adjust accordingly.
The following sections describe a small deployment example and include details on deployment size assumptions and hardware configuration.
Table A-1 shows the size assumptions made for this deployment example.
Table A-1 Size Assumptions for a Small Deployment
Size and Usage Requirement | Nonclustered Nonredundant Environment | Clustered Redundant Environment |
---|---|---|
Number of concurrent users |
100 |
100 |
Number of orders per day |
8,000 |
8,000 |
Circuit assignment |
700 |
700 |
Number of trouble tickets |
4,000 |
4,000 |
Reliability/availability |
98% |
99.5% |
Table A-2 shows the hardware configurations for this deployment example.
Table A-2 Example Small Deployment Hardware Configuration
Machine | Nonclustered Nonredundant Environment | Clustered Redundant Environment |
---|---|---|
Client machine (one per user) |
Windows-based machine (2.6+ GHz; 512 MB+ RAM) |
Windows-based machine (2.6+ GHz; 512 MB+ RAM) |
Administration server machine |
N/A |
You can use the WebLogic application server machine (below) to handle the administration server as well. No additional hardware is needed. |
WebLogic application server machine |
1 Sun M3000
|
2 Sun M3000
|
External load balancers |
N/A |
***2 load balancers Customer's choice Example: F5 BIG-IP LTM 3600 |
Database server (Oracle) machine |
1 Sun M3000
-- or --
|
2 Sun M3000 (Active/Passive)
-- or --
|
Background Processor machine |
1 Windows-based machine
|
2 Windows-based machines
|
*Clustering with nonredundancy does not apply here. Oracle recommends one Oracle application server per 2 CPUs.
**Only one Oracle Application Server will reside on each machine.
***Access Oracle requirements for hardware load balancer. See:
http://docs.oracle.com/cd/E12839_01/web.1111/e13709/load_balancing.htm
For a configuration example using BIG-IP LTM as hardware load balancer, see:
http://www.f5.com/pdf/deployment-guides/f5-weblogic10-dg.pdf
The following sections describe a medium deployment example, and include details on size assumptions and hardware configuration.
Table A-3 shows the size assumptions for this deployment example.
Table A-3 Size Assumptions for a Medium Deployment
Size and Usage Requirement | Clustered Nonredundant Environment | Clustered Redundant Environment |
---|---|---|
Number of concurrent users |
300-400 |
300-400 |
Number of orders per day |
30,000 |
30,000 |
Circuit assignment |
3,000 |
3,000 |
Number of trouble tickets |
16,000 |
16,000 |
Reliability/availability |
99.5% |
99.9% |
Table A-4 shows the hardware configurations for this deployment example.
Table A-4 Example Medium Deployment Hardware Configuration
Machine | Clustered Nonredundant Environment | Clustered Redundant Environment |
---|---|---|
Client machine (one per user) |
Windows-based machine (2.6+ GHz; 512 MB+ RAM) |
Windows-based machine (2.6+ GHz; 512 MB+ RAM) |
Administration server machine |
N/A |
You can use the WebLogic application server machine (below) to handle the administration server as well. No additional hardware is needed. |
WebLogic application server machine |
1 Sun M3000
|
2 Sun M3000
|
External load balancers |
*** 1 load balancer Customer's choice Example: F5 BIG-IP LTM 3600 |
***2 load balancers Customer's choice Example: F5 BIG-IP LTM 3600 |
Database server (Oracle) machine |
1 Sun M3000
-- or --
|
2 Sun M3000 (Active/Passive)
-- or --
|
Background Processor machine |
1 Windows-based machine
|
2 Windows-based machines
|
*For better performance and reliability, a clustered environment is recommended for medium-sized customers.
**The recommendation is for four Oracle application server processes to run on each machine.
***Access Oracle requirements for hardware load balancer. See:
http://docs.oracle.com/cd/E12839_01/web.1111/e13709/load_balancing.htm
For a configuration example using BIG-IP LTM as hardware load balancer, see:
http://www.f5.com/pdf/deployment-guides/f5-weblogic10-dg.pdf
The following sections describe a large deployment example, and include details on size assumptions and hardware configuration.
Table A-5 shows the size assumptions for this deployment example.
Table A-5 Size Assumptions for a Large Deployment
Size and Usage Requirement | Clustered Nonredundant Environment | Clustered Redundant Environment |
---|---|---|
Number of concurrent users |
1,000 |
1,000 |
Number of orders per day |
100,000 |
100,000 |
Circuit assignment |
7,200 |
7,200 |
Number of trouble tickets |
42,000 |
42,000 |
Reliability/availability |
99.5% |
99.9% |
Table A-6 shows the hardware configurations for this deployment example.
Table A-6 Example Large Deployment Hardware Configuration
Machine | Clustered Nonredundant Environment | Clustered Redundant Environment |
---|---|---|
Client machine (one per user) |
Windows-based machine (2.6+ GHz; 512 MB+ RAM) |
Windows-based machine (2.6+ GHz; 512 MB+ RAM) |
Administration server machine |
N/A |
You can use the WebLogic application server machine (below) to handle the administration server as well. No additional hardware is needed. |
WebLogic application server machine |
1 Sun M4000
|
2 Sun M4000
|
External load balancers |
***1 load balancer Customer's choice Example: F5 BIG-IP LTM 3600 |
***2 load balancers Customer's choice Example: F5 BIG-IP LTM 3600 |
Database server (Oracle) machine |
1 Sun M4000
-- or --
|
2 Sun M4000 (Active/Passive)
-- or --
|
Background Processor machine |
1 Windows-based machine
|
2 Windows-based machines
|
*For better performance and reliability, a clustered environment is recommended for large-sized customers.
**The recommendation is for eight Oracle application server processes to run on each machine.
***Access Oracle requirements for hardware load balancer. See:
http://docs.oracle.com/cd/E12839_01/web.1111/e13709/load_balancing.htm
For a configuration example using BIG-IP LTM as hardware load balancer, see:
http://www.f5.com/pdf/deployment-guides/f5-weblogic10-dg.pdf