During runtime, the retrieval, transformation, and routing of documents occurs based on a defined business process. See Runtime Flow Diagram for a visual model of the runtime process.
When an inbound event is captured, it is processed immediately in non-persist mode if the process does not expect multiple events. If additional correlated events might be received by the same business process, the captured event is processed in persist mode and then routed to the specified business process. For additional information about persist and non-persist modes, see Transactionality and Errored Business Processes.
If the event is an initializer event, Unwired Orchestrator begins a new instance of the business process. The data that either flows through or is created in the business process is dispatched to external resources defined in a service interaction. Using the schema defined in the service interaction, the engine serializes the data into the format expected by that resource and sends it to the target.
The Command and Control interface provides the ability to control server functions and manage business processes. Using Command and Control, the server can be stopped, started, and queried to determine its current state. The Server Instance Management Monitoring interface allows users to view and manage business processes for a runtime instance. Each instance can be queried to return processes of a specified state or processes of a specified type. Errored business processes can be recovered or removed.