Software Configuration Guidelines for TIBCO Order Management - Long Running
Configure your TIBCO Order Management - Long Running components correctly to enhance your system performance. Ensure that you plan and complete the configuration in conjunction with appropriate performance testing and tuning.
Configuring components of TIBCO Order Management - Long Running essentially means determining how many instances of each type of engine must be deployed across the number of physical servers available. Also, how much physical RAM must be allocated to each engine. The product documentation provides basic recommendations for a minimal setup. For details about the setup, see "Installation and Deployment Options" in the TIBCO Order Management - Long Running Installation and Configuration guide.
Here are some recommended best practices:
- For a typical production setup containing two physical servers, use the basic starting configurations – two instances TIBCO Order Management - Long Running - Orchestrator, Automatic Order Plan Development, and Jeopardy (per server).
- Set identical minimum and maximum heap sizes.
- Set 8 GB of heap size for each TIBCO Order Management - Long Running instance.
Use Configurator to perform TIBCO Order Management - Long Running configurations.
TIBCO Order Capture System
Regarding system sizing, the number of Order Capture System 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 Order Capture System.
The same considerations apply to Order Capture System database sizing. Order Capture System only uses the database for the temporary storage of the shopping cart.