Taiwan APT OSM Sizing

THE SIZING ESTIMATES CONTAINED IN THIS DOCUMENT ARE BASED UPON THE ASSUMPTIONS OF PROPER APPLICATION CONFIGURATION AND TUNING, IN A MANNER CONSISTENT WITH BEST PRACTICES OF CGBU CONSULTING AND PERFORMANCE ENGINEERING. THIS DOCUMENT IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY AND IS NOT INTENDED TO BE, NOR SHALL IT BE CONSTRUED AS A COMMITMENT TO DELIVER ORACLE PROGRAMS OR SERVICES. THIS DOCUMENT SHALL NOT FORM THE BASIS FOR ANY TYPE OF BINDING REPRESENTATION BY ORACLE AND SHALL NOT BE CONSTRUED AS CONTAINING EXPRESS OR IMPLIED WARRANTIES OF ANY KIND. YOU UNDERSTAND THAT THE INFORMATION CONTAINED IN THIS DOCUMENT WILL NOT BE A PART OF ANY AGREEMENT FOR ORACLE PROGRAMS OR SERVICES. BUSINESS PARAMETERS AND OPERATING ENVIRONMENTS VARY SUBSTANTIALLY FROM CUSTOMER TO CUSTOMER AND AS SUCH NOT ALL FACTORS WHICH MAY IMPACT SIZING IN YOUR ENVIRONMENT MAY HAVE BEEN ACCOUNTED FOR IN THIS EXERCISE. Disclaimer

© 2011 Oracle Corporation – Proprietary and Confidential3 Sizing Parameters General InformationValueNote Peak orders per hour >10,000 Customer Provided Concurrent User >30 Customer Provided Average Tasks per Order 15 Customer Provided Order lines per Order <50 Customer Provided Maximum Task per seconds >42 Customer Provided Peak orders per hour 10,000 Customer Provided Target CPU Utilization of APP/DB server<70%Customer Provided Order retention period12 monthsCustomer Provided Orders per day100,000Assumption Miscellaneous AssumptionNote Customer already have Load balancerConfirmed with customer, load balancer is recommended for HTTP Oracle DB failover solution will be used instead of RACConfirmed with customer

© 2011 Oracle Corporation – Proprietary and Confidential4 Hardware Solution CategoryHardware SPECSolutionRemark ServerServer ModelSPARC T4-1In case of T4-1 hit maximum cores limitation, use Sun T4-2 instead for growth Chip TypeSPARC T4CPU: 8 cores, GHz, Cache:128KB L2, 4MB L3 # of Servers2Totally 4 Virtual Machines for 2 APP nodes and 2 database instances Cores Per Server2Totally 4 cores RAM per server64GBTotally 128GB RAM, in cause of low price of RAM, StorageDatabase Storage (TB)5TB APP Server Share Storage 256GBSAN storage for Application Domain / JMS Persistence store, Prefer UFS file system instead of ZFS. MiscellaneousLoad balancer Network Interface1Gb EthernetAcross application server, database server, load balancer, SAN. 1Gb Ethernet is sufficient. Link aggregation could be used to create more bandwidth.

© 2011 Oracle Corporation – Proprietary and Confidential5 Physical Host A: SPARC T4-1 Storage Area Network – RAID10 Zone (3) 1 Core, 8 Gb RAM Physical Host B: SPARC T4-1 Load balancer Deployment Diagram Legend Physical Hardware Virtual Machine-Zone Active Server Passive Server Logical component HTTP(s)Integration JMS Integration H/A solution OSM DB Instance 1 Zone (1) 1 Core, 8Gb RAM Zone (2) 1 Core, 12 Gb RAM OSM Cluster Managed Server 1 OSM Cluster Managed Server 2 OSM Cluster – Admin Server Zone (4) 1 Core, 8 Gb RAM OSM DB Instance 2 Distribute Queue Hardware Option1 – Using VM Server ModelSPARC T4-1 # of Server2 Cores per Server Used2 RAM per Server Used GB Fail over Space for Growth:6 Cores OSM Cluster

© 2011 Oracle Corporation – Proprietary and Confidential6 Zone (1) 2 Core, 16Gb RAM Scalability Options Zone (2) 2 Core, 20 Gb RAM OSM Cluster Managed Server 1 OSM Cluster Managed Server 2 Extend more cores /RAM OSM Cluster Managed Server 4 OSM Cluster Managed Server 3 OSM Cluster – Admin Server Add more servers into cluster

© 2011 Oracle Corporation – Proprietary and Confidential7 © 2009 Oracle Corporation – Proprietary and Confidential 7 Thank You