Recommended Setup for a TIBCO Order Management - Low Latency Development Environment
The following details are the recommended setup for a TIBCO Order Management - Low Latency Development environment:
| Component | Instances |
|---|---|
| Orchestrator | Multiple |
| Automated Order Plan Development | Multiple |
| Configurator | 1 |
| Configuration service | 1 |
| Authorization service | 1 |
| Data service | Multiple |
| Catalog service | Multiple |
| tmf-om-adapter | 1 |
| Redis Cluster | Multiple |
| Postgresql | 1 |
Hardware
8 GB of heap size is set for each instances. For orchestrator – 4 GB, for Automated Order Plan Development – 4 GB, for Data Service – 2 GB, and for Authentication – 2GB memory is allocated.
Disk Space
Redis in-memory is used for TIBCO Order Management Services. For collecting 10 instances, 10 GB memory on disk is used. For 100,000 orders on 10 nodes, it takes up to 218 MB for each node.
Temporary Disk Space for UNIX Platform
The installer launcher first extracts a Java Virtual Machine (JVM) in a temporary directory and uses this JVM to launch itself. The size of the extracted JVM differs from platform to platform.
On UNIX platforms, the following disk space is required in the temporary area:
256 MB of free disk space in /tmp location.
If your system does not have sufficient free disk space in the above temporary area, you can still run the installer with a different temporary area by using the following option when starting the installer:
install_package_name.bin -is:tempdir /new_tmp where /new_tmp has sufficient free disk space.