Micro-Services

Each TIBCO Fulfillment Order Management component, or micro-service with the new architecture, has its own embedded Tomcat container. The roles folder available in the $AF_HOME directory houses all the micro-services.

There are six micro-services for TIBCO Fulfillment Order Management:
Micro-Service Description Default Port
configurator Micro-service for Configurator. 9090
omsserver
Note: By default, OMS runs AOPD in colocated mode and OPE in standalone mode.
Micro-service for the OMS server. 9091
omsui Micro-service for the OMS UI. 9092
aopd
Note: By default, this service runs AOPD in standalone mode.
Micro-service for AOPD. 9093
ope
Note: By default, this service runs OPE in standalone mode.
Micro-service for OPE. 9094
ocs Micro-service for OCS. 9095
Each micro-service under the $AF_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 own set of configuration files. Initially, each service has the following files:
    • application.properties
    • configDBrepo.properties
    • profiles.properties (except for Configurator and OCS)

    When the service starts, it will download 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 OCS and OMS UI, have extra directories for the UI.