Recommended Setup for a TIBCO Order Management - Long Running Development Environment
The following details are the recommended setup for a TIBCO Order Management - Long Running Development environment:
Component | Type | Instances | Primary Server | Memory |
---|---|---|---|---|
Order Management Server (Automated Order Plan Development + Orchestrator + Jeopardy Management System + UI) | Java | 1 | M1 | 4 GB |
Oracle | Database | 1 | M2 | 8 GB |
TIBCO Enterprise Message Service | Messaging | 1 | M1 | Default |
Process Component (TIBCO BusinessWorks, TIBCO BusinessWorks Container Edition, or TIBCO BusinessEvent) | Java | 1 | M1 | 2 GB |
Disk Space
To install TIBCO Order Management - Long Running and all the prerequisite software, a disk space of 10 GB is required on machine M1. An additional space of 10 GB is required on M2 for Oracle software and tablespaces. The Oracle tablespace created might be at least 100 MB.
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.
Jeopardy Deployment Configuration
In the collocated mode, jeopardy deployment is a single instance or multiple instance cluster setups. Deploy it with the following configuration:
- Local and TIBCO ActiveSpaces® data store are not supported in this version.
- If Jeopardy is enabled, which means that the Jeopardy Management System deploy mode is set to JEOMS_colocated, every TIBCO Order Management - Long Running cluster instance has to run Jeopardy Management System in the collocated mode. This means that if some server instances are set to JEOMS_disabled and some server instances are set to JEOMS_colocated, such configurations are not supported.