Software Configuration Guidelines for FOM
Configure your TIBCO Fulfillment Order Management components correctly to enhance your system performance. Make sure you plan and complete the configuration in conjunction with appropriate performance testing and tuning.
Configuring components of TIBCO Fulfillment Order Management essentially means determining how many instances of each type of engine should be deployed across the number of physical servers available. Also, how much physical RAM should be allocated to each engine. The product documentation provides basic recommendations for a minimal setup in Chapter 2, "Installation and Deployment Options" in the TIBCO Order Management Fulfillment Installation and Configuration guide.
The following best practices are recommended:
- For a typical production setup containing two physical servers, it is recommended to use the following basic starting configuration (per server):
- Set identical minimum and maximum heap sizes.
- Set 8 GB of heap size for each Fulfillment Order Management instance.
- Offer and Price Engine (OPE) is an optional engine. Set 2GB for OPE.
Use Configurator to perform TIBCO Fulfillment Order Management configurations.
TIBCO Offer and Price Engine
Memory utilization in the OPE engine is related to the size of the catalogue. TIBCO recommends sizing the memory allocation for these business engines according to the catalogue size.
TIBCO Fulfillment Order Management agents require a maximum memory allocation of 1 GB to accommodate the largest orders that the system should accept.
TIBCO Order Capture System
Regarding system sizing, the number of OCS instances and whether or not a load balancer is needed depends on the number of concurrent users, the desired availability of the system (a single node system can be unavailable in case of crash or maintenance), and the specifications of the machine hosting OCS.
Same considerations apply to OCS database sizing. OCS only uses the database for temporary storage of the shopping cart.