Skip to content

Fortified IDDocs

Node

Deploy and manage application modules with the Node module.

The Node module deploys and undeploys a group of modules to form an application. It is the bootstrap module and is not itself deployed from the modules array.

The module reads modules and optional deployment settings from its configuration. The deployment order defaults to first, system, authn, default, last.

NameDescriptionDefaultMandatory
modulesModules to deploy. Each module defines its own name, enabled state, group and configuration.[]
groupsLegacy/top-level deployment group order. The server.deployment.groups setting takes precedence when present.["first", "system", "authn", "default", "last"]
server.deployment.groupsDeployment group order.Value of groups, otherwise ["first", "system", "authn", "default", "last"]
server.deployment.group_affiliationsMap of module names to their default deployment groups. Configured entries override built-in affiliations.Built-in platform affiliations
heartbeatOptional HTTP heartbeat configuration. The heartbeat module starts after configured modules have started.{"enabled": false}

Each entry in modules supports the following properties:

NameDescriptionDefaultMandatory
nameModule class name or alias.
enabledWhether the module is deployed.true
groupDeployment group. When omitted, the configured or built-in module affiliation is used, then default."default" or module affiliation
instancesNumber of instances to deploy.1
workerWhether to deploy the module using worker execution.false
configJSON object passed to the module.{}

The optional heartbeat object enables the HTTP heartbeat after all configured modules have started. See Heartbeat for the responder settings and defaults.