Hardware Sizing Guidelines
You need to consider certain non-functional requirements when designing infrastructure topography. You also need to follow specific guidelines before making hardware recommendations to a customer.
An example of a non-functional requirement involves putting logging and operational Enterprise Message Service (EMS) traffic on the same EMS instance. However, this leads to delays in processing orders because the orders are blocked by non-business critical logging traffic. A better solution is to create separate EMS instances for logging and core EMS traffic to eliminate this blockage.
Hardware sizing is generally an outcome from preliminary performance testing. All environments are different, and you cannot use a cookbook approach to a particular order management problem. TIBCO recommends completing extensive performance testing on lab hardware before recommending particular hardware to a customer. These lab runs should reflect a realistic order size and load mix, as well as an anticipated plan size. The plan should also cover pre-submit and post-submit activities, in particular, validation and eligibility calls to Offer and Price Engine (OPE).