Skip to main content
Version: 3.2

2.5 Workers

Workers are standalone services that DCH offloads specific processing tasks to, keeping that work outside the core application. Each Worker is one service of a particular type, and DCH picks the right worker automatically whenever a task of that type comes up.

DCH uses these worker types:

  • Expression: evaluates expressions, including composite business keys and expression-based property mappings.
  • RuleTransformation: runs the rule-transformation step in Workflows.
  • FileExtraction: extracts data from files.
  • LinkedDataSecurity: enforces Graph Access Rules.
  • AiContext: builds context from the graph for the M4AI features.

You register a Worker by pointing DCH at its URL; DCH then reads the worker's type from the service itself, so you do not choose it. Most workers are set up once and then run in the background. The one place you usually pick a specific worker yourself is the Workflows rule-transformation step.

Manage workers from the Workers section in the sidebar. The list shows each worker's title, description, URL, type, and when it was last modified.

The Workers list, showing each worker's URL and type

Register a Worker​

note

The workers that ship with DCH register themselves automatically when they start up, so you usually do not add one by hand. Register a worker manually only when it does not self-register.

To register a worker manually, choose Add New and fill in:

  • Title: a name for the worker.
  • Description (optional): a short description.
  • URL: the worker service's base address.
  • Endpoint (optional): the path on the worker that DCH calls. Only the RuleTransformation worker currently uses it.
  • Active: whether the worker is available for use. On by default.

Choose Save. DCH reads the worker's Type from the service, so the type is filled in for you.

caution

The worker must be running and reachable when you register it. DCH asks it for its type and details, and if that call fails the worker is not saved. Each worker's title and URL must be unique.

Active and inactive​

The Active toggle controls whether a worker is used. DCH runs each task on the active worker of the matching type:

  • Active: the worker is available and can process its tasks.
  • Inactive: the worker is skipped and processes nothing, without being deleted.

DCH expects one active worker per type, so turning a worker off is a way to disable a capability, or swap in a different worker, without removing it.

A worker's detail panel, showing its Active toggle, URL, endpoint and type

Delete a worker​

Open a worker and choose Delete worker, then confirm.

note

Workers use DCH's single sign-on, so they share the same login and authorization as the rest of DCH, and each worker must be covered by a valid license.