Microservices

Each TIBCO Order Management - Long Running component, or microservices with the new architecture, has its embedded Tomcat container. The roles folder available in the $OM_HOME directory houses all the microservices.

The following table lists the microservices for TIBCO Order Management - Long Running:

Microservice Description Default Port
configurator Microservice for Configurator. 9090
omsserver
Note: By default, Order Management Server runs Automated Order Plan Development in collocated mode.
Microservice for the Order Management Server. 9091
omsui Microservice for the Order Management Server UI. 9092
aopd
Note: By default, this service runs Automated Order Plan Development in standalone mode.
Microservice for Automated Order Plan Development. 9093
ocs Microservice for Order Capture System. 9095
Each microservice under the $OM_HOME/roles/<service name>/standalone directory has the following directory structure:
  • bin

    This directory contains shell and power shell scripts to start and stop the service. It also contains a copyLib script, which is a utility script that can be used to copy hibernate, JDBC, JMS and other essential dependencies.

  • config
    This directory contains the service's set of configuration files. Initially, each service has the following files:
    • application.properties
    • configDBrepo.properties
    • profiles.properties (except for Configurator and Order Capture System)

    When the service starts, it downloads its required config files from the database.

  • lib

    This directory holds all external and internal dependency jar files.

  • logs

    This directory is created when the service starts and contains all the logs for that service.

  • services

    This directory holds the service jar file, which is launched by the start script

Apart from these directories, some services like Order Capture System and Order Management Server UI, have extra directories for the UI.