Recommended Setup for a Fulfillment Order Management Development Environment

The following details are the recommended setup for a Fulfillment Order Management Development Environment:

Component Type Instances Primary Server Memory
OMS (AOPD + Orchestrator + JeOMS + UI) Java 1 M1 4 GB
Oracle Database 1 M2 8 GB
TIBCO EMS Messaging 1 M1 Default
Process Component (TIBCO BusinessWorks or TIBCO BusinessEvent) Java 1 M1 2 GB
OPE Java 1 M1 2 GB

Hardware

The recommended configuration for M1 and M2 are 8 core CPU @ 2 GHz with 16 GB RAM.

Disk Space

To install TIBCO Fulfillment Order Management 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 table spaces. The Oracle table space created should 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 colocated mode, jeopardy deployment is a single instance or multiple instance cluster setups. Deploy it with the following configuration:

Fields Colocated configurations
Profiles.properties com.tibco.fom.jeoms.deployMode = JEOMS_colocated
ConfigValues_JeOMS.xml Operational Datastore = cache
Note:
  • Local and ActiveSpace data store is not supported in this version.
  • If Jeopardy is enabled, which means that the JeOMS deploy mode is set to JEOMS_colocated, every TIBCO Fulfillment Order Management cluster instance has to run JeOMS in the colocated 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.