Software Configuration Guidelines for TIBCO Order Management

Configure your TIBCO Order Management 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 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 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 of TIBCO Order Management Configuration Service, Catalog Services, Orchestrator, Automatic Order Plan Development, and Process Component (per server).
• FTL Notification (True/False) - Amazon Web Services c4.4xlarge instance to set up FTL notification.
• Test Client - Amazon Web Services c4.2xlarge instance having Apache JMeter 5.2.1 test client for order injection purpose.
• Set identical minimum and maximum heap sizes across the services and instances.
• Set up an Amazon Web Services instance of type c4.4xlarge (default comes with 16 vCPU's and 30 GB memory) for each Order Management instance.
• For Orchestrator, 8 GB memory is allocated. It consumes up to 5.5 GB memory when 10,00,000 orders (with 3, 6, or 9 plan items) are submitted.
• For Automated Order Plan Development, 4 GB memory is allocated. It consumes up to 2.6 GB memory when 1000,000 orders are submitted.
• For Process Component, 4 GB memory is allocated. It consumes up to 2.5 GB memory when 10,00,000 orders are submitted.
• For Configurator, Configuration-Service and Catalog-Services, 1 GB memory is allocated by default.