Batch Notification

Following are the notifications sent by Orchestrator:

  1. Orchestrator sends the JMS notification to the Process Component for executing, suspending, and activating the plan items. Orchestrator also needs to notify the Milestone waiting in the Process components

  2. Orchestrator also publishes notifications for the state changes of entities such as Order, Order Line, Order Amendment, Plan, and Plan Item. Third party applications can listen to these notifications.

The Orchestrator needs to execute the actions triggered by the state change. The actions are configured internally to dispatch the JMS Messages, process Database notifications and logging. These actions are executed in batches using the batch processor.

Batch threads are configured to run in the Orchestrator. Batch Threads execute the actions with each thread dedicated to a group of orders and batch worker queue. The user can configure the number of batch threads (com.tibco.fom.orch.batchProcessorsCnt) and the maximum size (com.tibco.fom.orch.maxBatchSize) of the batch to process per thread, depending on the load. Actions generated by order events are posted to the Batch Queue and are processed in the sequence that was sent to Batch queue. Batch threads groups the action execute requests and executes them in batch.