DSLCore Orchestrator Documentation
The DSLCore Orchestrator is a separate control-plane application. It registers the applications in a network, routes events, commands and queries between them, runs scheduled jobs, reconciles cross-system state, raises and works governance exceptions, and keeps the delivery, execution and audit history for all of it. It is not the master database for business records — every domain app keeps ownership of its own data and business logic.
This section covers the DSLCore Orchestrator application specifically. For how the interface works in general (lists, forms, navigation, deletion), see the Framework Guides above.
One application, one instance per network
The same orchestrator code runs as a separate instance for each network — its own port, its own database, its own members and routes. What you see in this app depends on the instance you opened:
| Instance | Port | Network | Traffic | Data |
|---|---|---|---|---|
orchestrator |
5050 | the exploration suite (eis / epa / elwpm) — also the live orchestrator.dslcore.net | entity sync | the demo story in the Quick Reference |
orchestrator_r9 |
5089 | work_supply — Work Management, Inventory, Purchasing, Catalogue, Supplier, SAP AP, Asset Register, Asset Lifecycle, Warranty, Assurance |
message protocol | loaded from the network's manifest; fills as the network runs |
orchestrator_work_supply |
5086 | work_supply_00 — the earlier Work & Supply demo (mwem / msam / psam / scrm + amia / cwia / psba / soim) |
entity sync | loaded from networks/work_supply_00/system.manifest.yaml |
Networks are defined under networks/<name>/ and run from the command line or the control
panel's Networks view (http://localhost:5000/networks), which also shows each network's
live message flow.
In This Section
- Application Overview — what the app models and why, the two kinds of traffic, and the boundary between the control plane and the domain apps
- Quick Reference — menu map, status vocabularies, rules of thumb, and the exploration demo's codes
- System Diagram — the data model mapped, with an interactive pan/zoom viewer
- Exploration Demo Runbook — running the exploration suite (eis / epa / elwpm) against the orchestrator and firing its four acceptance flows (entity sync)
- Message Protocol — events, commands and queries between
integration apps (the
work_supplynetwork): routing, delivery, retries, dead letters, and where to watch it
The Application in One Paragraph
The orchestrator answers one question for a network of applications — is the right information moving to the right place, on time, and can we prove it? It starts with a registry: every application instance (DSLCore, external, legacy or infrastructure) with its address and status, the connectors that know how to reach it, the shared canonical entities, which application owns each one, and the mappings between their keys. Information moves in one of two ways. Entity sync matches a received event message to route definitions, transforms the record with each route's field mappings and records a delivery attempt per target. The message protocol routes complete events, commands and queries from apps with an integration contract — to an explicit destination, an entity's owner or every matching subscription — and records a route decision, delivery attempts and the receiver's acknowledgement. Either way, deliveries that exhaust their retries land in the dead-letter queue. The scheduling engine holds action and job definitions, their schedules, the job-execution history, sync checkpoints and retry policies. Governance catches absence, inconsistency and staleness, not just events: control definitions run on a schedule, each control execution passes or fails, and a failure raises a governance exception worked through Open → Acknowledged → Investigating → Remediation → Resolved → Verified → Closed — where Verified means the originating control was rerun and passed. Health checks track liveness and an audit record trail records who did what. Delivery is at-least-once and every receiver is idempotent; secrets are only ever referenced, never stored.