The umbrella term for the entire platform.
A concrete installation of OMP for a specific environment, organization, or deployment surface.
A module definition. It describes a reusable module that can be installed multiple times.
A concrete module instance inside a specific OMP instance.
An app definition that belongs to a module definition. An app definition can represent a web app, Portal app, worker app, or service app.
The concrete runtime instance of an app inside a specific module instance. An app instance can have its own artifact, configuration, host placement, route, path, public URL, and runtime policy.
A deployable build product for an app definition, such as a published folder, zip archive, or other packaged output.
A concrete runtime target inside an OMP instance. A host can carry zero or more app instances.
A template that describes how an OMP instance is expected to look structurally.
A template for a host role within an instance template.
A collective term for the tables that describe desired structure in a template:
InstanceTemplateHostsInstanceTemplateModuleInstancesInstanceTemplateAppInstances
A link between a concrete host and a host template. This is an automation-related part of the model, not a required part of manual installation.
A representation of a deployment attempt or deployment state for a host.
The shared web UI for navigation and administration in OMP.
A future optional automation component that can read desired topology and deployment state and execute or verify actions on hosts.