OMS Server Deployment

The functionality and interfaces of the default Java based Orchestrator component are enabled only through the colocated deployment with omsServer which is the default mode. Orchestrator cannot be deployed in a standalone mode like AOPD because there is no separate web application archive (.war) file for it. However, the Orchestrator component can be disabled on the deployment of omsServer by changing the configuration in the $AF_HOME/roles/omsServer/standalone/config/profiles.properties file.

To start and stop Orchestrator, use the following scripts:

  • To start: $AF_HOME/roles/omsServer/standalone/bin/start.sh (for Unix) or start.ps1 (for Windows)
  • To stop: $AF_HOME/roles/omsServer/standalone/bin/stop.sh (for Unix)
Note: Starting with Fulfillment Order Management 2.1.0, there is no need for ant scripts or TIBCO Administrator to start or stop Orchestrator.